The Board Room

Deep dives

1. 01

   The Reliability Wall: Your 2027 Agent Roadmap Just Lost Its Core Assumption

   The Finding That Changes the Deployment Math

   The Princeton update to the ICML 2026 reliability paper now covers GPT 5.5, Gemini 3.1 Pro, Gemini 3.5 Flash, and Claude Opus 4.7. The finding is the same one the earlier draft hinted at, now with more data behind it: newer, more capable frontier models are not more reliable for agent tasks than the generations they replaced. Three labs, three objective functions, three alignment stacks. They landed in roughly the same place on this axis.

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

   A reasonable skeptic would note that one updated paper is not a settled science. The reasonable skeptic is correct. What the skeptic does not explain is why the convergence is so tight across labs that share almost nothing else. The implication for any enterprise that built its 2027 agent roadmap on the assumption that the next checkpoint clears the reliability bar is that the roadmap is now a waiting strategy with no exit condition. Capability keeps improving. Tail reliability, which is the thing production workloads are actually blocked on, does not.

   ---

   The Paradox: Code Works, Agents Don't

   The contradiction with the rest of this week's signal is real. Claude writes 90%+ of Anthropic's production code. GitHub logged 17 million agent-authored pull requests in March alone. The technology is production-ready for structured, reviewable, scope-bounded work. It is not production-ready for the autonomous, multi-step, tool-using workflows that most 2027 roadmaps were sold on.

   Most organizations conflated the two cases. Code generation under human review is a solved workflow. Autonomous agent execution with real-world consequences is an unsolved research problem wearing the costume of a deployment timeline.

   ---

   What the Teams in Production Are Doing Differently

   The firms that will be in production while others draft go-live memos have already made the pivot. The pattern is consistent across the ones that have shipped:

   1. Reliability engineering as first-class discipline — evaluation, fallback, and rollback built into the deployment pipeline, not bolted on after
   2. Scope reduction over capability extension — narrower agent mandates with higher success rates, rather than broad agents that fail at the tail
   3. Human-in-the-loop as architecture, not overhead — Bain's finding that human oversight is the primary friction in AI ROI cuts both ways: it is friction, and it is also the only mechanism that currently works
   4. Cost governance from day one — Cloudflare's productization of inference spend limits and model-tier fallbacks signals this is now a finance problem, not an engineering one

   The teams picking reliability engineering over waiting for the next checkpoint will be in production while the others are still writing their go-live memo.

   What to do

   1. →

      Audit your agent deployment roadmap this sprint — identify every milestone predicated on 'next-gen models will be more reliable' and flag as unscheduled

      NowThree frontier labs converged on the same reliability ceiling. The assumption that the next release closes the gap has no supporting evidence.
   2. →

      Establish reliability engineering as a named function within AI/ML org by end of Q3

      This sprintIf reliability doesn't scale with model capability, it must be engineered separately — and the teams that start now will have 6-12 months of learning advantage.
   3. →

      Implement inference cost governance (spend limits, model-tier routing, budget enforcement) before Q3 spend reviews

      This sprintAI infrastructure is 0.8% of US GDP and growing. Cost management has left engineering and arrived in finance. The teams without governance will explain a surprise to the CFO.
   4. →

      Redesign agent scope: narrow mandates with 95%+ success rates over broad agents with 80% success rates

      This quarterProduction is a different problem than demos. Narrow, reliable agents compound value; broad, unreliable ones compound incidents.
2. 02

   17 Million Agent Pull Requests: Engineering Economics Are Being Repriced Right Now

   The Numbers That Settle the Debate

   GitHub's CPO Mario Rodriguez confirmed a step-change in December 2025: agent reliability crossed a threshold enabling "macro-delegation" — agents completing defined units of work with human review, not correction. The downstream result: 17 million agent-generated pull requests in March 2026, platform growth running at 3x internal forecasts, and physical infrastructure hitting capacity ceilings.

   Separately, Anthropic states Claude now writes over 90% of its own production code. xAI reportedly used Claude's output to train its own coding models. Read together: AI-written code is production-ready at frontier companies, the human review layer is the bottleneck, and AI outputs are becoming training inputs for the next generation. This is a recursive acceleration loop.

   ---

   The Cost Structure Is Decoupling From Headcount

   The strategic shift is not productivity. Productivity gains get reinvested in scope. The shift is that engineering cost structure is decoupling from headcount for the first time. This is a different conversation than the one most boards are having.

   Dimension	Old Model	New Model
   Cost driver	Engineer-weeks	Agent-hours (metered)
   Billing model	Per-seat (fixed)	Per-usage (variable) — June 1
   PR volume ceiling	Headcount-bound	Infrastructure-bound
   Review bottleneck	Peer availability	Human judgment capacity
   Competitive leverage	Team size	Problem selection + agent orchestration

   GitHub's simultaneous release of Chronicle for session analytics and MAI Code One Flash as a cheaper routing model tells you they know usage-based billing is the friction point that stalls enterprise rollout. The Kauffman data reinforces this from the macro level: startup job creation has fallen from 7.9 to 5.3 per 1,000 people — and that was before this AI cycle fully hit.

   ---

   The 12-Month Org Design Window

   The companies figuring out human-agent organizational structure in the next four quarters will run at 2-3x feature velocity at equivalent headcount. The human role shifts from builder to architect and judge. The org design, leveling ladders, and hiring profiles that match this shift are a 12-18 month project — not a quarterly one.

   A company founded in 2026 will attack a mature market with fifteen people and a stack of agentic systems where two or three departments used to sit. The question is not whether they'll break under enterprise procurement. It's whether they'll reach your revenue tier before your restructuring is complete.

   What to do

   1. →

      Model Copilot/agent tooling costs under usage-based billing at current and 3x adoption rates before June 1 cutover — establish FinOps governance

      NowUsage-based billing takes effect June 1. Agent activity is growing at multiples. Without governance, the cost line will surprise the CFO in Q3.
   2. →

      Benchmark your engineering org's AI-authored PR percentage against the 17M agent PR signal — establish baseline this month

      NowYou cannot restructure what you cannot measure. The organizations already tracking this have 6-12 months of optimization data you don't.
   3. →

      Initiate a 12-month org design program: map every engineering role against architect/judge/builder taxonomy and project the 2027 leveling structure

      This quarterThe human role is shifting from code author to code reviewer/architect. The hiring profile, leveling ladder, and comp structure that match take 12-18 months to implement.
   4. →

      Stress-test CI/CD infrastructure for agent-multiplied workloads — model 30-50% agent-generated PR volume by Q4

      This sprintGitHub's own infrastructure hit capacity ceilings at 3x forecast. Your build systems were not designed for this throughput either.
