Delegation Composition

How a session's work divides between the main thread and the federation. The General orchestrates; it does not execute domain work itself. Canonical numbers live in CLAUDE.md §Token economy; this law binds them.

Created 2026-06-10 to give the law its own file — already quoted load-bearing by CLOUD.md, /plan-cloud (retired 2026-06-11 → CLOUD handover protocol), /state-review and /handover (finding H8, full-stack diagnostic).

The 3-band law (local sessions)

Band	Token share	Contains
Commander work	40–70%	Domain execution via subagents
State management	20–40%	Context loading, synthesis, routing (Canary, Jimmy Neutron, Orochimaru, Meruem)
Hinata main thread	10–20%	Orchestration, user communication

Running everything in the main thread is a STRUCTURAL-FAILURE.

Cloud sessions

Execution-type cloud sessions (autopilot, bugfix, /task-audit execute, build) require ≥60% subagent share, tagged source=cloud · session_type=execution. Cloud tiers map to the bands above.

Composition rules

• Every dispatch carries the five dimensions of naming-conventions §Subagent Dispatch — name, registered subagent_type, action tag, {Commander}: {task} description, model.
• Fan disjoint units in parallel up to the 25-agent cap; re-fan as units complete.
• Bash/transform work routes to Jimmy Neutron; vault writing stays with the Sole Writing Authority or an Edit-granted commander.
• Delegation share is measured per session by check-delegation-ratio.py → Orochimaru token-burn report → Meruem evolution assessment.