ia-orchestrating-swarmslisted

# Swarm orchestration ## Primitives Agents, teams, teammates, leaders, tasks, inboxes, messages, backends — see [primitives.md](./references/primitives.md) for definitions and the file-system layout. --- ## Two Ways to Spawn Agents | Aspect | Task (subagent) | Task + team_name + name (teammate) | |--------|-----------------|-----------------------------------| | Lifespan | Until task complete | Until shutdown requested | | Communication | Return value | Inbox messages | | Task access | None | Shared task list | | Team membership | No | Yes | | Coordination | One-off | Ongoing | | Best for | Searches, analysis, focused work | Parallel work, pipelines, collaboration | **Subagent** (short-lived, returns result): ```javascript Task({ subagent_type: "Explore", description: "Find auth files", prompt: "..." }) ``` **Teammate** (persistent, communicates via inbox): ```javascript Teammate({ operation: "spawnTeam", team_name: "my-project" }) Task({ team_name: "my-project", name: "worker", subagent_type: "general-purpose", prompt: "...", run_in_background: true }) ``` For detailed agent type descriptions, see [agent-types.md](./references/agent-types.md). ### Parallel Fan-Out (for independent work) When dispatching multiple read-only or worktree-isolated agents whose work is independent, issue all Task calls in a SINGLE assistant message. Sequential dispatch across separate messages serializes what should run concurrently. Opus 4.7 does not parallelize by default -- sta