• Why IT operations is the highest-exposure agentic-AI workforce population
    May 10 2026
    Episode 13 of Agent Mode AI. Abby and Avery walk AM-012, the claim that the enterprise IT operations workforce is structurally the highest-exposure population to autonomous-action AI. The task surface that defines the family — incident triage, configuration management, ticket processing, routine diagnostics, scripted remediation — maps onto the agent-class capability boundary more directly than any other large enterprise job-family. The US Bureau of Labor Statistics Occupational Outlook Handbook projects Computer and Information Technology occupations to grow faster than average through 2033 with substantial role-mix shifts inside the family. The World Economic Forum Future of Jobs Report 2025 reads the same job-family bimodally: routine-task sub-population in the displacement cohort, AI-adjacent sub-population in the creation cohort, 2030 horizon. Anthropic chief executive officer Dario Amodei's twenty-eighth of May 2025 Axios interview projected that AI could eliminate half of entry-level white-collar jobs over the next one to five years. The procurement-deck distinction is between the agent-orchestration posture (team scales toward managing fleets of agents) and the agent-replacement posture (team contracts through churn). Sources cited: - US Bureau of Labor Statistics Occupational Outlook Handbook, Computer and Information Technology occupations, 2023-2033 cycle - World Economic Forum Future of Jobs Report 2025 - Dario Amodei interview with Axios, 28 May 2025 - McKinsey "Seizing the agentic AI advantage" workforce findings - Atlanta Federal Reserve Workforce Currents data on AI-skill wage premium Claims tracked: - AM-012 — IT operations as highest-exposure workforce population — agentmodeai.com/holding/?claim=AM-012 - AM-006 — Atlanta Fed wage-premium and BCG frontline access gap — agentmodeai.com/holding/?claim=AM-006 - AM-010 — Chief information officer playbook five operational characteristics — agentmodeai.com/holding/?claim=AM-010 - AM-011 — Change-management variable in deployment success — agentmodeai.com/holding/?claim=AM-011 Newsletter and the full Holding-up ledger: agentmodeai.com
    Show More Show Less
    12 mins
  • What the Anthropic Claude for Chrome disclosure tells procurement
    May 10 2026
    Episode 12 of Agent Mode AI. Abby and Avery walk AM-009, the claim that Anthropic's Claude for Chrome launch is a procurement-decision data point about the maturity of the browser-resident agentic AI class rather than about Anthropic specifically. The published security disclosure on the launch reports a twenty-three point six percent prompt-injection success rate pre-mitigation, eleven point two percent post-mitigation, and zero percent on URL-injection variants after subsequent patches, against a defined attack corpus. The procurement-relevant signal is the published-disclosure posture itself, which places Anthropic in Cohort A under the AM-007 vendor-response-split framework. Brave Software's adjacent research on Comet confirms the prompt-injection class is structural to browser-resident agents rather than Anthropic-specific. The episode concludes with five questions a chief information officer and chief information security officer can require answered in writing before authorising browser-agent pilots. Sources cited: - Anthropic Claude for Chrome announcement, 26 August 2025 - Anthropic published security disclosure on Claude for Chrome - Brave Software research on Comet prompt injection - Simon Willison agentic-browser-security commentary, 25 August 2025 - Zenity Labs AgentFlayer research, Black Hat USA 2025 - EchoLeak CVE-2025-32711, disclosed August 2025 Claims tracked: - AM-009 — Claude for Chrome procurement-grade disclosure pattern — agentmodeai.com/holding/?claim=AM-009 - AM-007 — AgentFlayer cross-agent prompt-injection class vendor-response split — agentmodeai.com/holding/?claim=AM-007 - AM-146 — Three accuracy-disclosure questions for procurement — agentmodeai.com/holding/?claim=AM-146 Newsletter and the full Holding-up ledger: agentmodeai.com
    Show More Show Less
    10 mins
  • The seven AI vendor exit clauses that decide whether you can leave
    May 10 2026
    Episode 11 of Agent Mode AI. Abby and Avery walk AM-145, the claim that AI vendor switching in 2026 is bound primarily by contract terms — exit clauses, data-portability obligations, model-deprecation rights — not by technical migration cost. Three forces drive the 2026 procurement story: vendor consolidation (ServiceNow completing the Moveworks acquisition in December 2025, Automation Anywhere closing the Aisera acquisition on the eleventh of November 2025), model-deprecation cadence becoming a recurring contract event, and the first wave of multi-year enterprise agentic AI contracts approaching renewal. Seven clause families repeatedly create the lock-in most enterprises only discover at year two: data-portability scope, model-deprecation rights, sub-processor expansion, output-IP ambiguity, pricing-tier rebalancing, agent-uptime SLA definition gaps, and audit-evidence retention obligations. Article 16 of the EU AI Act applies to deployers from the second of August 2026 with a six-month log retention floor. Sources cited: - ServiceNow announcement on completion of Moveworks acquisition - Automation Anywhere announcement on completion of Aisera acquisition - OpenAI deprecation page - Anthropic model lifecycle policy - Google Vertex AI model versioning page - Microsoft Azure OpenAI model retirement policy - Microsoft Customer Copyright Commitment - Bloomberg report on Klarna, 8 May 2025 - EU AI Act Articles 12 and 16 Claims tracked: - AM-145 — Seven AI vendor exit clauses — agentmodeai.com/holding/?claim=AM-145 - AM-027 — Vendor contract gotchas — agentmodeai.com/holding/?claim=AM-027 - AM-046 — EU AI Act Article 12 audit-evidence template — agentmodeai.com/holding/?claim=AM-046 - RES-005 — AI MSA Red-Team Checklist Newsletter and the full Holding-up ledger: agentmodeai.com
    Show More Show Less
    11 mins
  • What vendor "successful pilot" references do not tell procurement
    May 10 2026
    Episode 10 of Agent Mode AI. Abby and Avery walk AM-140, the claim that vendor "successful pilot" references transfer to scaled production at roughly the McKinsey twenty-three percent rate, and that the gap is operational rather than capability-driven. The McKinsey State of AI 2025 survey, published November 2025 with sample size one thousand four hundred ninety-one, is the anchor data point. The Klarna seven-hundred-agent reversal reported by Bloomberg on the eighth of May 2025, the Salesforce Agentforce two-hundred-customer reality through Q1 2026, and the GitHub Copilot token-counting bug acknowledged in April 2026 are the documented walk-backs that bound what reference language can credibly imply. CRMArena-Pro thirty-five percent multi-step reliability and the EchoLeak CVE cross-agent class are the structural failure-mode evidence. Six pre-pilot questions for the procurement committee close the gap. Sources cited: - McKinsey State of AI 2025, published November 2025, n=1,491 - Bloomberg report on Klarna, 8 May 2025 - The Information report on Salesforce Agentforce, April 2025 - GitHub Copilot changelog, 18 April 2026 - CRMArena-Pro paper, Salesforce AI Research, August 2025 - Carnegie Mellon TheAgentCompany academic benchmark - EchoLeak CVE-2025-32711, disclosed August 2025 Claims tracked: - AM-140 — Vendor pilot reference to procuring-enterprise scaled production transfer rate — agentmodeai.com/holding/?claim=AM-140 - AM-030 — McKinsey 23% from IT-leader perspective — agentmodeai.com/holding/?claim=AM-030 - AM-128 — MIT 95% pilot-failure claim — agentmodeai.com/holding/?claim=AM-128 Newsletter and the full Holding-up ledger: agentmodeai.com
    Show More Show Less
    10 mins
  • The three questions every CIO should ask about a vendor accuracy claim
    May 10 2026
    Episode 9 of Agent Mode AI. Abby and Avery walk AM-146, the claim that vendor "ready-to-run" positioning without named task, named baseline, and named methodology is procurement-deck noise rather than procurement evidence. The procurement-grade reference shapes in 2026 are the academic-benchmark layer (CRMArena-Pro 35% multi-step reliability, CMU TheAgentCompany 30-35% reproduction range, WebArena ~36% browser-agent ceiling, SWE-bench Verified for code generation) and the Anthropic Claude for Chrome disclosure pattern (23.6% pre-mitigation, 11.2% post, 0% on URL-injection variants after patches). A third class — the named-customer audited deployment, with McKinsey Lilli, JPMorgan, BT Now Assist, and UK Government Digital Service as the canonical references — sits alongside. Sources cited: - CRMArena-Pro paper, Salesforce AI Research, August 2025 - Carnegie Mellon TheAgentCompany academic benchmark - WebArena academic benchmark - SWE-bench Verified - Anthropic published security disclosure on Claude for Chrome, 26 August 2025 - McKinsey internal Lilli platform deployment data - JPMorgan Chase 2023 AI value disclosure - BT Now Assist deployment, Hena Jalil - UK Government Digital Service Q4 2024 Claims tracked: - AM-146 — Three accuracy-disclosure questions for procurement — agentmodeai.com/holding/?claim=AM-146 - AM-009 — Claude for Chrome procurement-grade disclosure pattern — agentmodeai.com/holding/?claim=AM-009 - AM-140 — Procurement-committee pre-pilot questions — agentmodeai.com/holding/?claim=AM-140 Newsletter and the full Holding-up ledger: agentmodeai.com
    Show More Show Less
    12 mins
  • Which LLM provider actually stays up?
    May 8 2026
    Episode 8 of Agent Mode AI. Abby and Avery walk AM-136, the foundation- model uptime track-record claim. Twenty-four-month operational record across Anthropic, OpenAI, Google, AWS Bedrock, and Azure OpenAI. Why the status pages do not tell the procurement team what they need to know. The SLA-credit gap that almost every enterprise customer discovers only after their first incident. Three multi-provider routing patterns. Three contract language additions every 2026 enterprise renewal MSA should require. Sources cited: - status.anthropic.com (Anthropic incident reports) - status.openai.com (OpenAI incident reports) - status.cloud.google.com (Google Cloud / Gemini API) - health.aws.amazon.com (AWS Service Health Dashboard) - status.azure.com (Azure / Azure OpenAI) - LiteLLM, OpenRouter, Portkey project documentation Claims tracked: - AM-136 — Foundation-model uptime SLA track record — agentmodeai.com/holding/?claim=AM-136 Related claims: - AM-026 — The 60-question agentic AI RFP - AM-138 — Vendor MSA renewal post-EU-AI-Act-enforcement - AM-123 — Agent observability stack Newsletter and the full Holding-up ledger: agentmodeai.com
    Show More Show Less
    14 mins
  • Why 88% of agentic AI deployments fail
    May 8 2026
    Episode 7 of Agent Mode AI. Abby and Avery walk the four datasets that document the bimodal ROI distribution in enterprise agentic AI: AM-029 on the Stanford Digital Economy Lab 12/88, AM-132 on the restored bimodal framing, AM-128 on the MIT NANDA GenAI Divide 95% finding, and AM-053 on the McKinsey State of AI 2025 17% EBIT-attribution. Then the GAUGE framework — six dimensions that distinguish the 12% high-performing cohort from the 88% struggling body. Governance, audit substrate, use-case maturity, guardrails, evidence baseline, exit posture. Sources cited: - Stanford Digital Economy Lab Enterprise AI Playbook 2026 (Pereira, Graylin, Brynjolfsson) - McKinsey State of AI 2025 (n=1,993, November 2025) - MIT NANDA State of AI in Business 2025 (Project NANDA / MIT Connection Science, August 2025) - Gartner Q1 2026 Infrastructure & Operations Survey - Fortune coverage of MIT NANDA findings, August 2025 Claims tracked: - AM-029 — Why 88% of agentic AI deployments fail — agentmodeai.com/holding/?claim=AM-029 - AM-132 — The bimodal ROI distribution in enterprise agentic AI — agentmodeai.com/holding/?claim=AM-132 - AM-128 — The MIT 95% GenAI-pilot-failure claim — agentmodeai.com/holding/?claim=AM-128 - AM-053 — The McKinsey 17% EBIT claim — agentmodeai.com/holding/?claim=AM-053 Newsletter and the full Holding-up ledger: agentmodeai.com
    Show More Show Less
    13 mins
  • What changes for enterprise AI on 2 August 2026
    May 8 2026
    Episode 6 of Agent Mode AI. Abby and Avery walk the four claims that interlock around the 2 August 2026 EU AI Act deployer-obligations enforcement window. AM-127 is the falsifiable prediction (three of four operational claims will downgrade by 1 October 2026). AM-135 is the Article 50 transparency UX with chatbot disclosure, generative AI watermarking, biometric notification, and deepfake disclosure. AM-138 is the post-enforcement MSA red-team — three new clause families covering Article 11 technical-file pass-through, Article 16 post-market monitoring support, and Article 26 deployer-documentation supply. AM-046 is the fourteen-field Article 12 audit substrate that the other three obligations feed into. Sources cited: - EU AI Act consolidated text (Regulation 2024/1689) - EU AI Office implementing guidance, 2026 - C2PA Content Credentials specification - Google SynthID documentation - Adobe Content Authenticity Initiative - European Data Protection Board opinion on AI models, 2024 - National supervisory authority enforcement decisions, Q1-Q2 2026 Claims tracked: - AM-127 — Deadline-anchored prediction on operational vs governance claims — agentmodeai.com/holding/?claim=AM-127 - AM-135 — EU AI Act Article 50 transparency disclosure UX — agentmodeai.com/holding/?claim=AM-135 - AM-138 — Vendor MSA renewal post-EU-AI-Act-enforcement — agentmodeai.com/holding/?claim=AM-138 - AM-046 — EU AI Act Article 12 audit-evidence template — agentmodeai.com/holding/?claim=AM-046 Newsletter and the full Holding-up ledger: agentmodeai.com
    Show More Show Less
    16 mins