06 · Durable workflow coordination
Orchestrator
Turn complex multi-stage work into a controlled stateful process instead of an ephemeral chat sequence.
Designed for
Teams coordinating builders, reviewers, evidence, recovery and protected approval gates.
Why it exists
State, ownership and evidence are lost across sessions and repeated retries.
- Duplicate execution and unclear stage ownership
- Review and implementation collapse into one context
- Partial failure has no durable recovery route
How it works
Orchestrator flow
- Durable stage
- Builder
- Evidence
- Reviewer
- Recovery / next stage
- Owner gate when required
Product relationship
Part of a wider system
Conceptual product relationships; this diagram does not claim active technical integration.
- User Canon supplies relevant guidance profiles
- Guardian protects consequential decisions
- Custodian can carry out a separately authorized bounded change
What it does
A bounded product response
- Preserves durable stages and dependencies
- Coordinates bounded builder and reviewer handoffs
- Carries evidence between stages
- Routes recovery and protected Owner decisions without using people as couriers
Product evidence
A concise passport
- Purpose
- Turn complex multi-stage work into a controlled stateful process instead of an ephemeral chat sequence.
- Current product state
- Stateful coordination product in active development
- Evidence basis
- Orchestrator state model, workflow contracts and recovery evidence.
- Human-controlled or bounded
- A failed step changes the recovery hypothesis; it does not trigger a blind retry loop. Protected decisions remain Owner-gated where required.
Next step
Explore with the right expectation
Product is evolving to the next product version.