Meridians documentation

# Meridians documentation

The documentation is a routed knowledge system, not a god document. Use the generated [Knowledge Atlas](generated/KNOWLEDGE_ATLAS.md) for the macro picture across corpus weight, concepts, links, authority, and status. Use the tree below to enter the smallest branch that answers your question; a leaf owns one concept and links only to its immediate neighbours.

```text
knowledge-base/
├── knowledge/     maintained, authored concept hubs
│   ├── foundations/   values and durable framing
│   ├── product/       promise, people, behaviour, strategy, and economics
│   ├── vocabulary/    canonical concept leaves
│   ├── architecture/  runtime, canonical state, and boundaries
│   ├── governance/    permission and security contracts
│   ├── operations/    configuration, release, and Hosted support
│   ├── conventions/   repeatable model, narrative, and UI rules
│   ├── worlds/        authored fictional canon and structured world contracts
│   └── plans/         intentionally future-facing specifications
├── diagrams/      maintained visual leaves, grouped by concept / flow / UI
├── personas/      maintained audience and onboarding leaves
├── specs/         bounded proposals that graduate into a maintained leaf when shipped
├── generated/     machine-produced reference and evidence; never hand-edit
└── insights/      local diagnostic bundles; generated, ignored, and never authoritative
```

## Choose a branch

- **Learning the product or making a product decision:** [product](knowledge/product/README.md)
- **Changing code, state, API, or UI structure:** [architecture](knowledge/architecture/README.md)
- **Running, securing, configuring, or releasing an instance:** [operations](knowledge/operations/README.md)
- **Defining or checking a product term:** [vocabulary](knowledge/vocabulary/README.md)
- **Changing authority, access, or a security boundary:** [governance](knowledge/governance/README.md)
- **Naming or applying a repeatable rule, including copy/localisation:** [conventions](knowledge/conventions/README.md)
- **Reading or extending first-party fictional canon:** [worlds](knowledge/worlds/README.md)
- **Assessing an unshipped change:** [plans](knowledge/plans/README.md)
- **Inspecting a code projection, measured debt, or an all-in-one diagram export:** [generated](generated/README.md)
- **Seeing the macro knowledge picture beyond hierarchy:** [Knowledge Atlas](generated/KNOWLEDGE_ATLAS.md)
- **Reviewing local repository, knowledge, static, economics, or forecast signals:** [insight bundles](insights/README.md)

Maintained leaves are the source of truth. Generated reference is a local artefact — git-ignored, materialised by `npm install` and rebuilt with `npm run gen:all` — so an unrelated branch never conflicts over a projection of the code; `npm run knowledge:check` verifies the committed budgets that ratchets measure a push against. The coding-agent router is [../AGENTS.md](../AGENTS.md).

Raw Markdown source