Fleet docs v0.2.0-rc.448

For developers

You change the code in this repo. Each folder is its own Go module with its own gate.

Folder Gate CI
fleet/ make -C fleet quick, test -z "$(gofmt -l fleet)" (the full make -C fleet check runs in CI only) fleet.yml

Read the exit code, not the tail: make -C fleet quick >"$TMPDIR/c.log" 2>&1; echo "exit=$?".

Where the code is

To change Look in
A CLI command fleet/internal/cli/ (also what fleet serve and fleet node run)
An HTTP route fleet/internal/api/router.go, the contract fleet/api/openapi.yaml
An MCP tool fleet/internal/mcpworker/, fleet/internal/mcpcontrol/, the contract fleet/api/mcp-tools.json
What happens after a turn fleet/internal/supervisor/
Placement on nodes fleet/internal/node/coordinator.go, fleet/internal/sched/
How claude starts fleet/internal/driver/claude/claude.go
A schema change fleet/internal/registry/sqlite/migrations/
The page fleet/internal/web/index.html, fleet/internal/dash/

The parts and their links: architecture/.

Rules that cost the most when broken

  • Do not change a contract. The contracts are in the seam tables of breakdown.md and breakdown-multiplayer.md. If one is incorrect, report blocked.
  • Test the wiring. A new loop, handler or backend needs a test through fleet/internal/cli, not only its package. Four parts passed their unit tests and the real binary never called them.
  • A change to install, nodes, placement, kubejob or login needs a clean-VM run (fleet/test/cleanvm/run.sh). Fix one check with --only on the kept machines. Prove with one full run on the final tag.
  • A page change needs a real browser through the real login, with each panel checked.
  • Report what you did not prove. A closing comment has three lists: proven by fakes, proven live, not proven.

The full rules, each with its cause: CLAUDE.md and .claude/rules/fleet-testing.md.