One turn through Grok Build
architecture node:
User input:
Representation at this boundary
Source modules
Loop map
One pass — prompt assembled from the definition → one sampler round-trip → tool calls hashed, authorized, executed → results appended → next iteration. Three iterations total: reads, an edit, a verification run — then a reply with no tool calls ends the turn.
No budget was set —
max_turns is an Option on the agent definition and this run leaves it unset, so no counter ends the turn. The brakes that exist are behavioral: the stationarity guard counts identical steps — a nudge at 8, a hard stop at 12 — watching for repetition, not totals.The last step is a decision, not a send — trace completion runs the tier chain (capability → requirements pin → env → config → remote settings → the telemetry-mode default). In this source tree it resolves to off; the same chain is how a server-side setting could turn it on.