We only publish what we can defend in a vendor meeting. Every claim carries an ID, a review date, and a verdict you can check.
- Our ledger194
- Holding182
- Partial06
- Not holding06
- Industry claims tracked26
- Last reviewtoday
Quiet — no verdict transitions in the last 30 days. See the ledger →
Agent Mode AI — claim-tracked agentic AI analysis
Why AI productivity gains create workforce reduction pressure: the demand ceiling and the competitive trap
The argument that AI-driven productivity lets companies keep all their workers and simply produce more runs into two hard limits: consumer demand and competitive dynamics. Both constraints are structural, operating regardless of management intent, and both resolve in the same direction: fewer workers for the same revenue.
27 years enterprise IT operations. Global organisation. Major incidents. Editorially independent.
- 116pieces
- 194tracked claims
- 14public retractions
The Enterprise Agentic Governance Benchmark. Six dimensions, scored 0–100. Free 5-minute web diagnostic; 30–45 minute Excel for governance groups.
Recently reviewed
Three claims most recently re-tested against their primary sources. Status changes log to the corrections page; nothing quietly vanishes.
- AM-133HoldingQ3 2026 Claim Review Bulletin: which claims moved, which held, and what the EU AI Act enforcement window did to the corpusReviewed 30 Jul 2026Read article →
- OPS-076HoldingPicking an agent protocol when you are a 6-person agency: MCP, A2A, Llama Stack, and the rule that keeps your tool inventory portableReviewed 24 May 2026Read article →
- OPS-075HoldingThree signs your small team has approved-tool, unapproved-capability shadow AI. Plus the 60-minute audit that catches itReviewed 24 May 2026Read article →
Why this publication has a ledger
Most AI commentary gets paid for being loud about what's new. Almost none gets measured on whether what it said last quarter still holds this one. That is the gap this publication exists to close. Every published argument carries an ID, a review date, and one of three verdicts — Holding, Partial, or Not holding — that updates over time as evidence accumulates. The verdict log is the product.
When a claim stops holding, the page says so. The original sentence stays visible. The correction is dated and appended. Nothing is quietly removed. You do not need to trust the author to trust the verdicts — the receipts are public, on a 30–90 day review rhythm, and the corrections record is permanent.
Two registers
Same Holding-up disciplineMid-market and large enterprise. Procurement, governance, EU AI Act, multi-vendor agentic stacks. 30–90 day claim review cadence.
No IT department. Practitioner-advisory voice; faster 30–45 day cadence. Tools, vendor red flags, hours-per-week evaluation budgets.
Topic pillars
Five clusters- 3 articlesNon-human identity
How enterprise IT manages AI agents as first-class identities — lifecycle, credentials, procurement clauses, audit.
- 30 articlesAgent procurement
The contracts, SLAs, and evaluation criteria that distinguish agentic-AI procurement from SaaS procurement.
- 3 articlesShadow AI discovery
Detecting unauthorised agentic-AI deployments inside the enterprise — telemetry patterns, inventory methods, policy response.
- 48 articlesAgentic AI governance
Governance frameworks, oversight patterns, and compliance postures for enterprise agentic-AI deployment.
- 19 articlesEnterprise AI cost
Verifying, tracking, and challenging the ROI claims vendors and analysts make about enterprise agentic AI.
Editor's picks
One per topic cluster- Governance90 days to EU AI Act enforcement: what the corpus says enterprises still haven't done
- Cost economicsThe hidden costs of agentic AI: a CFO's guide to true TCO and ROI modeling
- SecurityClaude Mythos: what 'too dangerous to release' means for your risk appetite and cyber posture
- ArchitectureNon-human identity for AI agents: the 2026 IAM playbook
- StrategyWhy 88% of agentic AI deployments fail
Latest pieces
Full archive →The agent protocol tax: MCP, A2A, and Llama Stack are not converging. Your tool inventory is the locked asset
Anthropic's Model Context Protocol reached broad client and server adoption through 2025. Google's Agent2Agent protocol moved to the Linux Foundation later the same year. Meta's Llama Stack consolidated its agent-runtime spec on a separate track. Microsoft's Copilot Agent platform and Salesforce's Agentforce maintain proprietary surfaces. The three open protocols are not converging on a single standard, and the four major proprietary surfaces are not adopting any of them as default. The cost of being wrong on the model choice is low. The cost of being wrong on the protocol choice is high, because the locked asset is not the agent code, it is the tool inventory the agents call.
What SAP's 50 Joule agents at Sapphire 2026 mean for CIOs making ERP renewal decisions
SAP's Sapphire 2026 keynote introduced the Autonomous Enterprise vision: 50-plus domain-specific Joule AI Assistants embedded across finance, supply chain, procurement, HR, and CX, orchestrating more than 200 specialised agents. Anthropic's Claude powers the finance, procurement, and supply chain Joule agents. RISE with SAP customers receive a contractual commitment to activate three Joule Assistants in year one. SAP GROW customers get 20-plus from day one. The ERP renewal calculus has changed. The AI agent layer is no longer an add-on evaluation; it is inside the contract.
97 percent invest, 5 percent are ready: why enterprise AI data readiness is a budget allocation problem
Dun and Bradstreet's 2026 AI Momentum Survey of 10,000 businesses across 32 countries found that 97 percent of organisations report active AI initiatives, but only 5 percent say their data is adequately ready to support them. That gap is not primarily a technology problem. Most enterprise data environments were built for human workflows, not for autonomous AI systems operating continuously across mission-critical processes. The gap between initiative volume and data readiness is a budget-allocation failure: enterprises that treat data infrastructure as the prerequisite spend rather than a parallel track are the ones that reach scale. Enterprises that treat it as a follow-on investment do not.
Anthropic-Microsoft Maia chip talks: what the May 21 disclosure means for enterprise AI infrastructure procurement
On 21 May 2026, CNBC and Bloomberg reported that Anthropic is in early talks with Microsoft to adopt its Maia 200 AI chips for inference workloads. The Maia 200 is Microsoft's custom silicon, announced in January 2026, which Satya Nadella described in April as delivering over 30 percent improved tokens per dollar versus commodity Nvidia hardware. On the same day, a SpaceX filing disclosed that Anthropic will pay 1.25 billion dollars per month through May 2029 for computing power. The two disclosures read together describe a foundation-model inference stack that is visibly diversifying from commodity Nvidia hardware to hyperscaler-proprietary silicon. Enterprise CIOs managing AI procurement agreements have a new field to add to their vendor questionnaires.
Karpathy joins Anthropic's pre-training team: what the May 19 hire signals for CIO vendor-trajectory models
Andrej Karpathy announced on Tuesday 19 May 2026 that he has joined Anthropic. Anthropic confirmed he will lead a team focused on using Claude to accelerate pre-training research, working under Nick Joseph on the pre-training team. The trade-press framing is the hiring coup. The CIO framing is different. Karpathy's specific mandate — applying Claude to the work of building the next Claude — is the load-bearing signal. It indicates Anthropic is betting on recursive self-improvement of its model line at the foundational layer, not just at the application layer. For enterprises sizing multi-year platform commitments, that materially changes the vendor-trajectory model on which the commitment rests.
Prompt injection just crossed the RCE threshold: what the May 2026 Semantic Kernel and MCP CVEs mean for enterprise AI agent frameworks
Microsoft Security Response Center disclosed two Semantic Kernel CVEs on 7 May 2026 in which a single attacker-controlled prompt resolves to host-level code execution. The same week, OX Security published a configuration-to-command path in Anthropic's MCP STDIO interface that traverses every published MCP server implementation. Windsurf 1.9544.26 carries a separate prompt-injection-to-MCP-registration path that automatically installs a malicious server with no user interaction. Three independently-disclosed CVE classes in a single fortnight, all at the framework layer rather than the deployment layer, are not a coincidence. They map a structural property of how 2026 agent frameworks treat tool-configuration data, and the operational implication for enterprise architecture is larger than any single patch.
The EU AI Act high-risk readiness gap: the budget reality enterprises haven't sized
The high-risk-system obligations of the EU AI Act activate on 2 August 2026, under 80 days from the publication date of this piece. Most enterprise conversations about readiness still treat the gap as a legal-interpretation problem to be solved by the general counsel and outside counsel. The operational evidence from procurement, audit, and headcount data argues a different reading. The gap is not legal interpretation; it is a budget gap on a class of operating expense the chief financial officer has not yet sized: conformity-assessment headcount, audit-evidence pipeline infrastructure, model-card production cadence, and post-market monitoring telemetry. The €15 million or 3% of worldwide annual turnover figure in Article 99(4) is the worst-case downside. The mid-case downside is the operating cost of carrying the readiness gap through 2027, which most enterprises have not modelled.
Anthropic's 10 Wall Street agents: what CIOs at non-finance firms should read into the May 2026 launch
Anthropic announced 10 financial-services agents and a Moody's data partnership on 5 May 2026, with full Microsoft 365 integration. The Wall Street launch is the most visible move in a six-month pattern of vertical-specialised agent stacks shipping from horizontal AI vendors. The CIO question at a non-finance enterprise is not whether to adopt the financial-services product; it is what the launch signals for procurement strategy when the same vendor cohort begins shipping vertical stacks for healthcare, legal, manufacturing, and public sector through H2 2026. The structural read on whether vertical-specialised agent stacks become the procurement default or remain a finance-specific anomaly determines whether a 2026 multi-year platform commitment to a horizontal stack is the right bet or the wrong one.
Browse by topic pillar
Five strategic pillarsComing next
Peter's editorial calendar — honest dates, bumped-with-notes if missed.- Week 1726 Apr 2026Non-human identity — the first procurement question CIOs aren't asking yet
Every enterprise agent deployment passes through a credential. Most teams still hand the agent a human's credential. Naming the NHI gap is the next Q2 procurement conversation.
- Week 1803 May 2026Shadow agent sprawl — what telemetry catches and what it misses
The browser-as-agent-runtime pattern creates a detection gap that MDM/CASB don't see. What the first wave of shadow-AI discovery tools actually find, and the three categories they miss.
- Week 1910 May 2026The AI agent MSA — four clauses every enterprise contract needs by August
EU AI Act enforcement activates 2 Aug 2026. The clauses that survive legal review in the next quarter will be the ones that don't pretend the agent is conventional SaaS.