Human authority
The owner defines the mission, reserved decisions, and the scope and expiry of permission. The agent holding credentials does not get to invent its own authority.
One governed record. Across agents, work, and time.
thecontinuitylayer.com/systemThe project brings a human owner, a continuing Director’s Office, a governed ledger and task-scoped builders into one operating model. Here is how the parts fit together—and what they carry from one session to the next.
Owner
Defines the mission and grants authority
Director’s Office
Coordinates work within that authority
Builders
Complete tasks within limited leases
Controlled write path
The Director’s permitted changes pass through a limited write interface. Owner-reserved changes have a separate authority boundary.
Genesis · governed record
Authority, current state, decisions, receipts, checkpoints and handoffs are read back from the record.
A conceptual view of the operating model, not a live status dashboard. Review roles inform the work; they do not independently grant permission.
01The components
What we built around the agent
A capable model is one part of the system. The surrounding structure makes its task, permission, changes and handoff explicit.
Director’s Office
The office continues while its occupants change. A named tenure claims the seat, checks its authority, coordinates work, and leaves a handoff for its successor.
Genesis ledger
Decisions, state, permissions, checkpoints and receipts share a record. Later states supersede earlier ones, keeping the change and its provenance available.
Controlled write path
The write rail provides a limited set of operations: append, conditionally supersede, claim or release a seat, and revoke. Protected records and write limits constrain the Director’s path.
Task-scoped builders
A builder receives a specific task under a limited lease. Its output must be checked, and its permission closed when the task ends or is stopped.
Review and recovery
Checkpoints, handoffs, calibration and independent review roles help the next session reconstruct the situation. Conflicting or expired records are surfaced before work resumes.
02Follow a piece of work
From an instruction to a continuing record
Select a step to see the intended operating path, the record it leaves and the boundary it must respect. This walkthrough explains the system; it does not run an agent.
Orient
Recover the situation before taking the task.
A new execution reads the handoff, current state and recorded history. Boot checks compare the constitution and write-rail fingerprint with an owner-held trust anchor.
What carries forward
A verified boot, a named tenure and an identified office state.
The boundary
A remembered instruction is evidence to examine; it is not fresh permission. A failed trust check stops operation.
03Beyond chat memory
Permission, state and evidence travel together
The current account has a history.
A changed decision needs its predecessor, reason and source. Supersession preserves that relationship instead of silently replacing the past. A handoff is a dated account of a tenure, not a new constitution.
Authority can end while memory remains.
An agent may remember a task after its grant expires. Stand-down, lease revocation and seat release give permission a lifecycle separate from stored knowledge. Stopping must be reflected in both records and execution.
The source of an instruction matters.
Documents, tool responses and quoted text can contribute evidence. The operating rules distinguish that material from commands in the owner’s authenticated channel. A claim of permission must be checked against the governing record.
Recovery is part of operation.
The owner retains an independent recovery path. A successor verifies the trust anchor, office state and authority before resuming. When those disagree, the disagreement becomes work to resolve—not something a fluent summary can conceal.
04System, evidence, field
Three parts of the same project
The governed system
The architecture and governance described here: an enduring office, controlled state changes, bounded delegation and succession.
Read the governance model →The working evidence
The Lab traces the bounded July experiment, September’s work and handoffs, and October’s recovery. The separate public demo covers a subset of the fourth tenure.
Inspect the Lab →The field map
The broader research, taxonomy, tools and benchmarks that inform the work. The map remains a separate editorial responsibility, with the project’s own interests disclosed.
Explore the field map →A recorded operating history across five tenures.
Recovered September dispatches describe verified boots, authority activation, delegated work, receipts and handoffs. October reads found the closing records still available: 620 memory records, 179 audit receipts and a vacant fifth-tenure seat.
Read the dated succession report →The record is recovered; a new runtime is separate work.
The old authority grant has expired, some summaries disagree, and host-bound credentials have not been restored. This is a research prototype with project-reported evidence, not an independently certified platform or a claim of unattended, universal model portability.