> ## Documentation Index
> Fetch the complete documentation index at: https://docs.turen.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Swarm workflows

> Run staged multi-agent discovery, planning, implementation, and verification

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.

```mermaid theme={null}
flowchart LR
  Goal[Parent objective] --> Discover[Discovery agents]
  Discover --> Plan[Bounded work plan]
  Plan --> W1[Worker A]
  Plan --> W2[Worker B]
  Plan --> W3[Research]
  W1 --> Integrate[Parent integration]
  W2 --> Integrate
  W3 --> Integrate
  Integrate --> Qualify[Qualification]
  Qualify --> Review[Risk review]
  Review --> Result[Verified outcome]
```

## 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.