canonlisted

# Canon Understand project governance before you act, so you do not spread heresy. ## Articles of truth Identify the authorities that bear on your task, then read the ones that carry meaning for it — not all of them, every time. The CLI is the source of truth — see [[mem.fact.doctrine.cli-source-of-truth]]. - `CLAUDE.md`, `AGENTS.md` — standing instructions and conventions. Project conventions are documented in [[mem.pattern.doctrine.conventions]]. - project governance - list each of these; read any which are potentially relevant in full, with `doctrine <kind> show <id>`: - `doctrine spec list` - specs describing product intent / technical architecture - `doctrine adr list` - architecture decision records - `doctrine policy list` - policies - `doctrine standard list` - standards of practice - the governing slice's `design.md` — canon for *this* change's design intent. For implementation truth (gotchas, patterns, invariants tied to files or commands), `/retrieve-memory` rather than rediscovering it. **Read entities tier-aware — via `show`, never a single raw file.** The storage rule + read-via-`show` discipline are resident in the boot digest and detailed in `using-doctrine.md`. The storage model and storage rule are documented in [[mem.concept.doctrine.storage-model]]; storage tiers: authored, runtime, derived — see [[mem.fact.doctrine.storage-tiers]]. Reading one tier and concluding "empty" is false witness. ## The mortal sins Beware — and refuse to co