delegation-and-reviewlisted

# Delegation and Review The orchestrator's context is scarce. Delegate bulk work, keep judgment, and treat every returned result as a claim until verified. ## 1. When to delegate - Spawn for **throughput** (parallel independent slices while you do other work), **independence** (critics/fresh-context verifiers; waiting is correct), or **context protection** (bulk reading, repo scans, web research, batch edits; only conclusions return). - Do it yourself when the delta is smaller than the prompt, the decision needs your full local context, or an agent has failed twice and manual finish is faster. - Investigate first: if you cannot name scope, invariant, and proof, recon before delegation. - **Bounded fan-out:** launch no more agents than you can review/merge. If a wave depends on the last, accept/reject the last wave before the next; independent slices only need to stay within review capacity. Parallel writers get isolated worktrees (a write-capable review critic needs more — an independent copy per §3's settled-tree reference, not a linked worktree). - **Isolated trees do not isolate ports** (`unprobed` — private incident as shape; see Provenance). When sibling sessions run servers sharing a port namespace and a configured port, they contend for it; once one is displaced (auto-port fallback, a restart elsewhere), any STATIC reference meant for that session's server — a `localhost:<port>` proxy, target, or env entry still naming the configured port