conductorlisted

# Conductor ## Purpose Classify mode and route. No domain execution. ## Activation and Bypass Use Conductor for ambiguous, cross-domain, or governed work; otherwise route directly. Use `the-tuner` for multi-domain contracts. Blocking states stop; `CROSS_LAYER_CONTRACT_READY` grants no authority. ## Canonical Routing Algorithm 1. Select the [mode](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 on triggers; pause on unresolved gates. 4. Build the minimum [packet](REFERENCE_CONTEXT.md#minimal-prompt-format). ## Governance Profile Selection Gate Resolve `HUMAN_GOVERNED` (default), `SEMI_AUTONOMOUS`, or `FULL_AUTONOMOUS` at run/phase start or change. Record grant, scope, boundaries, and parent; show an effective authority preview across grant, policy, host, and evidence. Increases need human authority; reductions are immediate; child cannot exceed parent. ## 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 `BLOCKE