Security · Recovery

After interruption, account for the work before starting more.

Draft for review. This page describes the proposed design. Features without a confirmed implementation status are marked for review; they are not claims of running controls.

An agent uses a model to reason and a harness to act. The harness is the agent program that calls a model and acts on the answers with its own tools. A seat is the confined environment in which the harness runs. The Awakener is the mechanism being built to start an agent within a limit and record what happened. A ledger is the ordered record of events. A cold start is a restart without relying on a still-running supervisor. A runbook is a written recovery procedure.

Recovery is part of the permission boundary. If the system cannot account for its state after an interruption, starting more work can compound the uncertainty.

The outline calls for a cold-start runbook, stopping on doubt and backups of the ledger.

Design outline dated 6 October 2026. What the four status labels mean.

The proposed design

Each heading states the design or practice. Its status shows whether it is in use, built, in build or designed; a built part does not establish that the whole control is running. Where the outline gives no implementation status, that status awaits review.

  • A cold-start runbook.

    The proposed procedure describes how to re-establish the system’s state when its supervisor is no longer running. The outline does not yet provide a reviewed procedure or a completed recovery exercise.

    Implementation status awaits review.

  • Closed on doubt.

    The intended rule is that uncertain state stops new work. The system should wait for the uncertainty to be resolved rather than guess that previous work has ended.

    Implementation status awaits review.

  • Account for runs after a crash.

    The Awakener design refuses new starts until everything that was running is accounted for. The record’s part is built; the supervisor’s part is still in build. The complete recovery path has not been demonstrated.

    • Builtthe record’s side
    • In buildthe supervisor’s side
  • Ledger backups.

    The outline calls for backups of the record used to account for work. A backup is a copy for recovery; this draft does not claim that a complete restore has been exercised.

    Implementation status awaits review.

What this provides

The intended result is a restart that preserves the permission boundary and the record of work, rather than treating an interruption as a fresh start with no obligations.

What is not yet proven

The complete Awakener recovery path remains unproven. The runbook, stopping-on-doubt implementation and ledger backup/restore process need confirmed statuses and evidence.

A stored backup alone is not evidence of a successful restore. No completed recovery exercise is claimed here.