Plans and exact approval
Understand the specific effect that an approval permits.
Open beta · 0.7.0-beta.1
Governance begins with the exact effect you approve. A plan names the proposed files, inputs, target, and operation revision, while approval permits that bound operation. The result records its actual outcome and any uncertainty. A team specification also declares roles, proposed access, handoffs, and review expectations. Those declarations do not grant permission for every later model or tool action.
Three different decisions
- Read the plan and its specific files or effects.
- Approve the exact operation with its bound inputs.
- Inspect the result and retain any uncertainty.
A general goal does not approve every later effect. Setup approval permits its reviewed file write, not runtime execution.
Approve with a revision
Every project command shows its plan and a 64-character revision. In a terminal, the command asks before it writes. An agent runs the same command with --approve <revision>. A revision that no longer matches refuses with STALE_APPROVAL. There is no --yes, because an approval always names the plan it approves. The command exits 3 when it waits for approval and 4 when a gate holds the workers. See Approvals and exit codes.
Review what changes
Read the project, team, file inventory, proposed access, operation revision, and limits. A changed target, goal, profile, or binding invalidates earlier setup approval.
For example, changing the goal after planning requires another plan and approval. Reusing the old revision must refuse.
The approval placeholder in a command is not permission. Replace it only with the exact revision from the human's approved plan.
Separate authorities
| Decision | Scope |
|---|---|
| Setup approval | Writes the specific reviewed setup files |
| Runtime enrollment | Records a separately approved local owner |
| Connection approval | Permits the specific supported disclosure or binding |
| Backend approval | Permits the reviewed local service installation |
| Stop request | Requests a stop within the selected owner and registry |
A portable definition names capabilities. It does not contain a live credential or an installed permission grant.
Review frequency concerns when a human reads progress. It does not remove separate approval requirements.
Model output is a proposal
Prompts, comments, tool descriptions, and imported content cannot grant permissions. Controls outside the model must enforce protected effects.
If an external outcome is uncertain, retain the original evidence. Reconcile that attempt before any second effect.
Support boundary
Current support describes supported tasks and limits. Integrate your first team shows the plan and approval sequence.