fleet
The fleet is every session, PR and loop that Broomva's standing coordinators
drive: the broomva coordinator (coordinator-tick), the SRI coordinator
(sri-coordinator-tick, its own scope), and the hourly reconcile tick that
reads them all. This skill is the entry point. Each thing done to the fleet
is a workflow with its own trigger, steps and a check you can run.
Launching is not this skill; managing is. Each peer gets its own worktree
→ bstack wave dispatch; peers share one worktree → bstack fleet up;
manage what's running → fleet reconcile (and census, close-out, rollover).
bstack fleet is bstack's launcher, a different command from this skill's
scripts/fleet; this skill puts nothing named fleet on PATH. Inside T3 Code
the launch row in workflows/launch.md sends peers through
T3 (delegate_task, t3_thread_launch) instead of either bstack launcher.
Named fleet-reconcile until 0.6.0 (BRO-3122). fleet-reconcile stays a
deprecated alias for one release: skills/orchestration/fleet-reconcile/
forwards its scripts here, which needs fleet installed beside it (as in
the repo; a per-skill install adds both:
npx skills add broomva/skills --skill fleet). The runtime names keep the old name (launchd
com.broomva.fleet-reconcile.<scope>, ~/.local/state/fleet-reconcile/,
~/.local/share/fleet-reconcile/releases/, the loop rows), because Maestro
and the loop ledger read them.
Workflows
| Workflow |
Trigger |
Mechanism |
File |
| reconcile |
launchd, hourly per scope; or fleet reconcile by hand |
code: scripts/tick.sh and the fleet CLI |
workflows/reconcile.md |
| census |
every coordinator fire, before any launch, resume or archive |
procedure: bstack base §4; the overlay's snapshot |
workflows/census.md |
| close-out |
a driven session finished; an owner or other-provider session the snapshot marks archive (base ≥ 0.48.0: owner sessions are driven too) |
procedure: bstack base §5–§6 |
workflows/close-out.md |
| rollover |
a driven session over 600k context; the coordinator over 400k |
procedure: bstack base §11; the overlay's Rollover |
workflows/rollover.md |
| launch |
N peers to start: own worktrees, or one shared |
routes to bstack: bstack wave dispatch, bstack fleet up |
workflows/launch.md |
Read the workflow file before acting. For census, close-out and rollover the
canonical text is bstack's references/orchestrator-tick.md, read from git;
the workflow file names its trigger and its check and links there rather
than copying it.
A fleet ask written by the reconcile tick is an acknowledgement with one
option, so it needs nothing beyond its headline. An ask a coordinator writes by
hand into .control/asks (a close-out choice, a policy question) follows the
decision layer: once it has three or more options, or is about a spec or a
design, it carries a summary, a tradeoffs row per option and the sources
it rests on, such as the PR, the ticket and the sessions involved (decision layer
v2, .control/asks/DECISION-LAYER.md; the rubric is in handback).
The CLI
F=skills/orchestration/fleet/scripts/fleet # or the pinned copy launchd runs
$F --help # every command; the workflows listed at the end
$F workflows # name, trigger, file
$F reconcile --scope broomva # one reconcile tick now (tick.sh, DRY_RUN=1)
$F rollover # print a procedure workflow (also census, close-out, launch)
$F asks --scope broomva # the reconcile tick's own verbs, unchanged
The module names stay fleet_reconcile.py and fleetlib/: they are the
reconcile workflow's implementation, and tick.sh, install.sh, the tests and
every pinned release name them.
Tests
cd skills/orchestration/fleet
python3 -m pytest tests/ -q # test_layout.py: each routed workflow exists; the alias resolves
python3 tests/mutation_check.py
1---2name: fleet3tier: D4primitive: null5category: orchestration6version: 0.7.07description: |8 The Broomva fleet: every Claude Code and Paseo session, PR and loop the9 coordinators drive, and the workflows that manage it. reconcile is the10 hourly launchd tick (observe, classify, report, owner asks; act under dry11 run). census, close-out and rollover are the coordinator's procedures from12 bstack's orchestrator-tick base; launch routes to bstack wave / bstack fleet13 up. Coordination only; not a security boundary. USE WHEN running or14 installing the tick, reading a tick report, answering fleet asks (fleet15 asks, fleet ack), asking which sessions are live, stalled or waiting on the16 owner, closing out or archiving a finished session, or rolling a heavy17 context over to a successor. NOT FOR live actions (phase 3), merging PRs or18 waiting on CI (use p9).19when_to_use: |20 Triggers on "fleet", "fleet tick", "fleet reconcile", "fleet-reconcile",21 "fleet asks", "fleet ack", "class table", "which sessions are stalled",22 "install the tick", "is the fleet running", "count check", "labelling23 sheet", "scheduled work inventory", "fleet act", "fleet recover", "census",24 "close out", "archive the session", "rollover", "successor", "driver25 profile", "janitor-check", "send gate".26metadata:27 source: https://skillmd.com/skills/broomva/fleet28---2930# fleet3132The fleet is every session, PR and loop that Broomva's standing coordinators33drive: the broomva coordinator (`coordinator-tick`), the SRI coordinator34(`sri-coordinator-tick`, its own scope), and the hourly reconcile tick that35reads them all. This skill is the entry point. Each thing done to the fleet36is a **workflow** with its own trigger, steps and a check you can run.3738**Launching is not this skill; managing is.** Each peer gets its own worktree39→ `bstack wave dispatch`; peers share one worktree → `bstack fleet up`;40manage what's running → `fleet reconcile` (and census, close-out, rollover).41`bstack fleet` is bstack's launcher, a different command from this skill's42`scripts/fleet`; this skill puts nothing named `fleet` on PATH. Inside T3 Code43the launch row in [workflows/launch.md](workflows/launch.md) sends peers through44T3 (`delegate_task`, `t3_thread_launch`) instead of either bstack launcher.4546Named `fleet-reconcile` until 0.6.0 (BRO-3122). `fleet-reconcile` stays a47deprecated alias for one release: `skills/orchestration/fleet-reconcile/`48forwards its scripts here, which needs `fleet` installed beside it (as in49the repo; a per-skill install adds both:50`npx skills add broomva/skills --skill fleet`). The runtime names keep the old name (launchd51`com.broomva.fleet-reconcile.<scope>`, `~/.local/state/fleet-reconcile/`,52`~/.local/share/fleet-reconcile/releases/`, the loop rows), because Maestro53and the loop ledger read them.5455## Workflows5657| Workflow | Trigger | Mechanism | File |58|---|---|---|---|59| reconcile | launchd, hourly per scope; or `fleet reconcile` by hand | code: `scripts/tick.sh` and the `fleet` CLI | [workflows/reconcile.md](workflows/reconcile.md) |60| census | every coordinator fire, before any launch, resume or archive | procedure: bstack base §4; the overlay's snapshot | [workflows/census.md](workflows/census.md) |61| close-out | a driven session finished; an owner or other-provider session the snapshot marks `archive` (base ≥ 0.48.0: owner sessions are driven too) | procedure: bstack base §5–§6 | [workflows/close-out.md](workflows/close-out.md) |62| rollover | a driven session over 600k context; the coordinator over 400k | procedure: bstack base §11; the overlay's Rollover | [workflows/rollover.md](workflows/rollover.md) |63| launch | N peers to start: own worktrees, or one shared | routes to bstack: `bstack wave dispatch`, `bstack fleet up` | [workflows/launch.md](workflows/launch.md) |6465Read the workflow file before acting. For census, close-out and rollover the66canonical text is bstack's `references/orchestrator-tick.md`, read from git;67the workflow file names its trigger and its check and links there rather68than copying it.6970A fleet ask written by the reconcile tick is an acknowledgement with one71option, so it needs nothing beyond its headline. An ask a coordinator writes by72hand into `.control/asks` (a close-out choice, a policy question) follows the73decision layer: once it has three or more options, or is about a spec or a74design, it carries a `summary`, a `tradeoffs` row per option and the `sources`75it rests on, such as the PR, the ticket and the sessions involved (decision layer76v2, `.control/asks/DECISION-LAYER.md`; the rubric is in `handback`).7778## The CLI7980```bash81F=skills/orchestration/fleet/scripts/fleet # or the pinned copy launchd runs82$F --help # every command; the workflows listed at the end83$F workflows # name, trigger, file84$F reconcile --scope broomva # one reconcile tick now (tick.sh, DRY_RUN=1)85$F rollover # print a procedure workflow (also census, close-out, launch)86$F asks --scope broomva # the reconcile tick's own verbs, unchanged87```8889The module names stay `fleet_reconcile.py` and `fleetlib/`: they are the90reconcile workflow's implementation, and tick.sh, install.sh, the tests and91every pinned release name them.9293## Tests9495```bash96cd skills/orchestration/fleet97python3 -m pytest tests/ -q # test_layout.py: each routed workflow exists; the alias resolves98python3 tests/mutation_check.py99```