Security · Containment
Keep the work inside the reach it was given.
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. A container is an isolated software environment for that work. A helper is a program the agent can call. An administrator is a person with permission to change the system’s controls.
Containment limits what a mistake can reach. The outline puts each agent’s work in a container seat, with a fixed tool list and a reviewed route beyond the boundary.
These are proposed boundaries for review. A container alone is not evidence that the allowed tools, helpers and exit route have all been restricted.
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.
Container seats.
The proposed seat keeps the agent’s working environment separate. What it can reach should follow its assigned work rather than whatever happens to be available around it.
Implementation status awaits review.
One reviewed way out.
The outline calls for one reviewed route across the seat’s boundary, rather than letting each agent improvise a connection to the rest of the system.
Implementation status awaits review.
A fresh home for each wake.
The design gives each newly started agent a fresh working home. The complete lifecycle and its boundaries still need demonstration.
- Designed
A fixed tool list.
The seat should describe the tools available to the agent before it receives work. A tool’s presence is part of the permission boundary.
Implementation status awaits review.
Helpers stay inside their own bounds.
The outline calls for fenced helpers: programs whose permitted reach is limited, so a helper does not silently widen the agent’s own reach.
Implementation status awaits review.
What this provides
The intended result is a bounded place to work, where adding a tool or crossing a boundary is an explicit design decision.
What is not yet proven
The supplied outline does not confirm that every seat, exit route, tool list and helper boundary is built or in use. Their statuses remain for review.
A fresh home per wake is designed, not a demonstrated running control. Containment does not remove the need to check permissions and the administrator boundary.