Fleet docs v0.2.0-rc.448

What a team copies, what stays per person

Copy to the team

  • An operating agreement. What the lead agent does alone, what it reports after, and what it asks first: messages in a person's name, a delete of data with no copy, history rewrites, money. Ask for this test: "Is there a path back?"
  • Repo rules with their cause. Each rule names the failure that made it, with an issue number. A rule with no cause gets removed.
  • Safe-shell rules. set -euo pipefail in a chain that changes state. Read the exit code, not the tail. Never pkill -f. Wait on a condition, not a guessed sleep.
  • The testing standard. Tests first, fakes over mocks, a real throwaway database, no live external calls, deterministic tests.
  • The skills that divide work. Build pipeline, drive a session, hand off, supervise, release.
  • The brief and ticket templates.

Keep per person

  • Facts about one machine: paths, memory, tools, which cluster context is which.
  • A person's preferred report style and language.
  • Auto memory.
  • Accounts, tokens, dashboards and the names of boxes.

In this repo today, and in a private repo

Item Where today
Repo rules (CLAUDE.md), fleet testing rule (.claude/rules/fleet-testing.md) this repo
Release skill (.claude/skills/fleet-release/) this repo
Operating agreement, safe-shell rule and skill one person's private repo
Build pipeline, drive a session, worker brief, ticket template one person's private repo
Hand off, supervise, testing standard, plain-language writing one person's private repo

Proposal: what moves here

Planned, not done. Move the general form, with no personal content, to docs/governance/ and .claude/skills/ in this repo:

  1. safe-shell, as a rule (.claude/rules/safe-shell.md) and a skill. Workers need it, and a worker does not load skills from a parent directory.
  2. testing-standard, as a rule that loads for test files (paths:).
  3. build-pipeline, drive-session and the worker brief, with placeholders for the forge, the owner and the model limits.
  4. supervise, after the watch design in #230.
  5. An operating agreement template: autonomy, the ask-first list, the source-of-truth table.

handoff stays per person. It names two boxes and their paths.