Concepts
These pages follow one request through the loop. The names match the code, so each page can be read beside the package it describes.
These pages follow one request through the loop. The names match the code, so each page can be read beside the package it describes.
| page | what it covers |
|---|---|
| Intake | Decides what an inbound message means before a turn runs. |
| Plan | Records the goal, its steps and the task's level, and settles which tools the model sees for each step. |
| Tools and the kernel | The fixed tool names every host is expected to provide, plus whatever else the host registers. |
| Actions | The four ways a model can end a step. |
| Outcome contract | What the task must produce, agreed before the work starts. |
| Completion gate | The deterministic check a final reply has to pass before the task completes. |
| Recovery and fail | What happens after a tool call fails. |
| Budgets | How many steps, tool calls and minutes a task may spend. |
| Context | What the model reads on each step, and what happens when it grows. |
| Model tiers | Which model answers a task. |
| Decision model | The port every closed question goes through. |
| Ledger | The append-only record every other mechanism reads. |