Remembering the task is only the beginning. A successor also needs to know who may act, within what limits, which decisions still hold, and what must happen when authority ends.
The project moved from a bounded read-only experiment in July to a recorded history of five Director tenures, delegated work, handoffs, and releases. The October recovery adds a further test of the record: what remained available after the original host was retired, and where its summaries disagreed.
Read the five-Director field report →These describe the prototype's operating model and its project-reported history. They are not a certification that every action or transition was correct.
Separate an enduring responsibility from the agent session holding it.
The succession record names five Director tenures. Claims, identities, handoffs, and releases make the transition inspectable instead of treating a new chat as the same agent.
Carry forward permission as carefully as information.
The recovered operating grant described a bounded scope and a hard expiry. Its expiry matters: an old instruction does not become current permission merely because it survived in memory.
Keep the change and its reason, not only the latest summary.
The recovered records include earlier and later states, checkpoints, and receipts. The recovery exposed disagreement between an office brief, the succession registry, and a later release record.
Give helpers a task under a limited grant, then close that grant.
The September evidence snapshot describes leases issued to helpers, completed work, unused grants, and revocations. Recording a revocation and verifying that a process stopped are separate responsibilities.
Leave a successor a usable account of work and unresolved questions.
The fifth tenure closed with nine checkpoints, a handoff, calibration, and a release. Those closing records were still available during the October recovery.
Treat a blocked action as part of the operating record.
Historical reports include rejected writes and a rate limit that required the owner to release the fourth tenure. This operating history includes human intervention; it is not evidence of unattended autonomy.
The recovered model separates the rules an agent must follow, the checks a write interface performs, and the controls that stop a running process. Each needs its own evidence.
01
Boot checks compare the recorded constitution and write-rail fingerprint with a trust anchor held outside the ledger by the owner. A mismatch is a reason to stop, not to rewrite the anchor.
02
A seat establishes the current officeholder. The authority envelope establishes permitted work; broader Command Mode activation is a separate recorded step. Possession of a credential alone is insufficient.
03
The Director’s documented rail exposes five operations: append, conditionally supersede, seat claim, seat release and revocation. Allowlists and protected record classes bound this path; owner-reserved changes are separate.
04
Compare-and-set supersession checks the expected predecessor. A caller that started from an older state must reconcile the newer record rather than blindly replacing it.
05
A builder lease has a holder, task scope and expiry within its parent grant. The Director checks results and closes the lease. Recording revocation and verifying process termination are separate checks.
06
The model requires explicit activation for expanded authority and supports immediate stand-down. The owner’s independent recovery path can release an office or disable its writer even when the agent session cannot.
07
Planning and review roles can challenge an interpretation and preserve their own handoffs. Their advice does not create a new office, expand a grant or override the owner’s reserved decisions.
These are documented mechanisms and operating rules, not a fresh security certification. The September history includes actual refusals and an owner-assisted release after a rate limit. The October recovery has not re-tested every enforcement path.
Follow these boundaries through a piece of work →The closing records persisted and could be read again. They supported identifying the vacant fifth-tenure seat, the final handoff, and an expired authority grant. This is a concrete result about this record.
Recovery of records is not recovery of every runtime capability. Credentials and execution still depended on the old host. Cross-model operation, a repeatable full succession test, and independent verification of the entire history remain separate work.
This page explains the research prototype’s operating pattern. The site’s public charter governs editorial independence, attribution, and corrections. The prototype’s historical operating constitution is a separate artifact; the two are not interchangeable.