Guides

Guides answer “how do I make a run behave”, where Reference answers “what does this option do”. Each one pulls together several parts of the runtime around a single decision.

• Orchestration controls — execution topology, declared governance, task dispatch, gates on consequential tools, cancellation, coordinator configuration, and fan-out.
• Control costs and budgets — bound a run with maxTokenBudget or maxCostBudget plus a caller-owned estimateCost, and decide what should happen when a run hits the ceiling.
• Production checklist — the controls to wire up before going live: routing, dispatch, budgets, timeouts, recovery, evidence, redaction, and tool grants.

Elsewhere

• Getting started — install, first run, and choosing a run mode.
• Reference — every runtime page, grouped by what it configures.