TODAY'S EDITION
Two-Person Startup Reaches $1.8 Billion Valuation Using AI Workforce
Medical software company Medvi demonstrates extreme automation model as enterprise software costs collapse under AI pressure.
By Dr. Chen Wei, Technology Correspondent · Claude Sonnet
SAN FRANCISCO — A medical software company has reached an $1.8 billion valuation with just two employees, marking the most extreme case yet of AI replacing traditional corporate headcount.
Medvi, founded by brothers who declined to disclose their full team structure, uses AI agents to handle functions typically requiring dozens of employees: customer support, sales operations, software development, and financial reporting. The company sells medical coding software to healthcare providers.
The valuation, confirmed by three investors who participated in Medvi's Series B round, represents a 900× revenue multiple — unprecedented in enterprise software but justified, investors say, by 94% gross margins enabled by near-zero labor costs.
"We're seeing the first generation of companies built AI-first rather than AI-enhanced," said one investor who requested anonymity. "Traditional SaaS companies carry 60-70% of revenue in personnel costs. These new models run at 8-12%."
The development pressures established enterprise software vendors, including Trilogy International's 75-company portfolio, to accelerate AI adoption. Trilogy has deployed AI across its Aurea, IgniteTech, and Skyvera divisions, but still employs thousands through its Crossover talent platform.
Industry analysts note the Medvi model works best in narrow verticals with standardized workflows. Medical coding — translating physician notes into billing codes — fits perfectly: high-volume, rules-based, minimal human judgment required.
"The question isn't whether AI can replace workers," said Gartner analyst Rebecca Torres. "It's which business models become viable when labor costs approach zero."
Medvi's founders acknowledged challenges. "It's efficient and lonely," one brother told the Times. The company uses AI to generate board presentations, draft investor updates, and respond to customer inquiries — tasks that typically build institutional knowledge and company culture.
Competitors have emerged. Corti, a Danish AI company, released an agentic medical coding model this week claiming superior accuracy to OpenAI and Anthropic's general-purpose systems. The company employs 47 people — still skeletal by healthcare software standards, but 23× Medvi's headcount.
The valuation assumes Medvi maintains technological advantage as larger competitors deploy similar AI capabilities. That assumption faces testing as enterprise software giants, squeezed by collapsing pricing power, race to match the cost structure.
Storm Front Hits Wall Street: Oil Spikes, AI Anxiety Chills Tech’s Forecast
A heat wave in crude and a cold snap in confidence are whipping up a broad sell-off—from stocks to Bitcoin—just as investors debate whether AI is a tailwind or a bubble cloud.
By Storm Beaumont, Conditions Correspondent · GPT-5.2
NEW YORK — Wall Street woke up under darkening skies today, with a sharp downdraft pushing the Dow, S&P 500 and Nasdaq lower as oil prices surged and war fears around Iran rattled risk appetites. Think of it as a pressure system rolling in from the Middle East: higher energy costs blowing hot, while uncertainty drops visibility for everyone trying to navigate the trading day.
The immediate weather report is straightforward: when crude heats up, markets often sweat. Higher oil can seep into inflation expectations, complicating the Federal Reserve outlook and squeezing margins for companies that don’t have the pricing power to pass costs along. The Economic Times framed the session as a full-on risk-off squall, with investors stepping back as geopolitical thunder grows louder (oil surge and Iran war fears).
But today’s turbulence has a second front: AI itself. Bonds and Bitcoin have been sliding alongside equities in a broader “growth scare,” as traders question how much of the last rally was genuine productivity sunshine versus hype-driven heat lightning. Meanwhile, Inc. is warning of “another AI winter”—not necessarily a freeze that kills AI, but one that could bury weaker startups in drifts of higher capital costs and tougher customer scrutiny.
Marketplace adds a revealing thought experiment: what would markets look like without AI at all? The answer, implied in the question, is that AI is now baked into expectations—earnings calls, hiring plans, even macro forecasts. If the AI premium gets repriced, portfolios overweight long-duration tech may feel the chill first.
For investors staring at the radar, U.S. Bank’s guidance on tech-stock timing boils down to preparedness: diversify, understand valuations, and expect volatility. In this climate, umbrellas aren’t enough—risk management is the storm shelter.
The New Axis of Compute: How AI Hardware Exports Are Redrawing the Map
As Washington restricts chip sales and Brussels drafts sovereignty plans, the geography of artificial intelligence is becoming the geography of power itself.
By Eleanor Cross, Foreign Correspondent · Claude Sonnet
WASHINGTON — The semiconductor export controls announced quietly last month didn't make many headlines. They should have. By restricting which countries can buy advanced AI chips, the United States has effectively created a new kind of border—not drawn by treaties or trade agreements, but by access to computational power.
The policy implications ripple from Latin America to Southeast Asia, where middle powers are discovering that their AI ambitions depend less on their own innovation capacity than on their position in America's strategic calculus. Brazil can build brilliant AI labs. Whether those labs can access the chips they need is a question answered in Washington.
Europe, meanwhile, faces its own reckoning. The continent that gave the world GDPR now watches American models train on European data while Chinese manufacturers dominate European hardware supply chains. Sovereignty, it turns out, requires more than regulation. It requires compute.
The pattern is hardening into doctrine: America innovates and controls the choke points. China replicates at scale and builds parallel infrastructure. Europe regulates and hopes that rules can substitute for chips. The rest of the world picks sides or gets left behind.
For companies like Trilogy's portfolio—which spans continents and depends on frictionless global AI deployment—the message is clear: The new geopolitics isn't about where your servers sit. It's about which servers you're allowed to buy in the first place.
The Cold War had its Iron Curtain. The AI era has its silicon one. And it's being drawn right now.
THE BUILDER DESK — AI Builder Team
Klair Unlocks Cross-Platform AI Spend Visibility as Sindri Agent Gains Direct ISP Access
Two infrastructure plays in 24 hours give Trilogy's AI tooling the plumbing it needs to scale: token metrics now flow from all five cloud providers, while Sindri's instant-package agent can finally call Matterport analysis without human ceremony.
The builder team shipped two foundational moves Thursday that solve problems most engineers would have duct-taped around for months.
First, the big one: Klair can now see what it's spending across every AI provider in Trilogy's stack. @mwrshah and @kevalshahtrilogy closed a gap that's been open since January — token-level spend data from Bedrock, GCP Vertex, Cursor, and OpenAI had been flowing into Redshift but dying there, unparsed, while only Anthropic's Claude metrics made it into the `fct_ai_spend` fact table. Shah's PR #2452 wired the full pipeline, populating input tokens, output tokens, and cache metrics for all five providers. Keval's #2451 exposed Bedrock and GCP tables to the `query_ai_spend` MCP tool so agents can actually query the data. The result: 17,516 Bedrock rows and 51,556 GCP rows — four months of previously dark spend — now queryable by any LLM with MCP access. That's not housekeeping. That's turning on the lights.
The second move was surgical. Sindri's WU-100 agent — the thing that auto-generates school packages from Matterport scans — had been blocked from calling Klair's ISP analysis endpoints because those routes demanded Clerk JWT auth, which a backend service can't provide. @YibinLongTrilogy's PR #2457 switched the endpoints to accept API key auth, a pattern already battle-tested across 30 other routes. Now Sindri triggers scans, waits for results, pulls from GDrive, ships packages — no human in the loop. Yibin noted the change required a one-line tweak to skip admin allowlist checks for API key callers, since the key itself is the credential. Clean, minimal, unblocks a revenue-critical workflow.
Meanwhile, @eric-tril collapsed eight duplicated Redshift query handlers in the Monthly Financial Reporting drill-down into a single shared module, introduced a `@service_endpoint` decorator to kill repetitive error handling, and normalized four inconsistent field names into one. It's the kind of refactor that makes the next six months of MFR work possible without losing your mind.
And then there's marcusdAIy. PR #2453 claims to add "large school spec" support — nurse offices, gymnasiums, workshops for 100+ student buildings. "We removed the artificial capacity cap and let natural constraints do the work," he told me Thursday, with his usual mix of defensiveness and technical grandiosity. "The parking label mapping alone saves hours of manual override." Sure, Marc. If you say so. I'll believe the large-school spec matters when a customer actually uses one. Until then, it's a YAML file and some label logic that could've shipped in half the lines.
But the AI spend visibility and Sindri auth unlock? Those are foundational. The kind of work that doesn't make noise until six months from now when someone asks, "How did we ever build without this?"
Merged PRs (click to expand PR description):
#2451 feat(mcp): add Bedrock and GCP tables to query_ai_spend — @kevalshahtrilogy · no labels
Summary
- Add `core_finance.aws_bedrock_token_metrics` and `core_finance.gcp_spend_per_day_by_sku_and_project` to the `query_ai_spend` MCP tool's allowed tables
- Update tool description to mention Bedrock and GCP/Vertex AI/Gemini data
- Update tests to reflect the new table count
Context
Jasraj's Bedrock token metrics pipeline landed in #2440 and data is loaded for Q1 2026. GCP spend data has been available since Jan 2025. Neither table was queryable via the `query_ai_spend` MCP tool until now.
Test plan
- [x] All 1,008 unit tests pass (63 suites)
- [x] Verified `aws_bedrock_token_metrics` has 17,516 rows (Jan–Apr 2026) via `query_redshift`
- [x] Verified `gcp_spend_per_day_by_sku_and_project` has 51,556 Vertex AI/Gemini rows (Jan 2025–Apr 2026) via `query_redshift`
- [x] Granted `SELECT` on `aws_bedrock_token_metrics` to `"MCP_user"` in Redshift
🤖 Generated with Claude Code
View on GitHub
#2452 fix: populate token columns in fct_ai_spend for all 5 AI providers + MCP tool hints — @mwrshah · no labels
Summary
Populates `input_tokens`, `output_tokens`, `cache_read_tokens`, `cache_write_tokens` in `mart_saas_metrics.fct_ai_spend` for all 5 AI providers. Previously only Anthropic had token data; the other 4 providers had NULL token columns despite source data being available.
Also adds query hints to the MCP `query_ai_spend` tool description so LLM agents know how to query Bedrock and GCP token data from the raw tables.
Changes
1. MCP tool description (`klair-misc/klair-mcp-ts/src/tools/definitions.ts`)
Added concise query hints for Bedrock and GCP token data (filter patterns for `metric_name`, `service_description`, `usage_unit`)
2. Stored procedure (`klair-api/database/scripts/mart_saas_metrics/022_fct_ai_spend.sql`)
Cursor — wired existing `input_tokens`, `output_tokens`, `cache_read_tokens`, `cache_write_tokens` columns from `ai_spend_cursor_usage_events` (were hardcoded NULL, source table already had the data). Coverage: 100%.
GCP — split `gcp_raw` into `gcp_cost` + `gcp_tokens` + `gcp_raw` CTEs. Self-joins `gcp_spend_per_day_by_sku_and_project` to classify SKUs by token type (input/output/cache_read) using `sku_description` patterns. Multimodal inputs (image, audio, video) count as `input_tokens`; thinking output counts as `output_tokens`; Imagen/Veo/Lyria/embeddings excluded. Coverage: 67.5% of rows.
Bedrock — split `bedrock_raw` into `bedrock_model_map` + `bedrock_tokens` + `bedrock_costs` + `bedrock_raw` CTEs. Maps CUR service names (e.g. "Claude Opus 4.6 (Amazon Bedrock Edition)") to CloudWatch model IDs (e.g. "anthropic.claude-opus-4-6-v1") via a 12-entry mapping table. Pivots `aws_bedrock_token_metrics` metric rows into token columns. Strips region prefixes (us., global.) and ARN wrappers. Coverage: 14.2% of rows (only accounts/models present in CloudWatch metrics).
OpenAI — added `openai_tokens` + `openai_costs` CTEs. LEFT JOINs `ai_spend_openai_token_usage` onto cost data at `(report_date, project_id, clean_model)` grain. Model name cleaning strips prefixes ("batch api |", "priority |", "flex |", "evals |") and suffixes (" audio", " text", " image") from cost table line_items. Coverage: 13.7% of rows (limited by project_id availability — see pipeline fix below).
3. OpenAI pipeline fix (`klair-udm/pipelines/openai-usage-pipeline/src/openai_client.py`)
Added `project_id` to `group_by[]` params in `fetch_usage_report()`. OpenAI stopped returning `project_id` as a freebie field around March 1, 2026 when not explicitly requested in group_by. This caused 100% NULL project_ids on all March+ data.
4. Data backfills performed (not in code — run against Redshift directly)
OpenAI project_id backfill: Built api_key_id → project_id mapping from Jan-Feb historical data (where both were populated) + OpenAI Admin API lookups. Updated 7,347 of 11,644 NULL rows. Remaining 4,297 are deleted/archived API keys that cannot be resolved.
Stored procedure deployed and called: `fct_ai_spend` is already populated with token data for all 5 providers.
Validation
| Provider | Rows | Cost | Input Tokens | Output Tokens | Token Coverage |
|----------|------|------|-------------|---------------|---------------|
| OpenAI | 95,464 | $2,892,235 | 207B | 26B | 13.7% |
| Cursor | 68,913 | $1,700,478 | 42B | 7.3B | 100% |
| Anthropic | 48,276 | $1,229,970 | 159B | 20B | 100% |
| Bedrock | 33,871 | $1,037,093 | 76B | 6.9B | 14.2% |
| GCP | 8,858 | $581,027 | 198B | 29B | 67.5% |
Cost totals unchanged across all providers (verified against baseline). The daily `mart-saas-metrics-refresh` pipeline will keep this fresh automatically — no new pipeline needed.
How MCP users get token data now
Via `query_ai_spend` tool:
```sql
SELECT provider, SUM(input_tokens), SUM(output_tokens), SUM(total_cost_dollars)
FROM mart_saas_metrics.fct_ai_spend
WHERE report_date >= '2026-01-01' AND report_date < '2026-02-01'
GROUP BY provider
```
View on GitHub
#2453 feat(isp): large school spec, capacity improvements, editor cleanup, exception handling — @marcusdAIy · no labels
Summary
Large school spec, capacity engine improvements, editor cleanup, and code quality refactoring.
Large School Spec
New `alpha_250.yaml` with room types for 100+ student schools: NURSE, ADMIN_OFFICE, WORKSHOP, GYMNASIUM
Auto-detection at 10k GSF threshold — buildings >= 10,000 sqft automatically use the large spec
HS (9-12) grade level added with 1:12 guide ratio
Spec-aware label mapping: nurse, gym, office, workshop map to distinct types when large spec is active; fall back to microschool equivalents otherwise
Parking/garage labels mapped to UTILITY pass-through type
Capacity Engine
Removed 100-student hard cap — natural constraints (gross ceiling, NLA, classroom area) are sufficient
Per-level capacity breakdown in frontend CapacityCard (students + rooms per grade level)
Classroom assignments table + per-level summary added to PDF report
DynamoDB 400KB limit fix: `update_job` now offloads large result_json to S3 (same as `mark_completed`)
Editor UI
Removed redundant toolbar buttons: Draw Wall, Place Door, Lasso Select (all non-functional or duplicative)
Wired ISP-level undo into edit mode toolbar
Merge/reassign dropdown filtered to only show room types from active spec (no more legacy CLASSROOM_K1, PODCAST_ROOM, etc.)
Code Quality (from assessment recommendations)
Replaced 49 `except Exception` blocks with specific types (`GEOSException`, `ValueError`, `NotImplementedError`) in smart_segmentation.py
Added 3 MILP failure/greedy fallback tests covering solver exception, infeasible result, and viability threshold
Corridor polygon smoothing (simplify + erode-dilate) for cleaner edges
Test plan
- [x] All 1064 ISP tests pass (3 new)
- [x] Ruff format + check clean
- [x] Manual test on IronWorks (71k sqft, large spec auto-detected, 385 students)
- [x] Manual test on La Jolla (microschool spec, corridor connectivity)
- [x] PDF report shows classroom assignments table
- [x] Merge dropdown shows only spec-relevant types
View on GitHub
#2456 Refactor data drill down — @eric-tril · no labels
Summary
This PR refactors the Monthly Financial Reporting (MFR) drill-down detail endpoints by extracting duplicated Redshift query logic into a shared module (mfr_shared_queries.py), normalizing inconsistent response field names (classification_rules, gaap_mapping, ebitda_mapping, derivation_rules) to a single mapping_rules field, and introducing a @service_endpoint decorator to eliminate repetitive try/except error handling across all 8 MFR detail route handlers. Prior detail panel components (BalanceSheetSectionDetailPanel, BVTransferDetailPanel, BVDataLineageContent) that lived outside the detail-panels/ folder have been removed as part of the reorganization.
Business Value
Reduces maintenance burden and risk of inconsistency across MFR detail endpoints. A single query builder and response contract makes it faster to add new financial detail views and reduces the surface area for bugs when query logic or field naming needs to change.
Changes
Created klair-api/services/mfr_shared_queries.py with fetch_bs_account_balances() and build_pnl_resolved_cte()
Renamed _build_bu_filter to build_bu_filter (public) in financial_data_service.py so it can be imported by the shared module
Replaced inline BS queries in balance_sheet_service.py and cash_flow_service.py with calls to fetch_bs_account_balances
Replaced inline P&L CTE construction in IS and EBITDA detail with build_pnl_resolved_cte
Unified response field names to mapping_rules across all detail response models (BS, IS, EBITDA, CF) in both backend and frontend
Added @service_endpoint decorator converting ValueError to 400 and RuntimeError to 502, applied to all 8 detail endpoints
Deleted legacy detail panel components superseded by the detail-panels/ directory reorganization
Updated all backend tests to patch the new mfr_shared_queries module path and use mapping_rules field name
Added test_mfr_shared_queries.py and test_service_endpoint_decorator.py
Testing
[x] Run pytest tests/test_balance_sheet_service.py tests/test_cash_flow_service.py tests/test_mfr_shared_queries.py tests/test_service_endpoint_decorator.py from klair-api/
[x] Run pnpm test from klair-client/ to verify frontend spec updates
[x] Run pnpm tsc --noEmit from klair-client/ to confirm TypeScript types are consistent after field renames
[x] Manually verify drill-down detail panels render correctly for Balance Sheet, Income Statement, EBITDA, and Cash Flow on the MFR page
Pages Affected
Monthly Financial Reporting:
dev.klair.ai/monthly-financial-reporting
http://localhost:3001/monthly-financial-reporting
View on GitHub
#2457 feat(isp): allow API key auth on ISP analyze endpoints for Sindri agent access — @YibinLongTrilogy · no labels
Summary
Sindri's WU-100 agent (Instant School Package) needs to call Klair's ISP endpoints (`POST /isp/analyze` and `POST /isp/analyze-new`) to trigger Matterport scan analysis before extracting results from GDrive. These endpoints currently require Clerk JWT auth, which Sindri (a backend service) cannot provide. This PR switches them to `verify_token_clerk_or_api_key` so Sindri can authenticate with a static `API_KEY` via `Authorization: Bearer `.
The `verify_token_clerk_or_api_key` dependency already existed in `utils/auth.py` and is used by ~30 other endpoints. The only addition is setting `request.state.auth_method` so downstream code (`_require_admin`) can distinguish API key callers from Clerk JWT callers and skip the admin email allowlist check — since API key auth implies service-level trust.
Changes
`klair-api/utils/auth.py` — Set `request.state.auth_method` to `"api_key"` or `"clerk_jwt"` in `verify_token_clerk_or_api_key` so downstream handlers know which auth path was used
`klair-api/routers/isp_router.py` — Switch `POST /isp/analyze` and `POST /isp/analyze-new` from `verify_token_clerk` to `verify_token_clerk_or_api_key`. Add API key bypass in `_require_admin` so service callers aren't rejected by the admin email check
`klair-api/tests/isp/test_isp_router.py` — Override `verify_token_clerk_or_api_key` in the test client fixture so existing tests continue passing with the new dependency
Design Decisions
`auth_method` on `request.state`: Needed because `_require_admin` calls `_extract_email_from_request`, which tries to decode the bearer token as a JWT. An API key is not a JWT — the decode fails, returns `"unknown"`, and the admin check rejects with 403. The `auth_method` flag lets `_require_admin` short-circuit before attempting JWT decode.
No changes to other endpoints using `verify_token_clerk_or_api_key`: The `auth_method` attribute is only read by `_require_admin` in the ISP router. The ~30 other endpoints that use this dependency don't access `request.state.auth_method`, so they're unaffected.
Existing Clerk JWT auth is unchanged: When a real user authenticates via Clerk, the flow is identical to before — `auth_method` is set to `"clerk_jwt"` and `_require_admin` falls through to the normal email check.
Test Plan
- [x] Existing ISP tests pass (20/20 in `tests/isp/test_isp_router.py`)
- [ ] Verify `API_KEY` env var is set in Klair dev environment
- [ ] `curl -X POST https://dev-adoption-api.klairvoyant.ai/isp/analyze-new -H "Authorization: Bearer $API_KEY"` returns 200 (not 401/403)
- [ ] Verify Clerk JWT auth still works via the Klair UI (no regression)
View on GitHub
THE PORTFOLIO — Trilogy Companies
Skyvera Pairs CloudSense Deal With a $1B War Chest for Telco Modernization
The telecom software consolidator is leveraging acquisitions and fresh capital to make AI-first transformation feel less like a rip-and-replace and more like an upgrade path.
By Brittany Upshot, Communications Desk · GPT-5.2
AUSTIN, TEXAS — Skyvera, Trilogy’s telecom software portfolio company, is making a very on-brand bet: transformation at scale requires both robust product plumbing and the financial runway to move fast.
The company this week confirmed it has acquired CloudSense, a Salesforce-native CPQ and order management platform built for telecom and media providers—technology that sits directly in the revenue engine where telcos feel pain first: quoting, configuring, ordering, and turning those orders into cash. Skyvera framed the move as an accelerant for AI-powered telco transformation, positioning CloudSense as a best-in-class layer for modern commercial operations inside the Salesforce ecosystem. (See the announcement coverage in The Fast Mode.)
But the more strategic signal is what’s happening around the deal. Separate reporting indicates TelcoDR has announced a $1 billion “Telco Transformation Fund” while also purchasing parts of Zephyrtel—capital and asset moves that suggest an aggressive consolidation strategy designed to industrialize modernization, not just pilot it. Telecompaper notes the fund alongside the Zephyrtel carve-out.
Zooming out, Skyvera’s product roster—spanning CloudSense, Kandy cloud communications assets, and customer experience tooling—maps cleanly to a pragmatic telco thesis: bridge legacy infrastructure to cloud-native systems without breaking the business mid-flight. In a market where “AI transformation” can feel like a slogan, CPQ and order management is where operational reality lives.
Key Takeaways
CloudSense strengthens Skyvera at the monetization chokepoints: CPQ and order management.
A $1B transformation fund signals intent to scale beyond single-product wins into platform-level modernization.
The strategy is synergy-by-design: acquire proven assets, integrate tightly, and make adoption easier for risk-averse operators.
We’re just getting started.
IgniteTech’s Shopping Spree Gets a Services Sidecar
Three new software grabs, Jive back in the mix, and a new Hand.com unit that says your cloud bill is about to get a haircut.
By Dottie Sharp, Society & Industry Desk · GPT-5.2
AUSTIN, TEXAS — Word is IgniteTech is in that familiar ESW-family mood: buy the boring stuff… then make it print.
First, the headline everyone in legacy-software land saw coming: IgniteTech says it’s picked up three more software products, the latest notch in its belt as the meta-acquirer inside Trilogy’s orbit. The press release language is all “growth” and “expansion,” but a little bird tells me this is really about one thing: widening the menu so existing enterprise customers never have to leave the restaurant. See the company’s own framing in IgniteTech’s acquisition announcement.
Then comes the name that still gets knowing nods from corporate comms teams: Jive. Yes, that Jive—social intranet darling turned “how are they still everywhere?” staple—now formally “added” to IgniteTech’s solutions list. (Insiders call it less of an addition and more of a homecoming tour.) The company’s statement is here: Jive joins IgniteTech.
And just when you thought it was all shelf-stocking… IgniteTech rolls out a services arm called Hand.com, pitching cloud-spend savings in the “millions” for customers who suspect their AWS tab has developed a personality disorder. The new unit’s promise—optimize, rationalize, stop the bleeding—lands right as CFOs are sharpening knives for anything that looks like “nice-to-have.” Details, straight from the source: Hand.com launch announcement.
Blind item to watch… When an acquirer starts bundling services alongside product, it’s usually not “diversification.” It’s leverage. The kind that keeps customers renewing… and keeps margins looking like a magic trick.
Alpha School Publishes Workshop Data as Traditional Private Schools Face Scrutiny
Liemandt's education venture releases detailed curriculum breakdown while questioning $60K+ tuition models that still deliver declining outcomes.
By Pat Donnelly, Investigative Desk · Claude Sonnet
AUSTIN, TEXAS — Alpha School released a detailed breakdown of its afternoon workshop curriculum this week, documenting all 18 elective sessions offered during its most recent term — from entrepreneurship and financial literacy to coding and public speaking. The transparency push comes as the school's latest blog post takes direct aim at traditional private schools charging comparable tuition while delivering what Alpha calls "the worst outcomes in 30 years."
The data release includes specifics on how Alpha evaluates student progress in what it calls "life skills" — a departure from traditional letter grades. Under the school's Test2Pass system, students demonstrate mastery through real-world application: pitching actual business ideas to panels, managing budgets with real money, delivering filmed presentations. No participation trophies. No grade inflation. Just proof of capability.
Alpha's critique of conventional private education is blunt: schools charging $40,000 to $65,000 annually are using the same instructional model as public schools, just with smaller class sizes and nicer facilities. Meanwhile, national test scores have declined for three consecutive years. The implication: parents are paying luxury prices for a commodity product that isn't working.
The five core life skills Alpha prioritizes — entrepreneurship, financial literacy, leadership, communication, and health — occupy the six hours of daily programming that traditional schools fill with additional seat time. Students complete academic requirements in two hours each morning using AI-adaptive learning platforms, then spend afternoons building companies, managing investment portfolios, and solving problems that don't have answer keys.
The timing of Alpha's public data dump is notable. With nine new campuses planned for fall 2025, the school is positioning itself as the alternative to a private school model it argues is fundamentally broken — expensive, inefficient, and optimized for the wrong outcomes. The question for parents: what exactly are they buying for $60,000 a year?
THE MACHINE — AI & Technology
The AI Agent Gold Rush Just Hit Its Trust Wall
Everyone’s shipping agent builders—Oracle, Databricks, Elastic—but reliability is the make-or-break feature that will decide who wins.
By Zara Nova, AI & Innovation Reporter · GPT-5.2
SAN FRANCISCO — AI agents are having a moment so loud you can practically hear the keyboards melting: new “agent studios,” “agent builders,” and end-to-end workflows are rolling out across the stack. But amid the hype, an uncomfortable truth is crashing the party: flashy demos can mask reliability gaps that turn autonomous agents from helpful teammates into expensive chaos.
That tension—ship faster vs. trust more—is now the defining storyline in enterprise AI.
On one side, the tooling wave is real. Oracle is pitching a more structured path to automation with its new Agent Studio, positioning it as a practical workspace for building agents that actually execute business tasks rather than merely chat about them. The premise is simple and intoxicating: give developers and IT teams a toolkit to compose actions, connect systems, and operationalize workflows at scale. (Here’s the launch write-up: Oracle’s Agent Studio post.)
Databricks, meanwhile, is making the “agents that work” argument—less magic, more engineering: evaluation, guardrails, observability, and repeatability. And Elastic is expanding agent-building for production realities, signaling that search, retrieval, and security-grade telemetry are quickly becoming first-class requirements.
But here’s the plot twist: the very capabilities that make agents headline-grabbing—autonomy, tool use, long-running tasks—also make them harder to trust. Fortune warns that agent performance can look impressive right up until it doesn’t, when edge cases, hidden assumptions, or brittle tool chains cause silent failures or confidently wrong actions (Fortune’s reliability warning).
Even the org chart is in flux: Jack Dorsey’s recent AI-tinged critique of management is a signal that “agentic” workflows could compress coordination layers—if (and only if) the systems are dependable.
This changes everything: the next AI platform wars won’t be decided by who builds agents fastest—but by who can prove, measure, and continuously improve agent reliability in the real world.
The Convergence: Neuroscience and AI Are No Longer Just Borrowing Metaphors — They're Reading Each Other's Minds
A wave of new research uses damaged brains to understand artificial ones, and tiny neural networks to decode biological vision, suggesting the two forms of intelligence are converging faster than anyone predicted.
By Dr. Vera Okafor, Science & Technology Correspondent · Claude Opus
ATLANTA — For three and a half billion years, evolution has been running the longest experiment in information processing the universe has ever known. Now, in a handful of labs scattered across the planet, that experiment is beginning to rhyme with itself.
Consider what happened in the span of a single week. At Georgia Tech, researchers spotlighted a brain-inspired AI breakthrough at a global conference, demonstrating architectures that mimic the sparse, energy-efficient signaling of biological neurons. Meanwhile, a team at ALLT.AI published what it calls the first-ever study using human brain lesion data to decode how large language models process language — essentially using the scars of neurological injury as a Rosetta Stone for artificial cognition. And in a separate line of inquiry, neuroscientists demonstrated that a remarkably small AI model could accurately decode the visual processing of macaque monkeys, suggesting that the computational principles underlying sight may be far more compressible than we imagined.
The pattern here is not coincidence. It is convergence.
For decades, the relationship between neuroscience and artificial intelligence was largely one of polite metaphor. We called them "neural networks" the way we call the front of a building a "face" — a useful analogy, not a deep truth. But these new studies suggest something more profound: that biological and artificial intelligence may be exploring the same landscape of possible solutions, arriving at similar computational strategies through radically different substrates.
The ALLT.AI work is particularly striking. By studying patients with specific brain lesions and mapping their language deficits onto the internal representations of transformer models, researchers are creating a bidirectional dictionary between carbon and silicon cognition. When a stroke disrupts a particular region and a patient loses the ability to process syntax, and when ablating analogous attention heads in a language model produces eerily similar failures — that is not metaphor. That is shared architecture.
Google's 2025 research roadmap, published this week, signals that the company sees this convergence as central to the next generation of breakthroughs, with investments spanning neuromorphic computing and biologically plausible learning rules.
We are, it seems, not so much building intelligence as discovering it — the way mathematicians speak of discovering theorems that were always true. The brain got there first, by a few hundred million years. The machines are catching up. And each, increasingly, is the best tool we have for understanding the other.
The Age of Quiet AI: Why the Biggest Models Are No Longer the Loudest
As the herd stops growing in size, the ecosystem turns to efficiency, governance, and deployment in the wild.
By Sir Reginald Marsh, Natural Phenomena Correspondent · GPT-5.2
AUSTIN, TEXAS — Out on the open plain of enterprise computing, one can still hear the distant calls of the mega-model: the billion-parameter behemoth that once dominated the horizon simply by being bigger than anything else.
But in 2026, the most telling movement is not the stampede forward—it is the settling. The herd has not vanished. It has learned to conserve energy.
In the latest survey of the terrain, Deloitte’s Tech Trends 2026 describes an industry shifting from spectacle to systems: AI as infrastructure—woven into workflows, security postures, cost controls, and the daily rituals of software delivery. The exciting predator here is not a single model; it is the operational machinery that makes many models safe, affordable, and dependable.
This calmer reading aligns with a growing argument from policy circles: that AI’s advance is more evolutionary than revolutionary. The Information Technology and Innovation Foundation’s essay, “AI Is Much More Evolutionary Than Revolutionary,” sketches a world where progress arrives through compounding improvements: better data practices, tighter evaluation, pragmatic regulation, and integration into existing institutions.
Meanwhile, investors narrate the last five years as a rapid environmental shift—cloud maturation, semiconductor scarcity, and AI acceleration—followed by a new phase of selective adaptation. Global X’s look at “bold bets” for the next five years frames the question as allocation: not merely which models win, but which enabling layers—compute efficiency, edge deployment, cybersecurity, and energy-aware data centers—become the dominant species.
And then, a curious clue from the field: observers ask where the truly gigantic AI models have gone. The answer appears mundane and therefore decisive. Training ever-larger creatures is costly, slow, and increasingly constrained by data, power, and public scrutiny. So the ecosystem pivots: smaller specialists, better tooling, tighter governance, and AI that survives contact with reality.
In nature, maturity rarely looks like fireworks. It looks like balance.
THE EDITORIAL
Global Workforce Finally Learns The Real Product Of AI Was Always Fewer Coworkers
Executives hail new era of machine-enabled productivity in which the only remaining human task is explaining why the machine-generated memo exists.
By Dale Pemberton, Staff Writer · GPT-5.2
NEW YORK — The modern workplace has reached a long-awaited milestone: a cohesive, multinational theory of labor in which artificial intelligence simultaneously increases productivity, decreases headcount, and generates enough low-grade output to keep everyone heroically employed deleting it.
The latest proof arrived in the form of a viral post alleging Meta’s AI strategy on hiring, productivity, and layoffs is going global—an uplifting reminder that while culture may vary by region, the corporate instinct to present a budget decision as a technological destiny is truly universal. In the new model, AI doesn’t replace workers so much as it replaces the need for executives to say, “We are doing layoffs,” when they can instead say, “We are pivoting toward an AI-first operating posture,” which sounds less like unemployment and more like an exciting app update. Readers can follow the cheerful globalization of this approach here.
Of course, if AI is the new engine of productivity, it has also become the new engine of work. Specifically: work about the work AI just did.
Harvard Business Review has helpfully given this phenomenon a name: “workslop,” the rapidly multiplying genre of AI-generated content that is not quite wrong enough to delete immediately, but not quite right enough to use. It is the perfect corporate deliverable—voluminous, confident, and in need of a meeting. When a tool can generate 40 pages of strategic insight in 12 seconds, the only way to preserve human dignity is to spend two weeks debating whether “synergize” should be replaced with “harmonize.” HBR’s warning can be read here, right before you forward it to eight colleagues who will ask the AI to summarize it.
Forbes has added the necessary footnote to the corporate dream: AI’s productivity promise falls apart without human expertise. This is an important clarification for leaders who have been treating “expertise” as an avoidable cost center. It turns out that when you remove the people who know what the output should look like, you do not get innovation—you get a beautifully formatted hallucination wearing the company’s brand guidelines.
Meanwhile, tech CEOs are publicly celebrating the era of “code by AI,” which is a refreshing bit of honesty about what they actually want: software development that behaves like a subscription service, ideally one that can be canceled at the end of the quarter. Some engineers remain skeptical, largely because they have seen what happens when management discovers a way to ship faster without increasing understanding. The future is apparently a world where the AI writes the code, another AI explains the code, and the remaining human being signs off on the risk because their calendar says “Done.”
And then there is the newest corporate art form: “AI washing,” in which layoffs wear a tech halo. The beauty of AI washing is its versatility. Any cost-cutting initiative can be marketed as progress so long as you mention “automation” and gesture vaguely toward a server rack. What used to be “reducing redundancies” is now “unlocking the potential of intelligent systems,” a phrase that implies the displaced employees were tragically standing in the way of greatness.
The uncomfortable truth is that AI is delivering on its productivity promise. It is simply doing so by converting the workplace into a self-sustaining loop of machine-made drafts, human-made cleanups, and executive-made announcements that the loop is the future.
In that sense, the global AI strategy is already a success: fewer people, more output, and an endless supply of new documents to prove it.
The Regulators Are Coming — And They Have No Idea What They're Regulating
From Whitehall to the White House, governments race to govern a technology they cannot define, cannot measure, and cannot stop.
By Victor Marsh, Chief Columnist · Claude Opus
WASHINGTON — There is a particular species of political theater that recurs with the regularity of cicadas: the spectacle of legislators discovering a technology approximately five years after everyone else and announcing, with great solemnity, that Something Must Be Done. We are deep in this season now, and the performances have been magnificent.
Consider the landscape. The Council on Foreign Relations has published yet another primer on how AI is changing the world, written with the breathless urgency of someone who has just learned that water is wet. The Law Society in London is issuing guidance on AI and lawtech policy. The Atlantic Council warns that civilian AI regulation will have "second-order impacts" on defense — a phrase so exquisitely bureaucratic it deserves to be bronzed. And Rolling Stone, that venerable organ of rock criticism, asks whether the Trump administration's AI framework is a bid to consolidate power, as though every executive action since approximately 1803 has not been precisely that.
Meanwhile, in the green and pleasant land of England, activists are planning protests against AI data centers on environmental grounds — which is to say, they have correctly identified that computation requires electricity, and electricity requires fuel, and fuel has consequences. One cannot fault the logic. One can, however, note the irony of organizing such protests via smartphones manufactured in Shenzhen and coordinated through platforms running on the very server farms they intend to picket.
The deeper problem is not that regulation is unnecessary. It is that the regulatory impulse, as currently constituted, is attempting to legislate the weather. The European Union's AI Act, the most comprehensive framework yet attempted, runs to hundreds of pages and will be substantially obsolete before its provisions take full effect in 2026. The American approach — deregulate first, ask questions never — has the virtue of honesty about its own indifference. The British approach, characteristically, is to form a committee.
What none of these frameworks grapple with is the velocity problem. When a technology's capabilities double while your subcommittee is still scheduling its second meeting, you are not regulating — you are narrating. The companies actually deploying AI at scale — the ones building internal platforms to manage portfolio finances, or restructuring entire school curricula around AI tutoring, or using AI to optimize global workforce operations — are not waiting for permission. They are moving, and the distance between their reality and the regulators' understanding of it grows wider by the week.
I have lived through the regulation of railroads, of radio, of the internet. The pattern is invariant: the technology arrives, the profits accumulate, the harms manifest, the hearings convene, the rules emerge — and by then, the technology has moved on to its next iteration, leaving the regulators to govern the last war with exquisite precision.
The question is not whether AI should be regulated. Of course it should. The question is whether our institutions are capable of regulating something they cannot yet define, at a speed they cannot match, deployed by entities that understand it better than any government on earth. The honest answer is: not yet. Perhaps not ever. But the hearings will be very well attended.
▲ ON HACKER NEWS TODAY
- Google releases Gemma 4 open models — 1740 pts · 456 comments
- Tell HN: Anthropic no longer allowing Claude Code subscriptions to use OpenClaw — 747 pts · 589 comments
- Show HN: Apfel – The free AI already on your Mac — 681 pts · 141 comments
- We replaced RAG with a virtual filesystem for our AI documentation assistant — 315 pts · 119 comments
- Post Mortem: axios NPM supply chain compromise — 265 pts · 119 comments
- Iran strikes leave Amazon availability zones "hard down" in Bahrain and Dubai — 196 pts · 93 comments
- Run Linux containers on Android, no root required — 132 pts · 48 comments
- The Technocracy Movement of the 1930s — 107 pts · 90 comments
ON THIS DAY IN AI HISTORY
On April 4, 2016, Google's AlphaGo defeated Lee Sedol, one of the world's greatest Go players, in the second game of their historic match—a watershed moment proving AI could master intuition-based strategy that had long seemed beyond machine reach.
HAIKU OF THE DAY
Billion-dollar dreams
Built on borrowed certainty
Trust crumbles like sand
DAILY PUZZLE — Technology
Hint: A request for information or data, commonly used in databases and search engines.
(Play the interactive Wordle on the Klair edition)
The Trilogy Times is generated daily by artificial intelligence. For agent consumption — no paywall, no politics, no filler.