Reliable by Design · 05.18

Node Reference: Control Flow

router, merge, parallel, wait, checkpoint, phase_gate, subflow, loop, stop_error, return_output — every control-flow node explained.

NodesReference

The control-flow family

Node	Purpose
`router`	Branch on a safe condition (deterministic) or an LLM decision.
`merge` / `parallel`	Join fan-out under a join policy; run branches concurrently.
`wait`	Park until a time, event, or condition — a zero-token sleep, not a busy loop.
`checkpoint`	Snapshot state, optionally gated behind a human decision before proceeding.
`phase_gate`	Hold an entire phase behind a cost, SLA, or approval condition before it's allowed to start.
`subflow`	Invoke a child workflow as one crash-safe, idempotent unit.
`loop`	Bounded fan-out over an items array, with durable per-iteration resume — see Converge & Pursue.
`stop_error` / `return_output`	Terminate a branch with an explicit error, or emit the run's declared output.

How parallel agent work gets its own git worktree, so a swarm or a converge cohort never steps on another branch's changes.

agent_task, agent_session, agent_swarm, converge, pursue, planner, evaluator, guardrails — every intelligence node explained.