delegated-execution

Give the worker one bounded task with exact paths, acceptance criteria, verification commands, out-of-scope items, and a numeric size ceiling. Resolve required skill paths before dispatch and include their absolute paths in the brief, since the child does not inherit your context.

Use an advisor at a decision boundary when several plausible approaches have consequential tradeoffs or new evidence undermines an accepted plan. Advisors are read-only thinking partners; factual lookups belong to research and checking completed work belongs to review.

At most three concurrent children are allowed. Parallel writers need isolated worktrees with one writer per checkout, parallel reviews need disjoint surfaces, and children must not delegate further.

The model policy maps roles to harness-specific defaults, such as Opus for implementation and review on Claude Code, or Terra and Sol on Pi and Codex. Explicit user choices take precedence, and unavailable models require stopping to ask before substituting.

Inspect the actual diff and verification output, compare results against each acceptance criterion, and check changed assertions, suppressions, and call sites. A worker's completion report alone is not acceptance; pending or unsupported criteria block it.

Do not delegate intake, quick fixes, or small factual gaps; handle small tasks inline. Delegation is justified only when independent work or context isolation earns the coordination cost.