The Board Room

Three Labs, One Ceiling

The updated ICML 2026 reliability paper now includes GPT 5.5, Gemini 3.1 Pro, Gemini 3.5 Flash, and Claude Opus 4.7, and the verdict is the one the field has been quietly bracing for. Newer, more capable models are not more reliable for agent tasks. This is not one lab hitting a wall. Three independent labs, optimizing against different objectives with different data and different alignment stacks, converging on the same reliability ceiling.

When three labs converge on the same constraint, the constraint is usually not the lab. It is the problem.

The implication is direct. The most common enterprise AI deployment strategy, "gate the agent program on next-gen model reliability", is a waiting strategy with no exit condition. Every deployment blocked on that assumption now needs a different path to production.

The Paradox: AI Writes Production Code But Can't Run Autonomously

Sources diverge here, and the divergence is instructive. Anthropic claims Claude writes 90%+ of its production code. GitHub logged 17 million agent-generated pull requests in March 2026. These are not pilot numbers. They are production-scale output from AI systems operating in structured, human-reviewed workflows.

The distinction matters. AI is good at bounded, reviewable work, the kind that ends in a human sign-off. It plateaus at autonomous multi-step execution, the kind that has to chain decisions without checkpoints. A reasonable skeptic would say the gap closes as models improve. The Princeton data says the gap is not closing. The winning teams have stopped waiting and are restructuring around the review-based pattern that already works.

What This Means for the 2027 Roadmap

The path to production no longer runs through model capability improvements. It runs through everything around the model: evaluation frameworks, fallback architectures, scope reduction, human-in-the-loop design, rollback mechanisms. Teams building that infrastructure now will be in production while teams still waiting on the next checkpoint are drafting the go-live memo.

Open-weight models reinforce the shift. Google's Gemma 4 QAT runs in ~1GB of memory. Moonshot's Kimi K2.5 and Zhipu's GLM-5 match frontier closed models on agentic benchmarks. If reliability does not improve with scale, and capability is commoditizing at the same time, the durable advantage moves to orchestration, evaluation, and workflow design. We have argued this in this column for months and it was contested. It is less contested now.

The Cost of Waiting

AI infrastructure spending now sits at 0.8% of U.S. GDP. A meaningful share of that is underwriting agent deployment timelines the Princeton data does not support. The cost of continuing to wait is not zero. It is the compound interest on deferred capability while competitors ship with imperfect but functional reliability engineering.

The Numbers Are No Longer Pilot-Scale

Two data points landed this week that, taken together, stop being a signal and start being proof. Anthropic reports Claude writes over 90% of its production code. GitHub's CPO confirmed 17 million agent-generated pull requests in March 2026, with platform growth running at 3x internal forecast. GitHub is hitting physical capacity ceilings in its data centers, which is not the kind of problem you reach by accident.

The cost structure of an engineering organization is now decoupled from the headcount structure in a way it was not eighteen months ago.

GitHub's CPO describes the December 2025 step as a shift from micro-delegation, where the model fills in lines, to macro-delegation, where the model completes a defined unit of work and a human reviews it. The 17M PR figure is what you get when the review pipeline has already absorbed the new input and humans are approving often enough to keep the pipe full. That is the part that matters.

The Cost Model Is About to Surprise Finance

Usage-based Copilot billing takes effect June 1, 2026. Engineering cost is now coupled to agent activity rather than to headcount, and agent activity is compounding at multiples. The same week, GitHub shipped Chronicle for session analytics and MAI Code One Flash as a cheaper model for simple tasks. Both ship because GitHub knows where enterprise rollouts will stall.

Teams that build token discipline and semantic routing into engineering practice over the next two quarters will keep the productivity gains. Teams that wait will spend Q3 explaining a surprise FinOps line item to the CFO.

The Kauffman Data Confirms the Structural Shift

Startup job creation has fallen from 7.9 to 5.3 per 1,000 people since 1997, and the decline predates the current AI cycle. The full effect of agentic systems on new-firm headcount has not arrived yet. A company founded in 2026 will attack an incumbent market with fifteen people and a stack of agents where departments used to sit. The revenue-per-employee gap between lean AI-native entrants and incumbents is widening every quarter.

The Org Design Decision

A reasonable skeptic would say this is still a story about Anthropic and one quarter of GitHub data. The skeptic is correct, and also misses the point. The human role is shifting from builder to architect and judge, and organizations that restructure around AI as the primary code author, with humans in architecture, judgment, and orchestration, will operate at 5-10x leverage. Anthropic is operating that way today. Most competitors are six to twelve months behind, which leaves one planning cycle to get the engineering org model right before the gap stops being recoverable.

Self-Replication Changes the Economics of Attack

The Miasma worm has compromised 73 Microsoft GitHub repositories and remains uncontained. This is not a targeted campaign requiring operator coordination. It is an autonomous, self-replicating supply chain attack — analogous to the shift from targeted phishing to automated botnets. What was labor-intensive is now scalable without human involvement.

Supply chain attacks have crossed the self-replication threshold. Dependency management is no longer a DevOps hygiene practice — it is a board-level risk with a blast radius that scales autonomously.

Microsoft's own repositories being compromised is the detail that demands attention. Platform ownership provides no immunity. The trust model that says "official repository = safe" is now empirically false.

AI-Powered Vulnerability Discovery Is Overwhelming Patch Capacity

A security startup's AI agent discovered 21 zero-day vulnerabilities in FFmpeg — a library so ubiquitous it touches virtually every video processing workflow on earth. Chrome patched 429 bugs in a single cycle. Anthropic's Project Glasswing is expanding to 150 critical infrastructure companies. The discovery side now runs at AI speed. The remediation side runs at human speed. The gap widens every quarter.

The Hugging Face Exposure

A remote code execution vulnerability in Hugging Face Transformers exploits AI model configuration files — artifacts that ML teams download from model hubs every working day. It targets GPU-accelerated inference, your most expensive and strategically loaded compute. With 2.2 billion installs, this is not a niche stack. Any organization running production inference on downloaded models has a live exposure right now.

Cisco SD-WAN: Exploitation Without Remediation

CVE-2026-20245 is an actively exploited high-severity vulnerability in Cisco SD-WAN with no available patch. This is a vendor relationship failure, not merely a security event. When your sole network infrastructure provider has no fix, you have no options. This should accelerate conversations about network infrastructure diversification.

The Structural Imbalance

Attackers have reached platform economics. AI attack tools sell on underground marketplaces with vendor-style support, meaning capability development is self-funding and compounding. Defenders are discovering that AI infrastructure adopted at speed carries vulnerabilities that are architectural rather than incidental. The discovery-to-remediation gap is now structural, and the security strategy predicated on "patching faster" is investing in the wrong side of the trend.

Multiple sources confirm that enterprise security budgets are finally unlocking — spending is moving before breach headlines, not after. The architectural question for boards: Are we capable of operating safely in a world where we will always have unpatched vulnerabilities?