History and threads
The preamble supplies the goal, completed stages, steering and relevant context before each prompt. Repeated visits fold into one stage entry with the latest content and a visit count.
Fidelity
Section titled “Fidelity”| Value | Stage content |
|---|---|
compact |
Complete content, the default. |
summary:high |
First 2000 characters of each stage. |
summary:medium |
First 800 characters. |
summary:low |
First 200 characters. |
truncate |
No stage history. |
The incoming edge’s fidelity wins, then the node’s fidelity, then the graph’s default_fidelity, then compact. Steering queued for this turn remains complete even under truncate. Fidelity changes the prompt history, not the persisted evidence.
Threads and restart
Section titled “Threads and restart”Turns normally start fresh sessions. thread="implementation" shares a session across agent nodes carrying that thread name. A thread cannot mix resolved harnesses, and threads are forbidden inside parallel branches.
A loop_restart edge clears iteration context, completed stage history and thread sessions, while retaining original inputs, run identity, visit accounting and repair budget state.
Parallel branches
Section titled “Parallel branches”A component starts each bare outgoing edge as a branch, up to max_parallel at a time. Every branch must reach the same tripleoctagon join. Branches cannot contain cycles, nested fan-outs or edges escaping their branch.
Each branch gets its own context and visit accounting. Results arrive in edge order under parallel.results, with node, outcome, failure_reason and context. Branches share working files, so use read-only reviews or disjoint writes. Successful collection enters the join; partial failure takes a matching conditioned edge from the fan-out or holds for the operator.
A join with a prompt runs one synthesis turn on the default harness. Without a prompt it is only a barrier. In templates use a quoted index, such as {{ context.parallel.results['0'].context.assessment }}. The parallel guide validates that spelling in a complete graph.
An insulator requires a duration, for example 5m. Waiting keeps the interface responsive. The operator can skip the remaining duration, and the transcript records that choice. Saved waiting state lets resumed work account for the wait, and poll loops spend no agent visit budget.
Inline attribute expressions on this page are syntax fragments. Use the complete attribute wrapper and the linked runnable examples as validation contexts.