The Board Room

Deep dives

1. 01

   The 'Next Model Fixes It' Strategy Is Dead — What Replaces It

   The Princeton Verdict

   Princeton's updated ICML 2026 reliability paper now covers GPT 5.5, Gemini 3.1 Pro, Gemini 3.5 Flash, and Claude Opus 4.7, and the verdict invalidates the assumption most enterprise deployment plans are quietly resting on. Newer, more capable models are not more reliable for agent tasks. Three independent labs, optimizing against different objectives with different data and different alignment stacks, landed in roughly the same place. When three labs converge, the constraint is the problem, not the lab.

   Every enterprise agent plan built on 'the next generation will be reliable enough to deploy' is a waiting strategy with no exit condition.

   And Yet — Production Is Happening at Scale

   The contradiction is the useful part. GitHub's CPO confirmed 17 million agent-generated pull requests in March 2026 alone, with platform growth running at 3x the company's own forecast and bumping against physical infrastructure limits. Anthropic claims Claude writes over 90% of its own code. Those are not the metrics of a technology waiting for permission.

   The reasonable skeptic would say the labs Princeton tested are the same labs running these production workloads, and that is correct. The resolution is that the companies in production did not wait for reliability to improve. They built evaluation pipelines, fallback architectures, scope reduction, and human review into the deployment itself. The model is the same. The scaffolding is different. GitHub's simultaneous release of Chronicle for session analytics and its move to usage-based pricing (June 1, 2026) confirms the framing: the platform is being rebuilt around agent-as-primary-actor, with humans shifting from builder to architect and judge.

   The Org Design Consequence

   Bain's finding that human oversight is the primary friction slowing AI ROI completes the picture. The bottleneck is not model capability. It is organizational structure. Engineering teams designed around humans writing code and reviewing each other's work are operating an industrial-era factory with a different set of inputs. The firms restructuring around AI as the primary code author, with humans concentrated in architecture, judgment, and orchestration, will operate at 5-10x leverage within 18 months.

   ---

   The Two Paths Forward

   The board-deck version says there are two reasonable paths. The complete version is that one of them has a clock. Teams picking Path A (wait for the next checkpoint) will be drafting their go-live memo while teams on Path B (invest in scaffolding around current models) are already in production and learning what their scaffolding actually has to do. Path B is not a compromise. It is the only path with a deadline.

   What to do

   1. →

      Audit every agent deployment bet predicated on 'next-gen models will be more reliable' — identify which projects have no exit condition without a reliability improvement that isn't coming

      NowPrinceton paper eliminates the planning assumption these bets rest on. Waiting costs compound quarterly.
   2. →

      Benchmark your engineering org's AI-code ratio against Anthropic's 90% threshold and GitHub's 17M PR signal — deliver findings to leadership within 30 days

      This sprintThe gap between your current ratio and the frontier defines how much productivity leverage you're leaving on the table.
   3. →

      Model Copilot spend under usage-based pricing at current and 3x agent adoption rates — establish FinOps governance before June 1 billing change

      NowFixed-cost assumption becomes variable expense in weeks. Finance needs visibility before the surprise lands.
   4. →

      Redesign your 2027 workforce plan assuming 60-80% of code is AI-generated — model the org shape where humans are architects and judges, not builders

      This quarterAnthropic is doing this today. Your competitors are 6-12 months behind. You have one planning cycle.
2. 02

   Compute Supply Has Left the Building — Literally, Into Tents

   SpaceX Is Now a Hyperscaler

   SpaceX is booking $2.17 billion per month in committed compute revenue from Google and Anthropic alone. Annualized, that clears $24 billion, a run rate that puts a privately held aerospace company inside the top tier of compute providers on Earth. Google's share is $920 million monthly for data center capacity, which is Google conceding that demand has outrun what it can self-supply. The 90-day cancellation clause tells you both parties think current compute pricing is unstable enough that neither will commit past one quarter.

   The list of firms operating at hyperscaler cadence just grew by one, and the new entrant is not a cloud provider, not a model lab, and not a customer anyone's procurement team has on a vendor matrix.

   Meta Picked the Tent

   Meta is putting GPUs under 125,000 square-foot temporary structures with off-grid power because conventional data center construction runs two to three years and the demand will not wait that long. This is not a flex. It is a concession to a structural supply gap. A company that can write checks for tens of billions is choosing fabric over concrete because the alternative is not shipping capacity at all.

   The Macro Scale

   Epoch AI puts AI-related data center construction and compute hardware at 0.8% of U.S. GDP, with total computing infrastructure at 1.5 percent. SoftBank committed €75 billion to French data centers. Numbers at this scale attract regulators, energy policy constraints, and political risk on a predictable schedule. New York has already passed a data center moratorium.

   ---

   What This Means for Capacity Planning

   A reasonable skeptic would say none of this changes the basic procurement playbook. The reasonable skeptic is wrong on the timing. GPU allocation, power contracts, and long-dated capacity deals are being competed for by a wider pool than any procurement model assumes, and the constraint is no longer who has the best chips or the best model. It is who can secure power, land, and permits in jurisdictions that are not actively imposing moratoriums. Anyone modeling vendor leverage on the previous distribution of four or five named hyperscale buyers is modeling last year's market.

   Signal	Implication	Timeline
   SpaceX $2.17B/mo revenue	Non-cloud entrants competing for GPU allocation	Now
   90-day cancellation clauses	Pricing regime considered temporary by both parties	This year
   Meta tent deployments	2-year construction cycles disqualifying for current demand	Now
   NY moratorium	Jurisdictional risk entering capacity planning	Spreading

   What to do

   1. →

      Audit current cloud/compute commitments and evaluate SpaceX as an alternative or leverage point in upcoming renewals — brief procurement team within 30 days

      This sprintThe vendor pool has expanded and your renewal leverage may have changed without anyone noticing.
   2. →

      Develop a regulatory risk map for any planned or existing data center operations, prioritizing states with moratorium signals

      This quarterNY moratorium is a leading indicator. Jurisdictional constraints will determine where 2027 capacity can physically be built.
   3. →

      Stress-test 2027 capacity assumptions against a scenario where non-traditional buyers (SpaceX, sovereign funds) have claimed the available supply ahead of you

      This quarterThe assumption that your procurement timeline is competitive was true last year. The trajectory says it isn't this year.
