fleet-routine — Delivery Board¶
Canonical board for the
fleet-routineproject (FLT-34): cron-scheduled autonomous headless routines across the 6-harness fleet, delegating execution tofleet-harness(FLT-1).Redundancy rule: this file + Vikunja (project 2, http://127.0.0.1:3456/projects/2) + Jira (FLT project) move in lockstep on every status transition. This file is source of truth until the other two prove sync.
Statuses: Backlog · Ready · In Progress · In Review · Blocked · Done
Architecture (council opus 2026-07-17 — do not re-litigate)¶
Ranking D/grok > A/claude > B/codex > C/gemini > E/local; house councils 5 AGREE / 2 DISSENT
(dissents = the rejected "absorb into FLT-1/Python" minority; both heaviest votes — gpt-oss:120b,
qwen3-next:80b — confirm). Report:
llm-council/reports/2026-07-17_191704_should-the-fleet-harness-flt-1-the-universal.md.
fleet-routine= C# scheduling plane — owns WHEN + budget: registry, WTS trigger, fire-time governor check, NATS telemetry, Pavlok policy. Does NOT select harness adapters.fleet-harness(FLT-1, Python) = the ONLY orchestration engine — owns HOW + adapter selection + routing + Claude-down failover. The runner invokes it (fleet-harness routine-fire), never re-implements routing. Process boundary = feature; seam = prompt-file in / JSON out.- Runs on NullLedger (FLT-1 Gate 2 open — do NOT wire agy into cap_proximity). Signing identity =
sessionId, not worktreeId. Emit on frozen
fleet.v1.
Board¶
| Key | Phase | Status | Summary |
|---|---|---|---|
| FLT-104 | Gate 0 | In Review | doctor implemented + Claude-verified (build 0/0, 18/18 tests). Council review gate + live --register-probe run OWED before merge. Spec: docs/FLT-104-gate0-auth-smoke-spec.md; BUILD-REPORT.md. |
| FLT-105 | P1 | Blocked (by 104) | run-now vertical slice through the C#↔fleet-harness seam. run-now BEFORE WTS. |
| FLT-106 | P2 | Blocked (by 105) | WTS trigger via COM/API (trigger-only), StartWhenAvailable, reboot/sleep survival. |
| FLT-107 | P3 | Blocked (by 106) | multi-PC JetStream replay + Claude-native normalize. Fork: subprocess/sync vs NATS-command/async. |
| FLT-108 | P4 | Blocked (by 107) | Pavlok dedupe/escalation + full cap enforcement; missedRunPolicy = skip-retry-never-flush. |
Blocks chain: FLT-104 → FLT-105 → FLT-106 → FLT-107 → FLT-108. All anchored to FLT-34.
Log¶
- 2026-07-17 (WT-6022): repo scaffolded; FLT-104 Gate 0 spec drafted on branch
wt/WT-6022/FLT-104. Tickets FLT-104..108 created on Jira + linked. Next: buildfleet-routine doctor --noninteractiveper the spec; land Gate 0 before any FLT-105 code.