{
  "site": {
    "title": "Docs: one place for every document",
    "description": "The source of truth for project documents: proposals, build specs, and flows. One index, meaningful names, and symlinks from each project."
  },
  "categories": [
    {
      "id": "projects",
      "title": "Project documents",
      "description": "Design, build, and operations documents for one project. Each project keeps its sources, its build manifest, and its final pages in one folder.",
      "items": [
        {
          "title": "Claude Fleet: one identity per container",
          "path": "projects/claude-fleet/fleet-leadership.html",
          "kind": "proposal",
          "project": "Claude Fleet",
          "summary": "The 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.",
          "status": "current",
          "updated": "2026-10-26"
        },
        {
          "title": "Claude Fleet: build spec and task plan",
          "path": "projects/claude-fleet/fleet-spec.html",
          "kind": "spec",
          "project": "Claude Fleet",
          "summary": "The build spec for Claude Fleet. It holds the requirements, the tracked tasks, the target architecture, the open decisions, and the acceptance checklist.",
          "status": "current",
          "updated": "2026-10-26"
        },
        {
          "title": "Fleet Flows: how a request travels",
          "path": "projects/claude-fleet/fleet-flows.html",
          "kind": "flows",
          "project": "Claude Fleet",
          "summary": "How a request travels through Claude Fleet. It shows five scenarios, the container anatomy, the exact configuration, and the isolation contract.",
          "status": "current",
          "updated": "2026-10-26"
        }
      ]
    }
  ]
}