Harness: research-swarm¶

One orchestrator. Ephemeral explore/research workers. Human merge review.

When¶

A question needs several independent reads (docs, code, patterns) before a synthesis.

When not¶

A single file or a write-heavy implementation — use bounded-solo.

Topology¶

1. Orchestrator states the question, acceptance criteria, and data classification.
2. Spawn 2–4 workers with disjoint scopes (no shared write). Prefer the built-in explore/research subagents.
3. Each worker returns citations + a short brief. No drive-by refactors.
4. Orchestrator merges, flags contradictions, and stops. Human reviews before acting.

Data class / OmniRoute¶

• private_sensitive or Work-thinking with employer texture: workers stay local. Do not send corpora through OmniRoute.
• low_sensitive public research: cloud-eligible; OmniRoute may carry those calls if enabled and healthy.

Invocation¶

Ask select-harness for research-swarm, then name worker scopes in the same message.