{
  "about": "Which document holds what, so each topic is written in one place and the others link to it. spec/guards/delineation_spec.cr holds every document of the tree to this map; docs/knowledge-map.md is generated from it.",
  "kinds": {
    "guide": "written by hand, current, for people and agents",
    "definition": "the protocol's standard: changed only by the protocol's own rules",
    "data": "read by guards or code; edited by hand",
    "generated": "written from data; edit its source",
    "record": "kept as it stood, to say what happened",
    "stale": "no longer describes the code; awaiting the maintainer's decision"
  },
  "archives": [
    {
      "dir": "docs/battery",
      "index": "docs/battery/README.md",
      "holds": "each battery round's prompts, definitions and answers, kept as written"
    }
  ],
  "documents": [
    {
      "file": "README.md",
      "area": "Why OCX exists",
      "kind": "guide",
      "answers": "What is OCX, and what governs it?",
      "holds": [
        "the axioms",
        "the virtues",
        "the building blocks: Fossil, Crystal, Linux",
        "where the release is served"
      ]
    },
    {
      "file": "KEEP.md",
      "area": "Why OCX exists",
      "kind": "guide",
      "answers": "What has the maintainer said to keep?",
      "holds": [
        "the maintainer's standing directions, verbatim"
      ]
    },
    {
      "file": "PLAN.md",
      "area": "Why OCX exists",
      "kind": "guide",
      "answers": "What is OCX for, what guards it, and what is still missing?",
      "holds": [
        "the objective",
        "the precepts with their README virtues",
        "the functional gaps",
        "the work-unit and tool contract: an agent's MCP surface and the native agent for local models",
        "the phases",
        "the working rules"
      ]
    },
    {
      "file": "ROADMAP.md",
      "area": "Why OCX exists",
      "kind": "guide",
      "answers": "Where is each building block headed beyond this project?",
      "holds": [
        "the building blocks' direction"
      ]
    },
    {
      "file": "HISTORY.md",
      "area": "Why OCX exists",
      "kind": "record",
      "answers": "What was decided, and why?",
      "holds": [
        "where OCX came from",
        "the numbered decisions"
      ],
      "edit": "add a decision; never rewrite one"
    },
    {
      "file": "GLOSSARY.md",
      "area": "The words and the map",
      "kind": "guide",
      "answers": "What does a word mean here?",
      "holds": [
        "the project's words"
      ]
    },
    {
      "file": "ARCHITECTURE.md",
      "area": "The words and the map",
      "kind": "guide",
      "answers": "How do OCX's parts fit its purpose?",
      "holds": [
        "OCX's layers and their state",
        "how the parts are arranged"
      ]
    },
    {
      "file": "knowledge-map.json",
      "area": "The words and the map",
      "kind": "data",
      "answers": "Which document holds what?",
      "holds": [
        "which document holds each topic"
      ]
    },
    {
      "file": "docs/knowledge-map.md",
      "area": "The words and the map",
      "kind": "generated",
      "answers": "Which document holds what, to read?",
      "holds": [],
      "edit": "generated from knowledge-map.json"
    },
    {
      "file": "SCENARIOS.md",
      "area": "Using OCX",
      "kind": "guide",
      "answers": "How do I use OCX for a goal, and does each step work yet?",
      "holds": [
        "the maintainer's scenarios and the state of each step"
      ]
    },
    {
      "file": "USAGE.md",
      "area": "Using OCX",
      "kind": "guide",
      "answers": "What does each tool take and answer?",
      "holds": [
        "each tool's inputs and answers",
        "patterns and how to write one",
        "installing a node and the hook"
      ]
    },
    {
      "file": "AGENTS.md",
      "area": "Using OCX",
      "kind": "guide",
      "answers": "How does an agent work in this repository?",
      "holds": [
        "an agent's workflow in its workspace",
        "the check-in comment's form"
      ]
    },
    {
      "file": "docs/invite.md",
      "area": "Using OCX",
      "kind": "guide",
      "answers": "How does an invited agent join?",
      "holds": [
        "an invited agent's steps"
      ]
    },
    {
      "file": "docs/protocol-v1.md",
      "area": "Protocol v1",
      "kind": "definition",
      "answers": "What does protocol v1 define, what is it for, and what stays stable?",
      "holds": [
        "what protocol v1 is for",
        "the message kinds and their layers",
        "values",
        "the workspace, sandbox, limits and process layers",
        "subscriptions and delivery guarantees",
        "a run's life",
        "refusals",
        "ended's outcomes",
        "the protocol's words",
        "stability: what may be added and what never changes"
      ]
    },
    {
      "file": "docs/protocol-v1-fossil.md",
      "area": "Protocol v1",
      "kind": "definition",
      "answers": "What does protocol v1 rest on?",
      "holds": [
        "Fossil as the medium",
        "finding a message in an artifact",
        "who sent an artifact, and who may do what",
        "nodes: on the server and on other hosts",
        "versions"
      ]
    },
    {
      "file": "docs/protocol-v1-verdicts.md",
      "area": "Protocol v1",
      "kind": "definition",
      "answers": "How is a verdict written and counted?",
      "holds": [
        "writing and reading verdicts"
      ]
    },
    {
      "file": "docs/protocol-v1-tools.md",
      "area": "Protocol v1",
      "kind": "definition",
      "answers": "Which of OCX's tools write protocol v1's artifacts?",
      "holds": [
        "the tools for protocol v1 and where each is offered"
      ]
    },
    {
      "file": "docs/protocol-v1-examples.md",
      "area": "Protocol v1",
      "kind": "definition",
      "answers": "What do whole messages look like?",
      "holds": [
        "example messages with what a node writes back"
      ]
    },
    {
      "file": "docs/protocol-v1-failures.md",
      "area": "Protocol v1",
      "kind": "definition",
      "answers": "What comes of each failure or race?",
      "holds": [
        "the failure cases, numbered for the specs"
      ]
    },
    {
      "file": "docs/parity-v1.md",
      "area": "Building OCX",
      "kind": "guide",
      "answers": "What did trunk do that ocx2 lacks, and in what order is it built?",
      "holds": [
        "parity with trunk and the order to build"
      ]
    },
    {
      "file": "docs/interfaces.md",
      "area": "Building OCX",
      "kind": "guide",
      "answers": "Exactly what does each interface do, and which spec shows it?",
      "holds": [
        "each interface's behavior and its specs"
      ]
    },
    {
      "file": "docs/crystal.md",
      "area": "Building OCX",
      "kind": "guide",
      "answers": "How is OCX's Crystal written?",
      "holds": [
        "the rules for Crystal code"
      ]
    },
    {
      "file": "docs/fossil.md",
      "area": "Building OCX",
      "kind": "guide",
      "answers": "What has been learned about Fossil?",
      "holds": [
        "lessons about Fossil"
      ]
    },
    {
      "file": "docs/linux.md",
      "area": "Building OCX",
      "kind": "guide",
      "answers": "What has been learned about Linux?",
      "holds": [
        "lessons about Linux"
      ]
    },
    {
      "file": "docs/design/modules.json",
      "area": "What the code is made of",
      "kind": "data",
      "answers": "What is each module of src/ for?",
      "holds": [
        "each module's purpose and layer"
      ]
    },
    {
      "file": "docs/design/modules.md",
      "area": "What the code is made of",
      "kind": "generated",
      "answers": "What is each module of src/ for, to read?",
      "holds": [],
      "edit": "generated from docs/design/modules.json"
    },
    {
      "file": "docs/survey/functionality.json",
      "area": "What the code is made of",
      "kind": "data",
      "answers": "Which behavior does each file and spec serve?",
      "holds": [
        "each behavior with its parts and specs"
      ]
    },
    {
      "file": "docs/survey/gaps.json",
      "area": "What the code is made of",
      "kind": "data",
      "answers": "Which survey gaps are known?",
      "holds": [
        "the survey's known gaps"
      ]
    },
    {
      "file": "docs/design/facts.json",
      "area": "What the code is made of",
      "kind": "data",
      "answers": "Which Fossil settings does the code read?",
      "holds": [
        "the Fossil settings OCX reads"
      ]
    },
    {
      "file": "docs/precepts/precepts.json",
      "area": "What the code is made of",
      "kind": "data",
      "answers": "Which precepts do the guards hold?",
      "holds": [
        "the guarded precepts"
      ]
    },
    {
      "file": "docs/precepts/gaps.json",
      "area": "What the code is made of",
      "kind": "data",
      "answers": "Which precepts lack a guard, a refutation or a CI run?",
      "holds": [
        "the precepts' known gaps"
      ]
    },
    {
      "file": "docs/precepts/exceptions.json",
      "area": "What the code is made of",
      "kind": "data",
      "answers": "What is excepted from a precept, and why?",
      "holds": [
        "the precepts' exceptions"
      ]
    },
    {
      "file": "docs/precepts/pace.json",
      "area": "What the code is made of",
      "kind": "data",
      "answers": "How long may the gate take?",
      "holds": [
        "the gate's time limit"
      ]
    },
    {
      "file": "docs/design/events.json",
      "area": "What the code is made of",
      "kind": "stale",
      "answers": "Which events start code? It still describes the design before protocol v1",
      "holds": [
        "the events that start code"
      ],
      "edit": "the maintainer decides whether it is updated or removed"
    },
    {
      "file": "docs/design/sessions.json",
      "area": "What the code is made of",
      "kind": "stale",
      "answers": "How were sessions designed before protocol v1?",
      "holds": [
        "the sessions design before protocol v1"
      ],
      "edit": "the maintainer decides whether it is removed"
    },
    {
      "file": "docs/slices.md",
      "area": "Records",
      "kind": "record",
      "answers": "How was the rebuild first sliced?",
      "holds": [
        "the rebuild's first slices"
      ],
      "edit": "kept as it stood"
    },
    {
      "file": "docs/slices-parity.md",
      "area": "Records",
      "kind": "record",
      "answers": "How was parity with the ocx release first built?",
      "holds": [
        "the first parity slices"
      ],
      "edit": "kept as it stood"
    },
    {
      "file": "docs/slices-git.md",
      "area": "Records",
      "kind": "record",
      "answers": "How was the git round trip built?",
      "holds": [
        "the git round-trip slices"
      ],
      "edit": "kept as it stood"
    },
    {
      "file": "docs/slices-v1.md",
      "area": "Records",
      "kind": "record",
      "answers": "How was protocol v1 first built?",
      "holds": [
        "protocol v1's first slices"
      ],
      "edit": "kept as it stood"
    },
    {
      "file": "docs/review-v1.md",
      "area": "Records",
      "kind": "record",
      "answers": "What did the review of 2026-10-12 and 13 find?",
      "holds": [
        "the review of v1"
      ],
      "edit": "kept as it stood"
    },
    {
      "file": "docs/review-v1-tables.md",
      "area": "Records",
      "kind": "record",
      "answers": "What did the review of the tables draft find?",
      "holds": [
        "the review of the tables draft"
      ],
      "edit": "kept as it stood"
    },
    {
      "file": "docs/battery/README.md",
      "area": "Records",
      "kind": "record",
      "answers": "How did uninitiated readers fare on drafts of protocol v1?",
      "holds": [
        "the battery of uninitiated readers"
      ],
      "edit": "kept as it stood"
    }
  ]
}