Project documents
Design, build, and operations documents for one project. Each project keeps its sources, its build manifest, and its final pages in one folder.
Claude Fleet
| Page | Kind | Updated |
|---|---|---|
| Claude Fleet: one identity per containerThe case for one isolated container per client identity. It covers the architecture, the attach contract, the failure paths, and the decisions that keep the rollout small. | proposalcurrent | 26 Oct 2026 |
| Claude Fleet: build spec and task planThe build spec for Claude Fleet. It holds the requirements, the tracked tasks, the target architecture, the open decisions, and the acceptance checklist. | speccurrent | 26 Oct 2026 |
| Fleet Flows: how a request travelsHow a request travels through Claude Fleet. It shows five scenarios, the container anatomy, the exact configuration, and the isolation contract. | flowscurrent | 26 Oct 2026 |
Reference guides
Cross-project guides, checklists, and operating plans. These documents do not belong to one codebase. They hold the rules that each project follows.
Agent Team
| Page | Kind | Updated |
|---|---|---|
| Two models, ten people, one trunk: an operating plan for agentic deliveryRoute work by reversibility, then control intent, context, and acceptance. | guidedraft | 27 Oct 2026 |