Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Loop control states

Generated from crucible/src/runloop/machine.rs by crucible loop-states; scripts/state-docs.sh --check keeps it current. The driver advances through this table at every gate, so an edge missing here is a transition the loop cannot take.

Each Turn is one iteration's work graph (propose → apply → measure → decide), rendered in Work graphs. Everything else is the control shell around it: the gates at the Head, the parks, and how a run ends. Dashed states are idle; the colored edges are the ways out.

The loop's control states

The source is docs/img/loop-states.dot (crucible loop-states --format dot).

How a run ends

The edge label after the arrow is the shutdown token on the session log.

TokenMeaning
finishedall iterations completed
solveda kept candidate satisfied the win condition
budgeta cost or time cap was reached
stoppedstop signal received
escalatedthe agent declared the harness inadequate — halted for human review
stalledthe run stalled on consecutive transport failures — no turn could start

An error inside the loop reports error and takes none of these edges.