Security · Secrets
Keep credentials out of the agent’s working text.
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 operator is the person with authority over the system. A credential proves identity or permits access. A vault is the controlled store for credentials. A reference names a credential without containing its value. A key is a credential that permits access.
The secrets outline separates where a credential is kept from where it is used. Scripts should name a reference, and the operator should retain authority over the vault and the reach of each credential.
This page describes the intended arrangement without disclosing any credential, account, storage location or installation detail.
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.
One vault owned by the operator.
The proposed arrangement places credential ownership with the operator. An agent’s need to do work does not give it authority to grant itself wider access.
Implementation status awaits review.
References in scripts.
The outline calls for scripts to carry references rather than secret values. That separates a script’s description of its work from the credential used to perform it.
Implementation status awaits review.
Narrow keys.
A key should permit only the work it is issued for. The proposed boundary is explicit permission, rather than broad access shared by every agent.
Implementation status awaits review.
A revoke-everything order.
The design provides for an operator action that withdraws credentials when the system needs to be stopped. This is a designed capability, not a claim that a complete revocation path has been demonstrated.
- Designed
What this provides
The intended result is access the operator can limit and withdraw, without distributing credential values through the team’s scripts and working text.
What is not yet proven
Vault ownership, references in scripts and narrow keys need confirmed implementation statuses before this draft can present them as operating guarantees.
The revoke-everything order is designed. Its coverage and complete execution still need evidence.