fleet-routine

Cron-scheduled autonomous routines for the 6-harness fleet — like Claude Code's native cloud routines (/schedule → CronCreate), but uniform across every harness (Claude, Codex, Gemini/agy, Grok, Odysseus, Ollama) on all house PCs.

Design (council opus 2026-07-17, FLT-34): fleet-routine is the C# scheduling plane — it owns when a routine runs and under what budget. It does not orchestrate. Execution is delegated to fleet-harness (FLT-1, Python/LangGraph), the single orchestration engine that selects the harness adapter and routes the work. The runner invokes the graph (fleet-harness routine-fire) across a process boundary — prompt-file in, JSON out — and never re-implements routing. This preserves fleet-harness's anti-fork property.

Trigger = Windows Task Scheduler (trigger only: reboot/sleep survival, missed-run catch-up). Transport = NATS JetStream (fleet.v1 envelope). Governance = usage-governor, queried at fire time, fail-closed; defer means skip this tick, never queue-and-flush.

Status

Pre-build. Gate 0 (FLT-104) — non-interactive auth smoke — is the GO/NO-GO for everything. See docs/FLT-104-gate0-auth-smoke-spec.md and docs/BOARD.md.

Documentation

Full docs (two tracks — technical + plain — plus diagrams and a living making-of) start at docs/README.md.

Language

C# first (per fleet language policy). The orchestrator it delegates to is Python — an approved deviation, because an outage-continuity orchestrator must not depend on Claude.