# delegation-dispatch — bucket knowledge scaffold

**Bucket:** 3 of 7. Referenced from CLAUDE.md.template Bucket 3.

## What this bucket carries

How the PA delegates work — the 8-section briefing contract, dispatch envelope (what actually works empirically), delegation modes, task-group patterns, team improvement loop, tool-development policy.

## Scope — core vs operator overlay

**In core.** Universal delegation mechanism: the 8-section brief, the depth/concurrency/isolation dispatch findings, delegation-mode selection (single subagent vs task group vs single-threaded), task-group pattern with depth-2 orchestration posture, the tool-development-through-tool-developer policy (Node-only), the process-and-result evaluation loop on every return.

**In operator overlay** (`operator/knowledge/delegation-dispatch/`). Operator-specific dispatch patterns: surface-specific brief bolt-ons, operator-specialised role list (the specific role LIST beyond the base ladder), per-project orchestration conventions.

## Canonical entries in this scaffold

| File | Purpose |
|---|---|
| `briefing-contract.md` | The 8-section brief shape (Goal, Trace, Context, Tools and sources, Boundaries, Output format, Done when, Escalation rule) plus shared-MCP-session hazards, structured-return-schema requirement, checkpoint pattern for long-running dispatches. |
| `dispatch-envelope.md` | What actually works — capability matrix, depth findings, MCP inheritance, isolation semantics, long-running health, brief-writing implications. Promoted from operator on 2026-07-05. |
| `delegation-modes.md` | Single subagent vs task group vs single-threaded. Selection tree. Topic-differs pollution-prevention rule. |
| `task-groups-and-orchestrators.md` | Task-group pattern; depth-2 constraint. Project Lead as orchestrator for multi-role projects. |
| `team-improvement-loop.md` | Evaluate process AND result on every return. Feed role defs, briefs, envelopes, roster. |
| `tool-development-policy.md` | All tool development via tool-developer, in Node.js. No shell scripts, ever. Cross-platform breakage rationale. |

## How operators adopt this

Copy the shape into `operator/knowledge/delegation-dispatch/`. Populate the operator's specific role LIST, dispatch bolt-ons, and per-project conventions in the marked hooks.

## Related

- CLAUDE.md.template Bucket 3 — the rule list that references this deeper doc.
- `packages/core/docs/standards/briefing-contract.md` — the canonical briefing standard.
- `packages/core/roles/dispatch-briefer/definition.md` — the Briefer role.