The Board Room

Deep dives

1. 01

   Anthropic Just Bought Your Multi-Provider Insurance Policy — The Abstraction Layer Decision Moves to This Quarter

   The Acquisition That Changes Every Multi-Model Strategy

   Anthropic's $300M acquisition of Stainless is being filed as a developer tools purchase. The more useful reading is that Anthropic now owns a piece of its direct competitors' developer experience. Stainless generates the SDKs that OpenAI and Google use to expose their models to developers, and increasingly to AI agents like Claude Code and OpenClaw that are becoming first-class API consumers.

   The closest analogy is Salesforce buying a CRM plugin that HubSpot and Microsoft Dynamics both depend on. It is competitive positioning dressed as product investment.

   The neutral plumbing connecting enterprise buyers to multiple model providers is no longer neutral, and the company that just bought the plumbing is one of the providers.

   Why This Matters More Than It Looks

   A reasonable skeptic would point out that Stainless can keep serving OpenAI and Google exactly as it did last week, and that Anthropic has every commercial incentive to let it. The skeptic is correct about this week. The skeptic is not correct about the three-year horizon. Ownership of a shared tooling layer does not have to be weaponized to matter. It only has to become a dependency the owner gets to reprice, reprioritize, or quietly deprecate at the margins.

   The timing is deliberate. Agents like Claude Code are becoming first-class API consumers, which means the tooling layer is no longer about developer convenience. It is about machine-to-machine interoperability. Whoever controls how agents reach models influences how the agent ecosystem forms around them. $300M for a four-year-old company is platform pricing on a business that still looks like a tools company.

   The Likely Market Response

   Google and OpenAI now face a choice: continue relying on a competitor-owned SDK layer, accelerate in-house builds, or make competing acquisitions. The developer experience that was frictionlessly multi-model is likely to fragment along provider lines within 12-18 months. Any strategy that assumes frictionless multi-model portability has an expiration date that shortened this week.

   Context matters here. OpenAI's $18B custom chip arrangement with Broadcom is reportedly hitting financing friction, and xAI is losing engineers to Cursor and others. Anthropic is well-capitalized and operationally steady, buying while the competition is constrained or distracted.

   ---

   The Three Real Options

   1. Deep commitment to a single ecosystem. Accept the lock-in, optimize for velocity within it
   2. Investment in an abstraction layer. Open-source or built in-house, accepting the engineering tax
   3. Enough internal capability to swap providers without rebuilding tooling each time

   The "best model for each task" posture was subsidized by neutral infrastructure. That infrastructure is being acquired. The cost of neutrality just went up, and firms that priced their multi-provider strategy on last year's assumptions will spend the next four quarters rediscovering what the new price is.

   What to do

   1. →

      Audit all production dependencies on Stainless-generated SDKs and shared AI developer tooling by end of this sprint

      NowYou need to know your exposure before Anthropic's ownership starts influencing roadmap priorities
   2. →

      Evaluate building or adopting an open-source model abstraction layer (LiteLLM, custom wrapper) within 60 days

      This sprintThe switching cost of multi-provider architectures just increased — locking in your own interface layer preserves optionality
   3. →

      Add SDK/tooling layer ownership to AI vendor risk assessment framework this quarter

      This quarterThis acquisition pattern will repeat — Google and OpenAI will make competing moves, and your assessment needs to account for infrastructure layer consolidation
