The Board Room

Deep dives

1. 01

   The Agent Reliability Plateau — Your 2027 Deployment Roadmap Has No Exit Condition

   Three Labs, Same Ceiling, Different Implication

   Princeton's updated ICML 2026 reliability study now covers GPT 5.5, Gemini 3.1 Pro, and Claude Opus 4.7, and the finding is that newer, more capable models are not meaningfully more reliable on production agent tasks than the generation they replaced. A reasonable skeptic would point out that one study is one study. The reasonable skeptic would be ignoring that this is convergence across three independent organizations optimizing against different objectives, on different data, with different alignment stacks. When three labs land on the same ceiling, the ceiling is not the lab.

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

   The consequence for buyers is the part worth sitting with. The default enterprise posture — wait for the next frontier release to clear the reliability bar — is now a strategy with no exit condition. Capability scaling has decoupled from production reliability. The next checkpoint will improve the demo. It will not change the deployment math.

   The Cost of Waiting Is Now Visible

   The economics are moving on a separate track. AI infrastructure spending is running at 0.8% of U.S. GDP (Epoch AI), while open-weight models are producing useful work on consumer hardware — Google's Gemma 4 QAT runs in roughly 1GB of memory. The frontier is getting more expensive to produce and less expensive to consume at the same time. Competitive positions built on access to a specific model are the ones compressing fastest.

   Cloudflare's productization of inference cost governance — spend limits, model-tier fallbacks, identity-based controls — is the tell. AI cost management has left engineering and landed in finance. Teams that build cost governance now will carry 6-12 months of optimization advantage into the next budget cycle.

   What the Winning Teams Are Doing Differently

   The path to production runs through everything around the model: evaluation, fallback, scope reduction, human review loops, and reliability engineering treated as a first-class discipline rather than a postscript. The teams that picked this path quietly are in production already. The teams waiting on the next checkpoint are still drafting the go-live memo.

   Open-weight models reaching parity in specialized domains — Kimi K2.5 and GLM-5 matching frontier performance — means the model layer is commoditizing on a different timeline than the reliability layer. Any product whose moat reduced to "we have access to the best model" has watched that moat drain. What remains is proprietary data, distribution that makes the underlying model interchangeable, and integration depth that creates switching costs surviving a model swap. This quarter's deployment posture decides which of those three a company owns next year.

   What to do

   1. →

      Audit every agent deployment bet predicated on 'next-gen models will be more reliable' — identify which 2027 milestones have no path without reliability improvements that aren't arriving

      This sprintThe Princeton data shows three consecutive generations have failed to move the needle — plans built on this assumption are drifting indefinitely
   2. →

      Stand up a reliability engineering function for AI with dedicated headcount, separate from ML engineering — scope to evaluation frameworks, fallback orchestration, and scope-bounded deployment

      This quarterReliability is now the binding constraint, not capability. Teams that solve it will ship while others wait.
   3. →

      Evaluate open-weight model deployment for 2-3 non-sensitive production workloads within 60 days to reduce vendor dependency and inference cost

      This sprintOpen models at parity means inference margin arbitrage is structurally exposed — diversification is now free
   4. →

      Implement model-tier routing and inference cost governance before Q3 budget reviews

      This quarterUsage-based pricing plus agent volume growth creates surprise bills — the FinOps discipline needs to exist before the bill arrives
2. 02

   AI-Authored Code at Industrial Scale — The 12-Month Window to Restructure Engineering

   The Numbers That Settle the Debate

   Two data points landed in the same cycle, and between them they close out whatever remained of the question of whether AI code generation is a pilot or a production workflow.

   • GitHub: 17 million agent-generated pull requests in March 2026, three times the company's own internal forecast.
   • Anthropic: Claude writes 90%+ of its own code. The company building the model is running its engineering org on the model's output.

   GitHub's CPO has been explicit that something shifted in December 2025: agent reliability crossed a threshold that enabled what they are calling macro-delegation, where agents complete defined units of work and humans review rather than correct. The 17M PR figure is downstream of that capability step, not coincident with it. That distinction matters, because it tells you the curve is not going to bend back on its own.

   The cost structure of an engineering organization is now decoupled from its headcount structure. That is a different conversation than the productivity one.

   The Compounding Problem Nobody Is Modeling

   Agent-generated PRs compound across the entire CI/CD stack. Each PR triggers Actions runs, security scans, and review cycles, and the bill grows with the fan-out, not with the headcount that authored the change. GitHub's infrastructure hit capacity ceilings at three times forecast. That is not a marketing claim. You do not run out of data center floor space on vibes.

   The pricing change makes the timing immediate. Usage-based billing takes effect June 1, 2026, which means the cost line is now coupled to agent activity, and agent activity is growing in multiples. Engineering organizations that bake token discipline and routing logic into practice over the next two quarters will keep the productivity gains. The ones that wait will be explaining a surprise to the CFO in Q3.

   The Org Design Consequence

   Bain's read is that human oversight is the primary friction slowing AI cost savings, and xAI reportedly used Claude's output to train its own coding models. A reasonable skeptic would say one quarter of GitHub data and one Bain survey do not constitute a reorganization mandate. The skeptic is correct in the small. What the skeptic does not explain is the consistency of the signal across vendors, customers, and competitors training on each other's output, which is a recursive acceleration loop rather than a survey artifact.

   The Kauffman data provides the long view. Startup job creation has fallen 33% since 1997, from 7.9 to 5.3 jobs per thousand. A company founded in 2026 will attack a mature market with fifteen people and a stack of agentic systems. The gap between revenue per employee at the leanest new entrants and at established incumbents widens every quarter this continues.

   The human role shifts from builder toward architect and judge. The org design, leveling ladders, and hiring profiles that match that shift are a twelve to eighteen month project, not a quarterly one. The window in which this restructuring is proactive rather than reactive closes inside this calendar year.

   What to do

   1. →

      Benchmark your org's AI coding adoption against the 17M PR / 90% self-authored signals — measure what percentage of PRs, reviews, and CI tasks are agent-assisted today vs. 6 months ago

      This sprintYou cannot manage a transition you haven't measured, and the frontier has already crossed the threshold
   2. →

      Model Copilot/coding-tool spend under usage-based pricing at current and 3x adoption rates — establish FinOps governance before June 1 billing switch

      NowUsage-based billing starts June 1. Without cost governance, agent volume growth creates unbudgeted spend within one quarter.
   3. →

      Develop a 2027 engineering workforce plan with a scenario where 60-80% of code is AI-generated — model the org design implications (architect/judge roles vs. builder roles)

      This quarterAnthropic is already operating at 90%. Your competitors are 6-12 months behind them, which gives you one planning cycle to get this right.
   4. →

      Stress-test CI/CD infrastructure capacity for 3-5x current PR volume — identify bottlenecks before they become production incidents

      This quarterGitHub hit capacity ceilings at 3x. Your internal infrastructure likely has lower headroom.