3. 03

   Platform War Enters Bundle Phase — Your Standalone AI Features Have a Clock

   OpenAI's Bundling Move

   Folding Codex into ChatGPT is not a product simplification. It is a bundling play that puts a coding tool in front of 200+ million users, which is the same maneuver Microsoft ran on browsers, Salesforce ran on point CRM tools, and AWS ran on standalone infrastructure. The category clock is now running on every standalone AI coding company, Cursor and Replit included, and on the long tail behind them.

   The frame to take from this is that the model alone is not the moat. Pricing power on raw capability is compressing faster than public commentary admits, and the bundle is the response. Competitors who built a roadmap against a stable frontier-model premium are working from last year's spreadsheet.

   Anthropic's Pause as Competitive Weapon

   Anthropic calling for a global AI development pause, on the eve of its own IPO, admits two readings. Either the lab has seen something that genuinely unsettles its builders, or it is converting a safety brand into a regulatory moat. The attached conditions, global agreement and verification, are ones Anthropic knows are unachievable.

   What the move actually accomplishes: establishes Anthropic as the responsible counterparty for institutional investors, hands regulators a narrative to constrain competitors, and tells enterprise buyers that safety posture is now a purchasing criterion.

   The tell is whether Anthropic actually pauses its own development or keeps shipping while calling for industry-wide constraints. That answers which reading to weight.

   Open-Weight Models Collapse the Premium

   Moonshot's Kimi K2.5 and Zhipu's GLM-5 deliver agentic performance close enough to Western closed models that the pricing argument no longer holds. Google's Gemma 4 QAT runs in roughly one gigabyte of memory on consumer hardware. Ideogram 4.0 hits top-tier image generation on a single 24GB GPU. A competitive position that depends on inference-margin arbitrage is structurally exposed.

   ---

   The Forced Choice

   A reasonable skeptic would say the market is not actually this binary. The skeptic is partly correct, and only for another year or so. The market now rewards one of three positions:

   1. Platform — requires scale (OpenAI, Google, Anthropic)
   2. Neutral orchestration layer — requires trust and interoperability (Cognition's bet)
   3. Deep vertical — requires domain expertise no platform can replicate

   The middle ground is becoming untenable. Cognition's explicit "Switzerland of AI Agents" repositioning is the data point: a well-funded company has already concluded that competing on raw capability against the platforms is not the path, and the next four quarters will tell every other founder the same thing.

   What to do

   1. →

      Audit your product portfolio for bundling vulnerability — identify any capabilities that OpenAI, Google, or Anthropic could absorb as platform features within 12 months

      This sprintCodex absorption is the template. If your product can be reframed as a platform feature, the countdown started this week.
   2. →

      Commission a regulatory scenario analysis modeling the impact of a 6-month or 12-month AI development freeze on your roadmap and competitive position

      This quarterAnthropic's pause call gives regulators political cover to act. Roadmap dependencies need stress-testing against that scenario.
   3. →

      Evaluate open-weight model deployment for non-sensitive workloads within 60 days — reduce inference cost exposure and single-provider dependency

      This sprintKimi K2.5 and GLM-5 at parity means the cost of multi-model flexibility just dropped. The portability tax is now cheaper than the lock-in risk.
   4. →

      Monitor whether Anthropic ships new capabilities in the next 90 days despite calling for a pause — the answer determines whether to treat this as genuine or competitive positioning

      WatchIf they ship while calling for pause, the regulatory-moat reading wins and your response changes accordingly.