Track 2 — Builder 构建 · M8 · 30 min · Sandbox by 31 Aug 2026
Run safety: budgets & kill switch (W4)
Step, token and wall-clock budgets per run, a monthly workspace cap, and an operator kill switch. Every run records its stop reason.
Prerequisites: M7 · Adapters and execution honesty
After this module you can…
- Set a budget, trip it deliberately, and read the stop reason.
- Explain why a runaway loop is a financial event.
Key points
- Defaults: max steps, max tokens, 180s wall clock, monthly cap, kill switch off.
- Budget rules are pure functions with unit tests — show the tests as proof.
Hands-on exercise: Trip the budget
- Lower max steps to 2 in Organisation → Run safety.
- Run a multi-step task and read the HALTED reason.
- Flip the kill switch and observe the pre-flight refusal.
Evidence of success: A usage row with a non-empty stop reason.
Knowledge check
Getting it wrong is fine — the explanation tells you why.
1. Which budget stops an infinite loop?
2. What does the kill switch do?
Module 8 of 20 · progress is stored on this device.