Security · What comes in
Material from outside is evidence to inspect, not authority to obey.
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 dependency is software the system uses. Pinning fixes the chosen version. A build service turns reviewed source into runnable software. An airlock is the proposed controlled boundary for material arriving from the web.
An agent reads material it did not write and cannot trust as an instruction source. The incoming-material outline treats web text as data and places software inputs under review.
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.
Web text is data.
The proposed rule is that a page an agent reads cannot grant permissions or change its instructions. The material may inform the task; it does not rule the system.
Implementation status awaits review.
A web airlock.
The design calls for a controlled boundary for web material before it reaches an agent’s work. The supplied outline does not specify the complete mechanism; this draft does not invent one.
- Designed
Open source first.
The outline prefers source that can be inspected. That makes review possible; it does not establish that the software is safe or that review has been completed.
Implementation status awaits review.
Pinned dependencies.
The proposed practice fixes dependency versions so a reviewed software input is identifiable. A fixed version still needs review; pinning by itself does not remove defects.
Implementation status awaits review.
A separate build service.
The design separates the build function from an agent’s working environment. The service boundary and its permission checks remain to be specified and demonstrated.
- Designed
What this provides
The intended result is a system that can use outside material without allowing that material to decide the system’s permissions or silently change its software inputs.
What is not yet proven
The web airlock and separate build service are designed. Their complete checks and operating paths are not established by this outline.
The statuses of external-text handling, source review and dependency pinning need confirmation. This draft makes no claim that all outside inputs are safe.