Swarm

Read the installed poteto-mode reference ../poteto-mode/references/t3-execution.md before selecting models or delegating. It owns named-role resolution, catalog option keys, accounts and automatic authorized missing-usage fallback.

Start

Open a todolist with one entry per phase before launching anything.

1. Frame
2. Fan out
3. Aggregate
4. Report

Phase A: Frame

1. State the done predicate and the artifact or report the swarm must return.
2. Choose the shape. Partition into slices, race N workers on identical briefs, or mix both. For a race or mixed shape, declare first pass, rank all, or best-of before spawning.
3. Pick the worker model from the swarm workers line in pstack-models.md. If the file or that line is missing, use its bundled default at xhigh reasoning through live catalog option keys unless the user chooses a budget. For auto or inherit-parent, resolve the parent target. If delegate_task rejects an entry, follow the execution adapter's authorized fallback preserving effort and required diversity and say so. For a model race, name each arm's model up front. Set each subagent's reasoning level and speed per the Subagents section of the poteto-mode skill.
4. Give each worker its own writable output when it writes. When workers verify or measure commits, each brief names the exact SHAs. A measurement brief also names the method (sample count, what one sample is, order). The worker records both in its result.