Concepts
Brakes and state
The brakes are a feature. Learn the three NZT STOPs and how Plan/state.json keeps the work so a new session can resume without rebuilding the chat history.
By default, every unit ends at a reviewable edge. You can authorize a batch, but the material brakes are still there.
The three brakes
| Brake | When | What happens |
|---|---|---|
STOP 01 |
Unapproved plan | Nothing runs. |
STOP 02 |
End of unit | State → report → wait. |
STOP 03 |
Material risk | The environment and the consequence are named. |
The state: Plan/state.json
The session is disposable. The state is not.
Plan/state.json keeps the goal, approval, units, autonomy, blockers and the next entry point. A session that saw none of the conversation has to be able to understand it.
{
"goal": "Build Pulso",
"phase": "build",
"approved": true,
"units": [
{ "id": 3, "status": "done" },
{ "id": 4, "status": "todo" }
],
"waiting_on": null
}What it gives you
- Resume without rebuilding the chat.
- A single unit in progress.
- What is pending stays visible.