3. 03

   Self-Replicating Supply Chain Worms — A New Class of Threat Demands Immediate Response

   Supply Chain Attacks Are Now Autonomous

   The Miasma worm has compromised 73 Microsoft GitHub repositories and remains uncontained. This is not another poisoned package incident. It is a self-replicating worm — the attack propagates without human intervention, analogous to the shift from targeted phishing to automated botnets. What was once a labor-intensive campaign is now scalable and autonomous. Microsoft's own repos being compromised signals that platform ownership provides no immunity.

   Simultaneously, a Hugging Face Transformers remote code execution vulnerability exploits AI model configuration files — the artifacts ML teams download from model hubs every working day. With 2.2 billion installs, this is not a niche exposure. It targets GPU-accelerated inference workloads: the most expensive and strategically loaded compute in your building.

   Discovery Now Outruns Remediation Structurally

   A security startup's AI agent discovered 21 zero-day vulnerabilities in FFmpeg alone — a library touching virtually every video processing workflow on earth. Anthropic's Project Glasswing is expanding to 150 critical infrastructure companies. The next generation of frontier models ('son of Mythos') purpose-built for vulnerability discovery is on the near-term horizon.

   When discovery runs at AI speed and remediation runs at human speed, the window of exploitable exposure widens every quarter until something on the defensive side compounds too. Nothing in the current vendor roadmap suggests that is happening soon.

   Cisco's CVE-2026-20245 — an actively exploited high-severity vulnerability in SD-WAN infrastructure with no available patch — exposes the fundamental fragility of single-vendor network architectures. When your sole provider has no fix, you have no options.

   Offense Has Reached Platform Economics

   Ransomware operators now sell AI attack tooling with vendor-like business models and support. Microsoft has formally expanded its attack taxonomy with 7 new AI agent failure modes — a signal that the problem warrants ecosystem-level coordination. Attacks that previously required nation-state sophistication are available at commodity pricing. The probability of being targeted has moved from 'if' to 'when.'

   Attack Vector	Blast Radius	Status
   Miasma worm (GitHub)	73 repos, spreading	Uncontained
   HuggingFace RCE	2.2B installs	Patch available
   Cisco SD-WAN 0-day	Enterprise WAN	No patch
   FFmpeg AI-found 0-days	Video processing	21 vulnerabilities

   What to do

   1. →

      Convene emergency security review of Cisco SD-WAN exposure within 48 hours — activate compensating controls (segmentation, enhanced monitoring, traffic analysis) until patch exists

      NowActively exploited, no remediation path. Every hour of delay is live exposure.
   2. →

      Audit all npm/GitHub dependencies and Hugging Face model downloads against Miasma/IronWorm indicators by end of week — implement mandatory dependency pinning and provenance verification

      NowSelf-replicating worm is still propagating across Microsoft's own repos. Your supply chain is not immune.
   3. →

      Commission a board-ready risk assessment quantifying your vulnerability remediation capacity vs. AI-accelerated discovery rate — present exposure scenarios within 30 days

      This sprintThe discovery-remediation gap is structural and widening. The board needs to understand this is not a patching problem but an architectural one.
   4. →

      Evaluate AI-powered compensating controls (virtual patching, runtime protection) as a bridge technology — initiate vendor evaluation within 45 days

      This quarterYou will always have unpatched vulnerabilities now. The question is whether your architecture makes individual vulns less consequential.