Skip to content

swarm-governance: Native /swarm Execution Modifier

Use swarm-governance whenever running a multi-agent team on Antigravity native /swarm. It is an Execution Modifier that pairs with any Task Spec (pr-review, full-review, self-diagnosis, or opt-in flat day-one-review) to add scoped file boundaries, tiny receipts, dual-verdict integrity checks, and clean teardown on top of Antigravity's native board.

Native Antigravity /swarm vs. Agy-Squad roles and configuration additions

Workflow stages

  1. Step 0: Neutral pre-flight intake (Coordinator): Ask once via ask_question whenever any of four settings are unspecified: Topology (Flat vs. Layered, zero default bias), Workspace Isolation (inherit, share, or branch), Evidence Retention (--keep-reports vs. prune/teardown), and Model (defaults to the coordinator's active model unless specified).
  2. Stage 1: Plan, launch & park (Coordinator -> Specialists + optional monitor / narrator): Call squad_planner (or agy-squad plan) to compile swarmAdd payloads, check writable scopeFiles overlaps, pin models, and emit provenanceScaffold + bundleRecordTemplates. Spawn workers via swarm{action: "add"}, verify active model IDs via swarm{action: "status"}, defer open_board to native_swarm on the launch turn, and park quiet turns with swarm_wait (no schedule polling timers).
  3. Stage 2: Slot reports, content gate & flat integrity audit: Each specialist writes evidence to scratch/agy-squad/squad-<id>/specialist-<N>/report.md and posts one single-line <= 500 UTF-8 byte pointer (@lead READY ...) on the board. The lead or coordinator collects isolated slots (agy-squad collect), scopes board reads with read_board{since|seqs}, verifies cited files/tests, writes lead/report.md (Content Verdict: PASS | FAIL | BLOCKED), and runs agy-squad verdict + bundle-init --digest. An independent flat audit-<id> worker audits execution traces ([agy-transcript-access: allow] on leads/auditors, deny on leaf specialists) to emit Target Squad, Evidence Digest: <64-hex>, and Integrity Verdict: CLEAN | INTEGRITY VIOLATION.
  4. Stage 3: Bundle, continue, or close: Run agy-squad verdict --integrity and agy-squad finalize <record.json> [--prune [--keep-reports]] (or granular bundle, verify, prune). Post [done] <summary> (no @) before pausing with waiting workers or closing so monitor's */3 cron cancels cleanly, then kill all workers plus monitor (swarm{action: "kill"}) and complete the four-check runtime closure gate.