FAST 3-STEP SERIES DIGEST 2/3 — Digest 1 (§01–§03) · Digest 2 (§04–§06) · Digest 3 (§07–§09) · 1-Page Master Brief · All 9 Articles · Assurance · Proof

§04 — The Room: Why Git and Chat Are Not Coordination Planes

  • URLs: 1-Call Brief (/04/brief/) · Full (/04-the-room-why-git-and-chat-are-not-coordination-planes/) · Raw Markdown (/04.md) · Parts (5): P1 P2 P3 P4 P5
  • Thesis & Scope: Problem: Git history and chat transcripts cannot establish who may act, receive, stop, or complete work now. — Proves: The Room revalidates territory, causal observation, sealed wakes, native replies, cancellation, and privileged acceptance. — Scope: Use the Multi-Agent Coordination & Acceptance Audit Challenge on one assignment with an uncertain outcome.
  • The Whole Machine, Not a Wake Queue: The Room includes eleven cooperating mechanism families grouped into six architectural domains. Nine receive numbered subsystem sections below; worker staging and controller-side brokerage are developed within native execution and…
  • One Assignment Through the Machine: Consider a coordinator assigning renewal-evidence review to reviewer-beta. The path is not “write a prompt and hope the right agent answers”: If registration changes before dispatch, the old wake stops with… — Items: Territory and principal. The coordinator's credential, native conversation, project object, and Room scope are re-derived. The recipient's registration is current. | Recognized work. An EISA submission supplies the constitutional act and its evidence handles.
  • 1. Git and Chat Are Necessary—and Insufficient: Git is an excellent source-history plane. Chat is an excellent human and model communication surface. The Room does not replace either. It prevents their artifacts from impersonating live authority. — Table Data: Tool-call schema; Native value: The proposal has a valid shape; Additional question the Room answers: Is this exact act recognized, currently standing, and inside the caller's verb and tier authority? | Graph/workflow checkpoint; Native value: A prior plan can resume; Additional question the Room answers: Is that plan valid for the current target, conversation, task…
  • 2. Subsystem 1: Territory and Principal Identity: Subtopics: Split-brain state-tree refusal; Project grants pin path and kernel object identity; CSPRNG enrollment without persistent plaintext secrets; Thread-local sessions and native conversation identity; Tier clamping includes the route, not just the tool name; Stdio and pre-model egress are separate boundaries — Authority starts by proving which state tree and which physical project object the act concerns. Before the engine opens its state tree, validate_state_dir requires the state-directory identity marker. — Items: a unique project ID and bounded name; | the requested and canonical root paths; | root_object_id, a 192-bit combined identity: a 64-bit volume serial number plus the 128-bit NTFS/ReFS file ID; | opening actor and time; | an optional governing-source grant and its reading…
  • 3. Subsystem 2: The Room Graph Is a Visibility and Recovery Boundary: Subtopics: Withholding closes over descendants; Composition is intersection, not union, of authority; Recovery refuses reparse shortcuts and preserves causal order — Each Room owns a physically isolated graph shard derived from the workspace instance and Room name: binding.json permanently fixes Scope::Coordination or Scope::Project { id }.
  • 4. Subsystem 3: The Room Sync Engine and the Pre-Action Work Gate: Subtopics: A durable per-Room sync index; Handle-pinned reconciliation; Checkpoints bind actor, conversation, credentials, Room, and view; The Work Gate requires frontier and causal readiness — A coordination plane cannot rely on an agent remembering what it has read. It must measure the observation. Each Room has sync_index.db under squad.room_sync_index.v1. — Items: journal_mode = WAL; | synchronous = FULL (2); | foreign_keys = ON; | busy_timeout = 5000 ms. | The conversation checkpoint is ready and confirmed_offset covers the live coordination frontier.
  • 5. Subsystem 4: Contribution Verbs Have Different Authority Effects: The Room is not freeform chat with locks added later. Its verbs deliberately separate status, answer, assignment, transfer, and completion. An untargeted say reply cannot resolve a mixed set of pending obligations. — Table Data: note; Wake and task rule: Never wakes; visible @mentions refused; Constitutional effect: Status or identity telemetry without mentions, obligations, or dispatch | reply; Wake and task rule: Never wakes; explicit reply_to required; Constitutional effect: Resolves an addressed mention or obligation after validating that it belongs to the caller | say; Wake…
  • 6. Subsystem 5: A Wake Is a Sealed Authority Transition: Subtopics: The 18-field room-wake-job-v3 binding; Five live dispatch checks; Single flight, capacity, and split-lock claim; Evidence is delivered to the recipient, not inherited from the sender; Exhibit 1 — A sealed wake binding excerpt; Exhibit 2 — Registration changed after sealing; Exhibit 3 — Deadline consumed before dispatch — A queued prompt is not execution authority. It is a proposal to deliver work later, under conditions that may have changed. binding_sha256 covers these exact queue fields: The explicit task: null matters: adding or stripping a task… — Items: Sealed integrity and replay eligibility. Schema, binding digest, canonical queue object, and retry_allowed must hold. Tampering records wake_job_binding_changed as an integrity signal.
  • 7. Subsystem 6: Native Session Delivery and Reply Are Different Proofs: Subtopics: Session Factory v1; The five delivery/reply proof states — A tool transport can deliver a request to a process. It cannot prove that the intended native conversation received it or that the resulting obligation was answered. — Table Data: dispatched; What is proven: A delivery attempt exists, not body delivery; Obligation status: delivery_unproven; unresolved | delivered_to_body / ide_delivered; What is proven: The prompt reached the native session body; Obligation status: pending_reply; unresolved | body_visible_pending_reply; What is proven: The target thread UI or store shows the…
  • 8. Subsystem 7: Active Cancellation and Worker Authority: Subtopics: Authenticated control and held in-flight operations; The 1 Hz owned-Job observer and durable stop outbox; Worker staging minimizes data before confinement; The controller-side MCP broker revalidates the worker and the call — Room control is authenticated and physically enforced. It does not rely on a worker noticing a cancellation message eventually. Lifecycle actions require control_actor standing through an authenticated operator or local owner console.
  • 9. Subsystem 8: Task Lineage and Privileged Acceptance: Subtopics: Delegation cannot outlive or widen its ancestry; Seven acceptance kinds, evaluated by the engine; Completion revalidates authority and live evidence; Exhibit 4 — Successful artifact acceptance; Exhibit 5 — file_absent cannot turn an observation error into absence — A Room reply says the worker answered. Acceptance asks whether the actual artifacts satisfy the task. Task scopes exclude controller state, recovery storage, shipped binaries, skill mirrors, and authoritative Room ledgers. — Table Data: sha256: Reads the in-scope file and compares its live SHA-256 with the expected digest | file_exists: Uses Path::try_exists(); an OS or permission error is unconfirmed, not success | file_absent: Uses the same observation law: an error fails closed instead of becoming absence | command: Executes an absolute, owner-allowlisted binary with no shell or… — Items: Basic requires at least min task submissions with one terminal outcome and no pending, recording-pending, or worker-unread results. | StrictReturn requires one applied submission with the exact worker, target, expected fields, and version delta +1, then proves that…
  • 10. Subsystem 9: Five Runtime Invariants Constrain Event Law: Subtopics: Exhibit 6 — An in-doubt TTL record — Pre-action gates decide whether an act may proceed. The runtime invariant engine continuously checks the event stream for structural violations and records dedicated invariant_violation nodes through the journal and Room graph. — Table Data: exactly_once; State carrier and rule: A bounded 10,000-entry FIFO IdempotencyRegistry rejects a repeated confirmed idempotency key; Severity and boundary: Reject; deduplicates registered events, not every external effect | well_formed; State carrier and rule: A lifecycle tracker per (agent_id, parent_id) enforces valid Begin → Effect → Resolve transitions;…
  • 11. The 2026 Coordination Evidence Landscape: The 2026 literature and protocol specifications reinforce the same architectural distinction: state management, native session identity, revalidation, and measured completion are separate control surfaces. Each source has a bounded claim. — Table Data: Liu et al., Multi-agent Collaboration with State Management (STORM), May 2026 preprint; What it actually establishes: Worktree isolation defers conflicts to post-hoc merge; STORM mediates shared-workspace state at write time and outperforms the baseline by 18.7 points on Commit0-Lite and 1.4 on PaperBench, with comparable or better…
  • Bring One Assignment With an Uncertain Outcome: The Multi-Agent Coordination & Acceptance Audit Challenge evaluates one assignment whose delivery, ownership, or completion is currently hard to prove.
  • The Twelve Coordination Claims: Table Data: 04-C01; Bounded claim: Split-brain state trees are refused, and project grants revalidate canonical path plus 192-bit combined kernel object identity; Evidence and ceiling: Implemented and author-verified on local NTFS/ReFS territory; not a remote-share or host-admin guarantee | 04-C02; Bounded claim: Enrollment, thread-local sessions, native conversation binding, tier clamping, and multiplexer verb probing bind every connector call to a principal and route; Evidence and ceiling: Implemented and author-verified on declared MCP/CLI paths and host contracts | 04-C03; Bounded claim: Room shards carry immutable scope bindings and parent-withholding closure; Evidence and…
  • The Article 04 Claim Card: Items: Mechanism: | The AINA Room Coordination Plane | (state identity, project grants, connection/session authority, tool policy, | graph shards, visibility, sync, contribution verbs, wake permits, | Session Factory, worker confinement, cancellation, acceptance, invariants) | Failure it governs: | Source history and chat impersonating live authority; | split-brain state and redirected territories; | stale context, causal-parent blindness, and ambiguous obligations; | stale queued wakes and wrong-session delivery; |…
  • The Room Is Where Authority Becomes Current: A recognized act can be mathematically sound and still be operationally stale. The evidence may be valid, the partition correct, the destination plausible—and the worker may be reading an old frontier, holding a replaced registration,…
  • Frequently Asked Questions: Subtopics: Why aren't Git worktrees enough for multi-agent coordination?; Why isn't a workflow checkpoint enough?; What makes a Room wake different from a prompt queue?; Is delivery to an IDE session proof of completion?; Why does file_absent use try_exists()?; Do the five invariants prove exactly-once external effects? — Worktrees separate source histories and defer conflict resolution to a later merge. They do not establish current resource ownership, causal observation, wake validity, native delivery, or artifact acceptance.
  • Continue the Series: Items: Series index: From Proposal to Consequence: The AINA Transition-Governance Series | Previous: [Article 03 — Semantic Switch and EISA: Protected Computation and Entity…
  • Primary 2026 Sources: Items: Liu et al. — Multi-agent Collaboration with State Management (STORM), arXiv:2605.20563 | Sarkar — Before the Pull Request: Mining Multi-Agent Coordination, arXiv:2606.19616 | [Nechepurenko and…
  • Publication Metadata: Title tag: The Room: Why Git and Chat Are Not Coordination Planes Meta description: Why Git worktrees and chat transcripts cannot govern live agents: inside The Room's territory pins, causal sync gate, sealed wake permits,…

§05 — Expiry Is Not Fencing: Typed Leases and Kernel Write Exclusion

  • URLs: 1-Call Brief (/05/brief/) · Full (/05-expiry-is-not-fencing-typed-leases-and-kernel-write-exclusion/) · Raw Markdown (/05.md) · Parts (4): P1 P2 P3 P4
  • Thesis & Scope: Problem: An expired lease does not physically stop a stale worker or an uncooperative local writer from changing a resource. — Proves: Monotonic generations, current tenancy, typed scopes, and overlapping Win32 handle exclusion fence the write itself. — Scope: Use the Shared-Resource Lease & Kernel Fencing Challenge on one shared file or SQLite row.
  • The Two Hazards the Architecture Must Defeat: Subtopics: Hazard 1: The resurrected worker; Hazard 2: The uncooperative local writer — The refusal must happen at the resource. A wake-time check is not enough because authority can change after the wake. A heartbeat alone is not enough because a delayed heartbeat can arrive after succession.
  • 1. Six Typed Namespaces and Real Target Identity: Subtopics: Lexical paths are not kernel object identity — Leases are partitioned by resource class, not by an undifferentiated path string. Bare paths default to file:// for compatibility. A TypedScope contains the namespace and full resource_id; different namespaces never conflict with one… — Table Data: file://; Example resource: Exact files or directory hierarchies; Conflict rule: Canonical path-prefix conflicts; parent and child scopes overlap | session://; Example resource: Managed sessions and virtual resources such as sqlite.records/<target>; Conflict rule: Canonical session-resource prefix conflicts | window://; Example resource: GUI application…
  • 2. Workspace-Wide Monotonic Generations: Subtopics: Two-phase persistence; Exhibit 1 — A sealed generation marker; Exhibit 2 — The stale-worker refusal — A per-file counter can restart when the file is replaced or a lease is released. That makes old authority look current again. AINA therefore uses a workspace-wide high-water sequence in room.generation.v2.
  • 3. A 30-Second Cross-Process Transition Mutex: Generation, lease mutation, vault capture, guarded replacement, and readback must form one authoritative transition. with_transition serializes them through .lease-transition.mutex, an OS file lock opened with read/write sharing but no… — Items: The transition mutex serializes one commit and is held across decision, capture, replacement, and verification. | The lease TTL bounds tenancy and requires heartbeat renewal. | The generation determines whether a tenancy is current at execution.
  • 4. Acquisition, Re-Grant, and Conditional Lifecycle: Subtopics: Dead-holder re-granting requires proof of death; Conditional lifecycle compares all six tenancy keys — Acquisition checks break-glass admission, package/source exclusion, namespace conflicts, and existing tenancy. A lease cannot silently change tasks; lease_task_mismatch preserves the original binding. — Items: an enforced server-held tenancy, or an eligible identity-bound managed SQLite session; | holder_alive to be false; | the recorded holder_pid to be absent according to process_alive.
  • 5. The Five-Role Overlapping Handle Exchange: Subtopics: Role G: the long-term exclusion; Role W: pin and hash the preimage; Role P: pin the parent directory; Role T: stage and rename the new object; Role H: bridge publication to the next guard; Role G': verify before success — Windows refuses to rename over an existing destination when any open handle withholds FILE_SHARE_DELETE. The long-term guard therefore cannot simply remain open across replacement. Closing it naively would create a write-open race. — Items: FILE_RENAME_INFORMATION_EX class 65; | FILE_RENAME_FLAG_POSIX_SEMANTICS (0x2); | FILE_RENAME_FLAG_REPLACE_IF_EXISTS (0x1) when replacement is allowed; | RootDirectory = parent_pin.as_raw_handle(); | one verified relative UTF-16 leaf name.
  • 6. Two Residual Intervals—and the Evidence They Produce: Subtopics: Preimage displacement forensics; Exhibit 3 — Successful guarded replacement verification; Six typed reconciliation faults; Exhibit 4 — destination_preimage_displaced — The handle exchange closes write-open gaps. It does not make every delete or rename impossible. During Interval 1, only W and P remain; during Interval 2, only H remains. — Table Data: GuardLost; What broke: The destination guard could not be acquired or reacquired; reconcile_by action: If the rename completed, hash the path to distinguish published bytes from preimage; if it failed, re-establish the lease before any further write | NameRedirected; What broke: G' resolves somewhere other than the leased path; reconcile_by action: Resolve… — Items: Interval 2's object substitution is detected by G' identity verification. | A reparse redirect is detected by comparing G''s resolved path with the leased scope. | A moved preimage is detected through W.
  • 7. Server Liveness and Zero-Downtime Image Handoff: Subtopics: Adopting leases without an exclusion gap — A fencing system cannot depend on a PID alone. PID reuse would let a dead holder appear alive. enter_server_mode publishes .squad/servers/<pid>.json with build, session, and protocol identity, then holds the record itself with… — Items: Generate a one-time handoff secret and pass it only to the child. | The child authenticates with squad/lease_adopt before serving ordinary requests. | For every held scope, the child takes its own deny-write handle while the parent still holds its handle.
  • 8. Fencing Continues Into Every Execution Surface: Subtopics: File write funnel; Fenced SQLite mutation; RequestedAct and result grants — Generation checks would be decorative if they stopped at the lease manager. They are wired into file replacement, SQLite, worker acts, and successor result delivery. — Items: rereads the current row and requires now_version == expected; | captures recovery state; | revalidates target identity, RequestedAct, and approval; | executes a conditional `UPDATE ...
  • 9. Release Verification and Quarantine: Subtopics: The out-of-band owner lock kill-switch; Exhibit 5 — Release quarantine instead of baseline laundering — Release is another evidence boundary, not a lockfile deletion with good intentions. release_content_check compares on-disk bytes with: If content matches, release archives the post-edit state to Amber. — Items: post_sha256 from the last gated write under the lease, when one exists; or | the lease's captured pre-write FNV-1a and byte count when no gated write occurred.
  • Platform and Route Matrix: The architecture is therefore strong without becoming unfalsifiable. It names the route it governs, the kernel primitives that enforce it, the interval it cannot close, and the evidence that remains when verification fails. — Table Data: Windows long-lived MCP server: Kernel handle exclusion is enforced across tenancy and all five replacement roles | Windows short-lived CLI: Lease is advisory because process exit drops handles; protected execution requires a server-held handle | Non-Windows: No equivalent Win32 share-mode, parent-pin, native-rename, or liveness claims; no false equivalence is…
  • 10. The 2026 Fencing Evidence Landscape: The research supports monotonic execution fencing and exposes the same limitation that matters here: a mechanism proves only the effect classes its boundary actually covers. The functional-equivalence concession still applies. — Table Data: Shu, Boundary-State Control for Tool-Using Language-Model Agents, September 2026 preprint; What it establishes: BSC-R binds a single-use authorization to the exact action and semantic authorization state.
  • The Adversarial Stale-Writer Challenge: The Shared-Resource Lease & Kernel Fencing Challenge uses a deliberately hostile sequence, not just a happy-path replacement: The challenge excludes retroactive revocation of pre-existing handles and mappings, universal OS/filesystem… — Items: Worker A acquires generation 14 and stalls. | Worker B acquires generation 15 and completes a guarded replacement. | Worker A resumes and attempts both a stale-generation write and a direct incompatible file open.
  • The Twelve Execution Claims: Table Data: 05-C01; Bounded claim: Six typed lease namespaces and hierarchical conflict rules govern ownership; FNV-1a is only a routing key; Evidence and ceiling: Implemented and author-verified for all lease requests; full canonical identity decides authority | 05-C02; Bounded claim: Filesystem scopes reject ambiguous paths and resolve opened object identity through handles; Evidence and ceiling: Implemented and author-verified on local NTFS/ReFS targets | 05-C03; Bounded claim: Workspace-wide monotonic generations use two-phase persistence and refuse rollback; Evidence and ceiling: Implemented and author-verified; missing state never resets to zero | 05-C04; Bounded claim: A…
  • The Article 05 Claim Card: Items: Mechanism: | AINA Typed Leases, Monotonic Generation Fencing, and Guarded Replacement | (typed scopes, room.generation.v2, transition mutex, lifecycle guards, | G/W/T/H/G' handles, parent pin, liveness, SQLite fences, and release quarantine) | Failure it governs: | Stale workers resurrecting after lease expiry; | uncooperative local write/delete/rename opens; | rolled-back generation stores and successor-tenancy confusion; | parent junction swaps and destination reparse redirection; | displaced preimages and…
  • The Clock Is Not the Fence: A lease expires because coordination needs a way forward. That does not mean the old worker has become harmless. Authority must change form at the resource: a new generation, a new holder, a new epoch, and a kernel-enforced exclusion that…
  • Frequently Asked Questions: Subtopics: Why is lease expiry not fencing?; Is FNV-1a part of the security proof?; Why are five handle roles necessary?; Does the kernel gate revoke handles or mappings opened earlier?; What does preimage displacement detection prove?; Does this guarantee exactly-once external effects? — Expiry allows ownership to move after a holder stops responding, but it does not erase a stale worker's process, cached authority, delayed request, or physical ability to write. The resource must reject the stale generation at execution.
  • Continue the Series: Items: Series index: From Proposal to Consequence: The AINA Transition-Governance Series | Previous: [Article 04 — The Room: Why Git and Chat Are Not Coordination…
  • Primary 2026 Sources: Items: Shu — Boundary-State Control for Tool-Using Language-Model Agents: Commit-Time Consistency under State Drift, arXiv:2609.37475 | [Lyu et al.
  • Publication Metadata: Title tag: Expiry Is Not Fencing: Typed Leases and Kernel Write Exclusion Meta description: Why wall-clock lease expiry cannot stop stale AI writes: typed scopes, monotonic generations, five-role Win32 handle exchange, preimage…

§06 — Rollback Is Not Erasure: Dual-Tier Vaults and Ungated Quarantine

  • URLs: 1-Call Brief (/06/brief/) · Full (/06-rollback-is-not-erasure-dual-tier-vaults-and-ungated-quarantine/) · Raw Markdown (/06.md) · Parts (3): P1 P2 P3
  • Thesis & Scope: 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.
  • 1. Why Single-Tier Undo Fails: 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: 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: 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. — Items: 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: 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/<fnv1a_16hex>/. — Items: 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: 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. — Items: 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: 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.
  • 6. Per-Mutation Amber Accumulation: 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: 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… — Items: 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: 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: 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: 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. — Items: 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…
  • 11. The 2026 Recovery Evidence Landscape: 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. — Table Data: Shu, Boundary-State Control for Tool-Using Language-Model Agents, 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…
  • The Forensic Baseline & Quarantine Challenge: 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: Table Data: 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 object | 06-C03; Bounded claim: Primary bytes and sidecars are read back immediately after writing; Evidence and ceiling: Implemented and author-verified; mismatch aborts protected change | 06-C04; Bounded claim: Full ledger replay binds exact versions to canonical…
  • The Article 06 Claim Card: Items: 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: 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.
  • Frequently Asked Questions: 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.
  • Continue the Series: Items: Series index: From Proposal to Consequence: The AINA Transition-Governance Series | Previous: [Article 05 — Expiry Is Not Fencing: Typed Leases and Kernel Write…
  • Primary 2026 Sources: Items: Shu — Boundary-State Control for Tool-Using Language-Model Agents, arXiv:2609.37475 | Pino — Hard Stop: Kernel-Level Preemption and Containment for Rogue Agentic Execution, arXiv:2609.29808 | [Qin et…
  • Publication Metadata: 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,…

FAST 3-STEP SERIES DIGEST 2/3 — Digest 1 (§01–§03) · Digest 2 (§04–§06) · Digest 3 (§07–§09) · 1-Page Master Brief · All 9 Articles · Assurance · Proof