2. 02

   The AI Productivity Gap Is Now Measurable — And It's Not the Story Your Board Is Hearing

   The Numbers That Challenge the Narrative

   The AI productivity thesis underwriting most 2026 enterprise budgets has a data problem. The tools work. That is not in dispute. What is missing, two years into the deployment cycle, is the aggregate evidence of firm-level P&L impact the thesis requires.

   Company	AI Claim	Actual Result
   Monday.com	"AI productivity" hiring freeze	Revenue growth halved: 27% → 19%
   Amazon	80%+ developer AI usage mandate	Staff gaming token leaderboards
   Spotify/Pinterest	AI efficiency gains	Computing costs hurting gross margins

   Monday.com is the case worth examining closely. A company that froze hiring and cited AI productivity while revenue growth halved is not telling an efficiency story. It is telling a demand story in an efficiency story's jacket. The stock is down 48% YTD despite beating expectations. The market is pricing the framing, not the caption.

   If AI were genuinely compounding output per employee, the expected pattern is flat hiring with revenue growth holding or accelerating. The observed pattern is flat hiring with revenue growth cut in half. Those are not the same story.

   Amazon's Goodhart's Law at Enterprise Scale

   Amazon, arguably the most metrics-driven company in technology, set an 80%+ developer AI usage target, stood up token consumption leaderboards, told employees this would not affect performance reviews, and watched staff game the system anyway because the managers were watching. That is Goodhart's Law at enterprise scale, inside the firm with the strongest measurement culture in the industry.

   The takeaway is narrow and useful. Input metrics such as tokens consumed, tools activated, sessions logged are close to useless when the objective is capability transformation. Deployment frequency, mean-time-to-resolution, and code review cycle compression are the outputs that move the P&L.

   The Acemoglu Baseline Holds

   A reasonable skeptic would point out that Daron Acemoglu's 2024 prediction that AI would barely move the productivity needle looked contrarian at the time. The reasonable skeptic is correct, and two years later the prediction is still the baseline. The firms with the heaviest AI deployment are not yet pulling away from the firms with the lightest. That separation is precisely what the productivity thesis predicts, and it is not in the data.

   The Real Cost Equation

   The honest equation is not that AI replaces headcount and the savings drop to the bottom line. It is that AI substitutes some headcount cost with compute cost, rewires the vendor dependency profile, and may or may not improve margins depending on usage. The labor line did not get cheaper. It moved to another firm's income statement, and that firm has pricing power the labor market never had.

   ---

   None of this makes the AI thesis wrong. It means the thesis has to be defended on a longer horizon than the one most 2026 budgets are written against. Boards that were patient in 2023 are not patient in the same way in 2026.

   What to do

   1. →

      Commission an independent AI ROI audit that separates genuine value creation from metric theater — map actual headcount savings against incremental compute costs by end of Q2

      This sprintYour board is receiving the narrative version, not the measured version. Monday.com shows what happens when the gap between the two becomes visible
   2. →

      Replace all input-based AI adoption metrics (usage, tokens, logins) with output-based metrics (cycle time, defect reduction, deployment velocity) before next board meeting

      This sprintAmazon's failure proves that input metrics produce gaming, not value — and your org is susceptible to the same dynamic
   3. →

      Stress-test your AI investment thesis against the Acemoglu scenario: productivity gains plateau at 'small boost' for 3+ more years

      This quarterIf the scenario holds, every AI capex decision needs a longer payback model than currently budgeted
   4. →

      Model compute cost trajectory alongside headcount reduction assumptions — present both curves to the board together

      This quarterThe margin story only works if compute cost growth stays below headcount savings — Monday.com, Spotify, and Pinterest all suggest it doesn't automatically
3. 03

   Agentic Commerce Infrastructure Is Forming Now — The Settlement Layer Decision Has a 2-Year Window

   Two Payment Giants Converged on Crypto Rails in the Same Quarter

   Google's Agentic Payments Protocol launched this quarter with 120+ partners including PayPal. Coinbase's x402 has processed 180 million agent payments since October 2025. The two are not competing with each other. They are competing with the traditional payment stack, and they are winning, because the traditional stack was never designed for counterparties that do not sleep.

   The structural reason is plain. AI agents cannot open bank accounts. They need programmable, permissionless, machine-readable rails, and the only mature option is stablecoins on crypto infrastructure. Google donating AP2 to the FIDO Foundation is the tell. The company is not trying to own the payment layer. It is trying to own the services that sit on top of it. That is the Android playbook, and the Android playbook worked the first time.

   Coinbase's Base is capturing 92.8% of agentic payment volume — the kind of share that produces winner-take-most outcomes in an infrastructure layer.

   The Regulatory Window Opened

   SEC Chairman Atkins is calling for onchain-native definitions rather than retrofitting existing law, and the CLARITY Act's stablecoin yield provisions have already pulled in $4.9B of institutional inflows in six weeks. S&P 500 member Corpay is settling on blockchain alongside SWIFT. The risk calculus has inverted. The old question was what happens if regulators shut this down. The current question is what happens to firms that arrive late to infrastructure their competitors already depend on.

   The Revenue Implication

   If McKinsey's $3-5T agentic market materializes and even twenty percent settles on stablecoin rails, Coinbase ends up in Visa's neighborhood, without the two-to-three-day settlement delay, weekend closure, or inability to serve non-human customers. The 20% machine-readable catalog figure says the window is still open. The 180 million payments already processed say it is closing.

   ---

   The Three-Part Audit

   Three questions are worth running, in order, for any organization with payments, commerce, or AI infrastructure exposure:

   1. Product surface: What percentage of revenue could flow through AI agent intermediaries within three years, and are the interfaces machine-readable today?
   2. Payment infrastructure: Can checkout and settlement serve a software agent holding a budget and a goal, not a human holding a card?
   3. Coinbase/Base positioning: Over the next three years, is this a critical dependency, a strategic partner, or a competitor?

   A reasonable skeptic would say the engineering tax of committing to a rail that is still consolidating is real. The reasonable skeptic is correct. The cost of arriving after the defaults have been set by AP2 and x402 shows up in the 2027 P&L, which is too late to argue about it.

   What to do

   1. →

      Model what percentage of your revenue could flow through AI agent intermediaries within 3 years — identify which products/services need machine-readable interfaces

      This quarterThe 20% catalog readiness figure means 80% of commerce surfaces are invisible to agents — if your interfaces are in that 80%, you're being excluded from the fastest-growing transaction channel
   2. →

      Evaluate USDC/stablecoin integration for B2B payment flows by Q3 — the regulatory window is open and enterprise precedent exists

      This quarterCorpay (S&P 500) is already settling on-chain. First-mover advantage in your vertical is available for months, not years
   3. →

      Add Coinbase/Base to board-level strategic watchlist — their 92.8% agentic share makes them either critical partner or chokepoint

      This quarterWinner-take-most dynamics in infrastructure layers are fast — by the time the share is visible to your board, the negotiating window is closed
   4. →

      Brief product and engineering on AP2 protocol and x402 standard within 30 days

      This sprintGoogle donating AP2 to FIDO Foundation means this becomes a standard, not a product — early integration shapes how the standard serves your use case
