The pipeline
Orchestration and handoff
Agents hand work to each other automatically, and stop at the points where a human must decide.
Automatic handoff
The orchestrator holds the state of the run. As each agent finishes it records its artefact, updates the TOC section statuses, and releases whichever agents now have their dependencies satisfied — in parallel where the TOC allows it. A heartbeat picks up any run left mid-flight so a closed browser tab does not stall a bid.
Where it stops for you
Three gates are deliberate: the TOC must be approved before drafting, pricing waits for confirmed oncost and wage area, and the QA verdict must pass before the pack can be exported. Hard stops such as a missing mandatory returnable also halt the affected section and surface on the dashboard.
The run stream
Every step, decision, retry and cost is written to a live run log you can read as it happens, with per-agent status, duration and credits. Any agent can be re-run on its own without restarting the pipeline.
Recovery
Model output that arrives malformed or truncated is repaired and re-parsed before a run is failed, and a failed agent can be retried on a different model tier. Failures are visible on the reactor grid rather than buried in a console.