# AINA §06 ONE-CALL TECHNICAL BRIEF — Rollback Is Not Erasure: Dual-Tier Vaults and Ungated Quarantine Canonical: https://blayneaina.com/06/brief/ | Full Article: https://blayneaina.com/06-rollback-is-not-erasure-dual-tier-vaults-and-ungated-quarantine/ | Raw Markdown: https://blayneaina.com/06.md | All §01–§09 Master Brief: https://blayneaina.com/ai-brief.txt Nav: PrevBrief=https://blayneaina.com/05/brief.txt | NextBrief=https://blayneaina.com/07/brief.txt | Site=https://blayneaina.com/ | Repo=https://github.com/SquadForge/blayne.aina | Contact=me@blayneaina.com Executive Summary: Problem: A single undo snapshot can destroy intermediate states and launder unauthorized writes into a clean baseline. | Proves: Primary certifies operational recovery while Amber preserves every intermediate and ungated state for forensics. | Scope: Use the Forensic Baseline & Quarantine Challenge on one file exposed to out-of-band edits. Parts (3): Part 1: https://blayneaina.com/06-rollback-is-not-erasure-dual-tier-vaults-and-ungated-quarantine/part-1/ (raw: https://blayneaina.com/06/part-1.txt) | Part 2: https://blayneaina.com/06-rollback-is-not-erasure-dual-tier-vaults-and-ungated-quarantine/part-2/ (raw: https://blayneaina.com/06/part-2.txt) | Part 3: https://blayneaina.com/06-rollback-is-not-erasure-dual-tier-vaults-and-ungated-quarantine/part-3/ (raw: https://blayneaina.com/06/part-3.txt) - Introduction & Thesis [Part 1/3]: # Rollback Is Not Erasure: Dual-Tier Vaults and Ungated Quarantine A backup can restore a clean state. It cannot explain what happened afterward. Recovery needs a certified baseline and a separate forensic history. By Blayne Aina · Principal Systems Architect and creator of… — Key Rules/Claims: a trusted operational baseline for recovery; | an evidence-preserving account of every intermediate and ungated state for forensics. - 1. Why Single-Tier Undo Fails [Part 1/3]: Subtopics: Failure 1: The baseline is overwritten by the task itself; Failure 2: Ungated content becomes a trusted post-edit state — Single-slot backup systems fail in two distinct ways. The task has an undo button but no state 0 left. Worse, it cannot explain how state 3 was reached or which intermediate state was valid. - 2. The Dual-Tier Separation [Part 1/3]: Subtopics: Exhibit 6.1 — Dual-tier operational separation — Primary and Amber are not two copies of one backup. They answer different questions and have different failure and custody properties. Primary is the bounded operational store for rapid rollback. - One Checkout, Six Mutations, Two Truths [Part 1/3]: Consider one file checked out for remediation: The result is deliberately two truths: the file can return to a trusted baseline, while the evidence retains every intermediate and ungated state. — Key Rules/Claims: Certified checkout. The lease and kernel handle are acquired. State 0 is written to Primary with its sidecar and capture-ledger binding, and archived to Amber with exact readback. If any step fails, both lease and handle are released. - 3. Primary: A Certified Operational Baseline [Part 1/3]: Subtopics: Scope sharding and identity; Monotonic version filenames; Readback before trust; Durable version binding; Exhibit 6.4 — A valid Primary capture binding — A file on disk in the Primary directory is not a baseline yet. It becomes one only after its bytes, sidecar, scope identity, and durable capture binding all verify. Each canonical file scope maps to .squad/vault/ /. — Key Rules/Claims: every nonempty line must parse; | the destination must name the selected version exactly; | the record's canonical scope must resolve to the same file; | duplicate or conflicting bindings are refused; | digest, byte count, owner, and RFC 3339 timestamp must be well formed. - 4. Amber: Content-Addressed Forensic Objects [Part 1/3]: Subtopics: Atomic creation, deduplication, and exact readback — Amber stores raw bytes under: The first two digest characters create 256 shard directories. There is no Zstandard or .zst container. Raw bytes eliminate codec selection from the recovery trust boundary and make the content address itself the object's identity. — Key Rules/Claims: event: "amber_archived"; | capture kind, canonical scope and absolute source identity; | owner and intent; | SHA-256 and raw byte count; | timestamp and deduplication status. - 5. Fail-Closed Checkout Capture [Part 1/3]: Subtopics: Exhibit 6.2 — Fail-closed checkout capture state machine; Exhibit 6.5 — Checkout failure revokes tenancy — Checkout is a state machine, not a best-effort backup call. The lease and kernel handle are acquired first so the source cannot be casually changed during capture. Any failure in storage, sidecar verification, Amber persistence, ledger append, or binding replay releases both. - 6. Per-Mutation Amber Accumulation [Part 1/3]: Subtopics: Exhibit 6.6 — Amber edit snapshot — snapshot_edit_state captures the current bytes before a governed mutation and archives them only to Amber with kind: "edit_snapshot". Primary remains the state-0 undo baseline. - 7. The Active Bypass Sentinel [Part 2/3]: Subtopics: Exhibit 6.7 — bypass_detected — A guarded file can still be changed by a process outside the tool path. The active bypass sentinel scans active File leases and cross-indexes three observations: The bypass condition is: Path spellings are normalized so a junction, case variant, or slash variant cannot make a… — Key Rules/Claims: the lease's started_at timestamp; | the latest gated write found in snapshot.jsonl and file_edits.jsonl; | the file's current filesystem modification time. - 8. Release Verification and Ungated Quarantine [Part 2/3]: Subtopics: Exhibit 6.3 — Release verification and quarantine flow; Exhibit 6.8 — Release quarantine receipt — Release checks live on-disk bytes against the last authorized state. If a gated write occurred under the lease, the expected value is its post_sha256; otherwise the expected value is the checkout's pre-write FNV-1a hash and byte count. - 9. Restoration Is Another Governed Mutation [Part 2/3]: Subtopics: Governed restore; Console-exclusive operator rescue — A restore does not travel backward through history and delete the unauthorized act. It creates a new, evidence-bound transition from current state to a verified prior state. - 10. The Local-History and Non-Erasure Ceilings [Part 2/3]: Subtopics: Artifact integrity; Artifact survival; Downstream irreversibility — Recovery has three distinct assurance properties that must not be collapsed. SHA-256 and capture binding prove that stored bytes still match the evidence recorded for them. This detects substitution, corruption, and misleading provenance. — Key Rules/Claims: an external API or webhook already dispatched; | a database query or third-party sync already committed; | confidential content already read or disclosed by another process; | another agent's reasoning, notifications, or subsequent state transitions already caused by the modified state. - 11. The 2026 Recovery Evidence Landscape [Part 2/3]: The strongest 2026 sources support independent interception, out-of-band supervision, and tamper-evident forensic records. They do not justify pretending that local rollback erases global consequences. — Spec/Table: Shu, Boundary-State Control for Tool-Using Language-Model Agents (https://arxiv.org/abs/2609.37475), September 2026 preprint; What it actually establishes: BSC-R binds a single-use commit authorization to the exact action and semantic authorization state, rejecting represented changed and replayed classes while still committing 25% of invalid effects in the broader external suite.; How the recovery… - The Forensic Baseline & Quarantine Challenge [Part 2/3]: The Forensic Baseline & Out-of-Band Mutation Quarantine Challenge exercises the complete sequence: certified checkout, several Amber-accumulated edits, an out-of-band mutation, release-time mismatch, and a governed restoration. - The Twelve Recovery Claims [Part 2/3]: Spec/Table: 06-C01; Bounded claim: FNV-1a scope sharding and meta.json bind Primary directories to canonical file identity; Evidence and ceiling: Implemented and author-verified; mismatched saved scopes are refused | 06-C02; Bounded claim: Monotonic version names and create-new synced writes prevent accidental overwrite; Evidence and ceiling: Implemented and author-verified; collisions fail instead of reusing an… - The Article 06 Claim Card [Part 3/3]: Key Rules/Claims: Mechanism: | AINA Dual-Tier Recovery and Forensic Quarantine | (Primary certified baselines, Amber content-addressed objects, | fail-closed checkout, version replay, per-edit snapshots, | bypass sentinel, release verification, and governed restore) | Failure it governs: | Single-slot undo destroying the original baseline; | uncertified files impersonating recovery images; | out-of-band writes laundered into legitimate post-edit state; | silent rollback destroying evidence and obscuring downstream consequences. - The Baseline Is Only Half the Recovery Story [Part 3/3]: A trusted recovery image matters. So does the record of why it was needed. The dual-tier architecture preserves both. Primary certifies the state to restore. Amber preserves every state the system passed through, including the state nobody authorized. - Frequently Asked Questions [Part 3/3]: Subtopics: Why is rollback not erasure?; What makes a Primary version a certified baseline?; Why keep two vaults instead of one backup?; Does bypass_detected prove every out-of-band write was seen?; What happens when release content does not match the last gated state?; Can recovery undo external API calls or disclosures? — Rollback changes current bytes to a prior state. It does not remove the fact that an action occurred, erase downstream reliance, or eliminate the need to investigate it. A governed recovery preserves both the restored baseline and the complete forensic history. - Continue the Series [Part 3/3]: Key Rules/Claims: Series index: From Proposal to Consequence: The AINA Transition-Governance Series (https://blayneaina.com/) | Previous: Article 05 — Expiry Is Not Fencing: Typed Leases and Kernel Write Exclusion (https://blayneaina.com/05-expiry-is-not-fencing-typed-leases-and-kernel-write-exclusion/) | Next: [Article… - Primary 2026 Sources [Part 3/3]: Key Rules/Claims: Shu — Boundary-State Control for Tool-Using Language-Model Agents, arXiv:2609.37475 (https://arxiv.org/abs/2609.37475) | Pino — Hard Stop: Kernel-Level Preemption and Containment for Rogue Agentic Execution, arXiv:2609.29808 (https://arxiv.org/abs/2609.29808) | [Qin et al. - Publication Metadata [Part 3/3]: Title tag: Rollback Is Not Erasure: Dual-Tier Vaults and Ungated Quarantine Meta description: Why single-tier undo fails autonomous agents: certified Primary baselines, content-addressed Amber forensics, fail-closed checkout, bypass detection, and ungated quarantine.