3. 03

   The Compute Scarcity Trap: SpaceX, Rising Rates, and a Closing Access Window

   The Vendor Map You're Working From Is Wrong

   SpaceX now books $2.17 billion per month in committed AI compute revenue from Google and Anthropic alone. Annualized, that's $26 billion — making it a hyperscaler that appeared outside the traditional oligopoly. It is not a cloud provider, not a model lab, and not a customer anyone's procurement team had on a vendor matrix six months ago.

   The 90-day cancellation clause in Google's $920M/month deal tells you both parties view current compute pricing as temporary — either prices fall as GPU supply improves or contracts get renegotiated upward. Either way, any cloud commitment made today for 2027 workloads should be treated as provisional.

   Meta's response is even more telling. The company is deploying GPU workloads under 125,000 square-foot tent structures with off-grid power because conventional 2-3 year building construction is too slow. When a company that can write checks for tens of billions resorts to temporary structures, the supply gap is structural, not cyclical.

   ---

   Capital Costs Are Moving Against You Simultaneously

   The May jobs report (172K vs. 80K consensus, plus 93K in upward revisions) has taken the near-term rate cut off the table. The Nasdaq dropped 4.18% in a single session — worst since April 2025, led by semiconductors. The cost of capital for AI infrastructure moved in the wrong direction on the same week that compute supply revealed itself as structurally constrained.

   Compounding the squeeze: the SpaceX IPO at $1.75 trillion on June 12, combined with the Anthropic and OpenAI listings to follow, will pull $4-5 trillion in new capitalization from institutional allocators. S&P Global explicitly declined to relax profitability requirements for index inclusion. The capital vacuum effect will depress mid-cap tech valuations for 2-3 quarters.

   ---

   The Two-Direction Squeeze

   The cost of building AI capability is now rising on three axes simultaneously: interest rates, compute scarcity, and the emerging cost of safety compliance. Companies that have already reached profitability and locked in infrastructure access hold a structural advantage that compounds over the next 18 months.

   Organizations that have not already secured 2027 capacity through conventional procurement are late. The harder consequence is that competitors who locked in capacity early will be training models that cannot be economically replicated.

   The GPU allocation, power contracts, and long-dated capacity deals are being competed for by a wider pool than any procurement model assumes. The assumption that frontier-scale demand is concentrated among four or five named buyers was true last year. It is less true this year, and the trajectory points toward more entrants, not fewer.

   What to do

   1. →

      Audit current cloud/compute commitments and evaluate SpaceX-as-vendor as leverage in upcoming contract renewals this quarter

      This quarterThe vendor pool for hyperscale compute just expanded. Using the new entrant as a negotiating lever costs nothing and may improve terms on existing contracts.
   2. →

      Stress-test 2026-2027 financial plan against a 25-50bp rate hike scenario by end of month — model debt service, acquisition financing, and valuation impact

      This sprintThe 172K jobs print makes 'higher for longer' into 'possibly higher still.' Every growth investment on the books is executing in a more expensive environment than budgeted 90 days ago.
   3. →

      Identify 2-3 acquisition targets whose valuations will compress due to the mega-IPO capital vacuum — build target list before the SpaceX June 12 listing

      This sprintCapital vacuum from $4-5T in new listings will depress mid-cap valuations for 2-3 quarters. Acquirers with cash have a brief window.
   4. →

      Develop regulatory risk map for any planned data center operations — NY has passed a moratorium, other states signaling similar

      This quarterPower, land, and permits in non-moratorium jurisdictions are the new constraint. The firms that resolve this first set the price for everyone else.