Delegation Patterns

Delegation works best when the orchestrator decides where work goes and the supervisor decides how that domain executes.

Routing Layer

Overseer now classifies requests into direct chat, single-domain, or multi-step work before planning. That reduces unnecessary delegation and keeps simple requests fast.

Good Delegation

• Route to one clear domain.
• Keep the handoff structured.
• Return evidence with the result.
• Escalate only when the task actually requires another layer.

Bad Delegation

• Sending every chat message through a planner.
• Letting supervisors invent new routing logic on the fly.
• Handing off free-form prose instead of task structure.
• Using delegation to hide weak prompts.

Personality Modes

Personality should be orchestrator-managed metadata, not the source of routing truth. Use modes to shape tone and output style, but keep delegation based on domain and evidence.

Next Steps

Continue with Planning Overview or inspect Viewing Traces to see delegation decisions in practice.