Skip to content
Arka Platform

Pilot a squad

A squad is a team of specialized agents recruited to work together on a mission. A leader coordinates, workers execute, a QA arbitrates.

When to use a squad

Section titled “When to use a squad”
  • Complex mission requiring several expertises (e.g. “audit the project’s GDPR compliance, propose a compliance plan, draft the missing policies”).
  • When a single agent does not cover all required roles.
  • When you want to trace who did what during the mission (the leader arbitrates, the QA validates).

Compose a squad

Section titled “Compose a squad”
  1. From the project view, open Create a squad.
  2. Describe the mission in natural language (one paragraph is enough).
  3. The squad-creator worker proposes a composition: recommended agents, designated leader, strategy.
  4. Validate or adjust the composition.
  5. The Leader Pack is recruited on the project (a special agent that pilots the squad).

Run the mission

Section titled “Run the mission”

With the squad-orchestration addon:

  1. The leader splits the mission into sub-tasks.
  2. Workers (recruited agents) execute their parts.
  3. The QA reviews each deliverable.
  4. The leader arbitrates escalations and concludes.

Progress is tracked in the persistent mission document — you see the state at any time in the Squad view.

Mission Guardian (gates)

Section titled “Mission Guardian (gates)”

The mission-guardian addon adds gates: an agent cannot move to the next phase until expected evidence (intermediate report, QA validation, etc.) is captured.

This is visible in the project’s Mission Guardian view (stepper, evidence, QA verdict).

Boundaries

Section titled “Boundaries”
  • Multi-agent orchestration is in beta. The live slice is functional but full UI routes are only active when the composition root exposes them.
  • A squad is attached to one project. You cannot share a squad across projects (by design — context is project-specific).

Going further

Section titled “Going further”