The Board Room

Deep dives

1. 01

   The 'Next Model Fixes It' Thesis is Dead — Your Agent Roadmap Needs a New Foundation

   The Princeton Finding That Changes the Planning Assumption

   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. The finding is narrow and uncomfortable. Newer, more capable models are not more reliable for agent tasks than the ones they replaced. Three independent labs, optimizing against different objectives with different data and different alignment stacks, landed in roughly the same place on tail reliability.

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

   The common enterprise posture has been to wait for the next model to clear the reliability bar. That is now a waiting strategy with no exit condition. The curve was supposed to keep bending. For now, it has stopped. The 2027 roadmap was not built to absorb that finding.

   The Contradiction That Defines This Moment

   The intelligence picture gets more interesting from here. Reliability has flatlined while raw capability is compounding aggressively. Anthropic reports Claude writes 90%+ of its own codebase. GitHub logged 17 million agent-authored pull requests in March. Open-weight models like Gemma 4 QAT run on 1GB of memory on consumer hardware. The gap between what AI can do in controlled environments and what it reliably does in production is widening.

   That produces two classes of use case with very different deployment postures:

   • Code generation and structured creation: Production-ready now. Human review catches failures. Volume proves the pattern works.
   • Autonomous decision-making and tool-use agents: Still blocked on tail reliability. No evidence the next generation solves it.

   What the Competitors Are Doing

   A reasonable skeptic would say the next model release will close the gap and the patient teams will be vindicated. The reasonable skeptic has been correct for three years. The Princeton data is the first serious evidence that this cycle is different. The teams quietly building production around evaluation, fallback, scope reduction, and human review will be live while the teams waiting on the next checkpoint are still drafting the go-live memo. The path to production now runs through everything around the model.

   Open-weight parity accelerates the dynamic. Moonshot's Kimi K2.5, Zhipu's GLM-5, and Google's Gemma 4 show the capability gap between open and closed models has collapsed for most production workloads. The deciding factor is no longer raw capability. It is cost, control, and reliability engineering. Any competitive position depending on inference-margin arbitrage is structurally exposed.

   ---

   The Decision This Quarter

   The question is not which model to standardize on. The question is whether the agent program is designed around model improvements that are not arriving on the schedule the 2024 plans assumed. Reliability engineering becomes a first-class discipline this year, not next. The teams that build it now will have six to twelve months of production learning over the teams that defer. That is the gap the next planning cycle will be measured against.

   What to do

   1. →

      Audit every agent deployment milestone predicated on 'next-gen models will be more reliable' — flag those without a model-independent reliability path

      NowPrinceton proves the assumption has no deadline; plans built on it are indefinitely deferred by default
   2. →

      Stand up a reliability engineering function for AI agents (evaluation, fallback, scope gating, human-in-loop) separate from ML research by end of Q3

      This sprintThe path to production runs through infrastructure around the model, not through the model itself — and this capability compounds
   3. →

      Evaluate open-weight model deployment (Gemma 4, Kimi K2.5, GLM-5) for non-sensitive workloads to reduce inference cost and vendor lock-in exposure

      This quarterOpen-closed gap has collapsed for production workloads; staying locked to frontier providers is paying a premium for a moat that no longer exists
   4. →

      Implement AI inference cost governance with model-tier routing and budget enforcement before Q3 spend reviews

      This sprintCloudflare's productization of inference cost controls confirms AI cost management has left engineering and arrived in finance — the CFO will ask
