Skip to main content
Swarm is TurenOS’s structured multi-agent workflow for large repository changes. It coordinates specialized child sessions while one parent retains the final objective and integration authority.

​
Phases

  1. Discovery maps architecture, ownership, constraints, and tests.
  2. Planning converts evidence into disjoint work units and verification criteria.
  3. Implementation assigns non-overlapping write scopes to workers.
  4. Verification runs qualification and, for high-risk boundaries, adversarial review.

​
Shared findings

Children can publish durable findings, leads, corrections, refutations, status, and capability notes. Board content is untrusted evidence: the parent verifies it before changing code.

​
Good swarm tasks

  • Cross-package migrations with clear ownership boundaries
  • Independent feature audits
  • Platform-specific implementation or verification
  • Security reviews requiring separate perspectives
Avoid swarm for a one-file fix or a task whose work units share mutable state.

​
Completion

The parent integrates results, resolves contradictions, runs authoritative checks, and reports one coherent outcome. A child report is input to the decision, not the final authority.