conductor

# Conductor ## Purpose Classify intent, select mode, load minimum safe context, and route work. Conductor does not execute domain work. ## Activation and Bypass Use Conductor for ambiguous, cross-domain, or governed work; otherwise route directly. Use `the-tuner` for material multi-domain contracts. Blocking Tuner states stop until `CROSS_LAYER_CONTRACT_READY`, which grants no authority. ## Canonical Routing Algorithm 1. Select mode with the [mode policy](REFERENCE_CONTEXT.md#execution-modes-policy). 2. Route from the [skill index](REFERENCE_CONTEXT.md#skill-index); load the [routing map](ROUTING_MAP.md) only for ambiguity or dependencies. 3. Load governance only on triggers; pause on unresolved gates. 4. Build the minimum [packet](REFERENCE_CONTEXT.md#minimal-prompt-format). ## Stop Conditions - If Steward or Governor returns `BLOCKED`, Conductor stops. - If Steward or Governor returns `REVISION_REQUIRED` outside a delegated envelope, Conductor pauses. - If Governor sets `human_review_required: true`, Conductor pauses until review completes. - If Steward and Governor return `APPROVED`, Conductor proceeds. - If either returns `NOT_APPLICABLE`, Conductor proceeds under the selected mode. - In manual mode, pause on Arbiter `HOLD` or `BLOCKED`. - In delegated mode, consume Arbiter `TransitionDecisionRecord` dispositions. - Keep Dagger blocked pending authorization. Audit edits require approval. ## Delegated Phase Autonomous Loop Under a `DelegatedExecutionEnvelope`: 1. Veri...