2. 02

   Your Engineering Org Has 12 Months Before the Restructuring Happens To You

   The Numbers That Ended the Debate

   Three data points, read together, demand a fundamental rethink of how engineering organizations are structured:

   1. Anthropic claims Claude writes over 90% of its code — not as a demo, but in production.
   2. GitHub logged 17 million agent-generated pull requests in March 2026 — platform growth running at 3x the company's own forecast.
   3. Bain reports that human oversight is now the primary friction slowing AI ROI at enterprise deployments.

   AI-written code is not only production-ready at frontier companies — the human review layer is now the bottleneck, and AI outputs are becoming training inputs for the next generation of systems. This is a recursive acceleration loop.

   December 2025: The Capability Step Nobody Announced

   GitHub's CPO Mario Rodriguez puts a date on the shift: December 2025. That's when model reliability crossed a threshold enabling what he calls macro-delegation — agents completing defined units of work where the human reviews rather than corrects. The 17 million PR figure is downstream of that change, not coincident with it. Physical infrastructure is now bumping against capacity ceilings from the load.

   The pricing shift makes the economics unavoidable. Usage-based billing takes effect June 1, 2026, meaning the cost line is now coupled to agent activity, which is growing at multiples. GitHub's simultaneous release of Chronicle for session analytics and MAI Code One Flash as a cheaper routing option tells you the company knows this is the friction point.

   The Org Design Consequence

   The cost structure of an engineering organization is now decoupled from the headcount structure. This is not a productivity story — productivity gains get reinvested in scope. This is a cost-structure story that shows up in the operating plan. The Kauffman data confirms the macro trend: startup job creation has fallen 33% since 1997 (from 7.9 to 5.3 per thousand). That decline predates AI. The full impact has not arrived yet.

   A company founded in 2026 will go after mature markets with fifteen people and agentic systems replacing two or three departments. The question is not whether this happens. It is whether your org restructures on its own schedule or on a competitor's.

   Role Shift	From	To
   Engineer	Primary code author	Architect, judge, orchestrator
   Engineering Manager	Team throughput coordinator	Agent governance and quality gatekeeper
   Cost Model	Headcount × salary	Agent-hours × token consumption
   Billing	Per-seat license	Usage-based (June 1, 2026)

   The FinOps Surprise Coming in Q3

   Organizations that bake token discipline and routing logic into engineering practice over the next two quarters will keep the productivity gains. Organizations that wait will be explaining a surprise variable expense to the CFO in Q3. The bill now scales with pull requests, not employees.

   What to do

   1. →

      Benchmark your engineering org's AI adoption maturity against the 90% threshold — measure what percentage of PRs, code reviews, and CI tasks are agent-assisted vs. manual by end of Q3

      This sprintYou cannot restructure what you have not measured, and the frontier is moving at 3x the rate anyone forecasted
   2. →

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

      NowUsage-based billing starts June 1; without governance, costs will surprise the CFO within one quarter of accelerated adoption
   3. →

      Revise 2027 workforce plan with a scenario where 60-80% of code is AI-generated — model the org design, leveling, and hiring profile implications

      This quarterThe org design, leveling ladders, and hiring profile that match the architect-and-judge shift are a 12-18 month project — starting now means landing on time
   4. →

      Stress-test CI/CD infrastructure for agent-multiplied workloads — model what happens when agent-generated PRs reach 30-50% of total volume

      This sprintAgent activity compounds across entire CI/CD stack (PRs → Actions → security scans); GitHub itself hit capacity ceilings at 3x forecast
3. 03

   Supply Chain Attacks Are Now Self-Replicating — This Is a Category Change, Not a News Cycle

   From Campaign to Worm: The Threshold That Was Crossed

   The Miasma worm compromised 73 Microsoft GitHub repositories and remains uncontained. This is not a supply chain campaign. It is a self-replicating supply chain worm — autonomous, scalable, and operating across the repositories of the company that owns the platform. The distinction matters: what was once a labor-intensive, targeted attack is now an automated, self-propagating one. This is analogous to the shift from phishing to botnets.

   Stack this against the Hugging Face Transformers remote code execution vulnerability affecting 2.2 billion installs. The exploit targets AI model configuration files — the artifacts ML teams download from model hubs every working day — and specifically hits GPU-accelerated inference infrastructure. Any organization running production inference on downloaded models has a live exposure right now.

   Discovery Outpaces Remediation — Structurally

   A security startup's AI agent discovering 21 zero-day vulnerabilities in FFmpeg alone proves that AI-powered vulnerability discovery is production-ready. The capability means two things simultaneously: defenders can find issues faster, and adversaries with similar tools will discover exploitable flaws at a rate that overwhelms human patching capacity. Anthropic's Project Glasswing is expanding to 150 critical infrastructure companies, which adds a discovery supply shock on the defensive side.

   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 crystallizes the risk: an actively exploited high-severity vulnerability in SD-WAN infrastructure with no available patch. That is a vendor relationship failure — when your sole provider has no fix, you have no options.

   The Offense Has Reached Platform Economics

   AI attack tools are now sold with vendor-like business models on criminal marketplaces — priced and supported like ordinary crimeware. Microsoft formally published 7 new AI agent failure modes, signaling the problem warrants ecosystem-level coordination. The attack surface is expanding faster than defensive capabilities, AI is accelerating this asymmetry, and traditional trust models (vendor repositories, official packages, single-vendor infrastructure) are proving insufficient.

   The Board Question

   The conversation must shift from 'how much do we spend on security?' to 'are we architecturally capable of operating safely in a world where we will always have unpatched vulnerabilities?' Companies that make the architectural pivot in the next 12-18 months hold a durable advantage in resilience.

   What to do

   1. →

      Commission immediate audit of all npm and GitHub dependencies against Miasma/IronWorm indicators — implement mandatory dependency pinning and provenance verification this sprint

      NowThe worm is uncontained and self-replicating across Microsoft's own repos; passive monitoring is insufficient for autonomous threats
   2. →

      Map every Hugging Face model, AI coding tool, and third-party AI integration in production — verify none are exposed to the Transformers RCE

      Now2.2B installs means this is likely in your stack; the exploit targets GPU inference — your most expensive and strategically critical compute
   3. →

      Convene emergency review of Cisco SD-WAN exposure and activate compensating controls (network segmentation, enhanced monitoring) until patch is available

      NowActively exploited with no patch available — this is a no-remediation-path scenario requiring immediate architectural mitigation
   4. →

      Evaluate build/buy/partner for AI-powered security testing and virtual patching capabilities by end of Q3

      This quarterDiscovery-remediation gap is structural and widening; organizations without AI-augmented security are falling further behind every quarter