4. 04

   Your CI/CD Pipeline Is Under Coordinated Attack — TeamPCP's Three-Month Campaign Demands Immediate Response

   A Systematic Campaign, Not Isolated Incidents

   TeamPCP has been running the same play against different surfaces since February 2026. First Trivy in the supply chain. Then GitHub Actions and OpenVSX extensions in March. Now the Checkmarx Jenkins AST Scanner plugin, distributed through the official Jenkins Marketplace. Call it opportunism if you like; the pattern says otherwise. This is a group that has decided build pipelines are the target and is working through the catalog methodically.

   Running in parallel, though from different actors:

   • An npm worm hit 169 package names including packages adjacent to Mistral and TanStack, bypassing trusted publishing, the mechanism most organizations treated as the integrity backstop
   • The TanStack compromise chained GitHub Actions vulnerabilities to exfiltrate npm publish credentials, then injected malware into 84 package versions across 42 packages with 12M+ weekly downloads
   • Two Linux kernel privilege escalation zero-days landed in two weeks, both with public exploit code before patches. Microsoft confirmed in-wild exploitation of Dirty Frag, including container escape
   • A critical Ollama zero-day exposes heap memory from 300K internet-exposed servers via 3 unauthenticated API calls

   The Jenkins plugin compromise gives the attacker the credentials. The kernel exploits give them the host. Together they describe complete compromise of the build and deployment pipeline. This is operational, not theoretical.

   Why This Is Different From Prior Supply Chain Alerts

   Trusted publishing was bypassed. The mechanism most organizations rely on for npm supply chain integrity has been proven circumventable; the attack weaponizes GitHub's optionalDependencies and prepare hooks to mint valid tokens. A reasonable skeptic would point out that every backstop eventually gets bypassed and the right response is patience. The reasonable skeptic is correct about patience and wrong about this specific backstop, because the security model did not assume trusted publishing was one layer among several. It assumed trusted publishing was the layer.

   The Compound Threat Model

   A foothold in the build system plus a reliable local escalation primitive on the hosts that run it equals compromise of the entire build and deployment pipeline. The affected Linux kernel set — Ubuntu, RHEL, CentOS Stream, AlmaLinux, Fedora, openSUSE, OpenShift — is essentially every production Linux footprint that matters. Microsoft explicitly calls out a container escape vector in Dirty Frag, which invalidates the specific isolation assumption that a compromised workload cannot reach the host kernel.

   Then the Ollama zero-day. Any engineering team running local LLM inference without IT visibility has an active exfiltration risk: heap memory containing user prompts, API keys, proprietary code, and customer contracts is retrievable via three API calls.

   What to do

   1. →

      Audit all CI/CD pipeline plugins and update mechanisms immediately — specifically Jenkins marketplace plugins, GitHub Actions, and VS Code extensions. Determine if Checkmarx Jenkins AST Scanner version 2026.5.09 was pulled during the exposure window

      NowTeamPCP has been running since February and the Jenkins compromise is backdoored in production if auto-update was enabled
   2. →

      Rotate every secret reachable from CI/CD runners this week — container registry credentials, cloud provider keys, artifact repository tokens, and deployment targets

      NowIf any affected plugin was consumed, credentials are already exposed — rotation is the only mitigation
   3. →

      Scan for and disable exposed Ollama instances across all developer workstations and shadow IT by Friday

      Now300K servers exposed globally, your developers likely deployed instances without security review — active exfiltration via 3 API calls
   4. →

      Implement kernel module hardening — disable vulnerable esp/xfrm and rxrpc modules on all Linux hosts where not required, accelerate kernel patching to sub-24-hour for critical vulns

      This sprintPublic PoC exploit code means script-kiddie-level exploitation is possible, container escape confirmed in-wild
   5. →

      Establish cryptographic build attestation for all CI/CD outputs within 90 days — evaluate Kettle (hardware-enclave verification) or Sigstore equivalents

      This quarterTrusted publishing has been bypassed — the next integrity layer requires cryptographic attestation, not marketplace trust