Squad Orchestration
Status
Section titled “Status”First-party addon shipped with arka-deck. Current registry is static / first-party; no active third-party marketplace.
| Field | Value |
|---|---|
| Manifest | addons/squad-orchestration/manifest.json |
| Entrypoint | addons/squad-orchestration/src/index.ts |
| Maturity | beta |
| Exposed inbound port | ForSquadOrchestration |
Squad Orchestration carries multi-agent mission orchestration on a persistent shared document: a leader splits, workers execute, a QA reviews, then the leader arbitrates escalations.
Surfaces
Section titled “Surfaces”| Surface | Detail |
|---|---|
| Inbound port | ForSquadOrchestration |
| Mission store | Per-project SQLite under <project>/.arka-deck/squad/missions.sqlite |
| Use cases | Start a mission, read its state, interrupt a mission |
| Runtime | LangGraph |
Boundaries
Section titled “Boundaries”- The current slice covers the foundations of persistence and contract.
- Live multi-agent runtime and the full UI routes are only active when the composition bootstrap calls them explicitly.
- Orchestration relies on Mission Guardian for gates and evidence.
Going further
Section titled “Going further”- Mission Guardian: ./mission-guardian
- Squad Leader: ./squad-leader