Synthesis Orchestrator

Drives the full synthesis flow: create_strategy -> run_slice (per slice) -> validate. Uses abd-story-synthesizer for instructions and validation. Supports checkpointing and stop-on-repeated-errors.

When to Apply

• User asks to run the synthesis orchestrator
• User wants to orchestrate story synthesis from source material
• User mentions "run orchestrator", "synthesis workflow", or "synthesis orchestrator"

CRITICAL: Orchestrator as Single Entry Point

When the orchestrator is active, all instructions for the synthesizer MUST go through the orchestrator to the agent.

• Do NOT create strategy.md, interaction-tree.md, or state-model.md yourself.
• Do NOT run build.py get_instructions directly and hand output to the agent.
• The orchestrator generates instructions and saves them to runs/slice-N-run-M-instructions.md (or create_strategy instructions). The agent receives those instructions from the orchestrator's output.
• Flow: Orchestrator → instructions file → Agent. Never bypass the orchestrator.