knowledge-priming

# Knowledge Priming ## Config Resolution 1. Look for `.lattice/config.yaml` in the repo root. 2. If found, check `paths.knowledge_base` for a custom document path. 3. If a document exists at that path, read the full document. 4. **STOP: Apply the loaded document as ambient context before any design, implementation, or review work begins.** 5. If a path is configured but no document exists at it → tell the user which configured path is missing, then see "When No Document Exists". 6. If there is no config file or no `paths.knowledge_base` key → see "When No Document Exists". ## When No Document Exists Inform the user: > No project knowledge base found. AI skills will operate from generic assumptions about tech stack, architecture, and conventions. > > To create one, trigger **knowledge-priming-refiner** — a guided interview (~10 questions) producing a concise document (~50 lines). > > You can also create `.lattice/standards/knowledge-base.md` manually and reference it in `.lattice/config.yaml` under `paths.knowledge_base`. Do not block. Continue without the knowledge base. ## What the Document Contains | # | Section | What It Captures | |---|---------|-----------------| | 1 | **Architecture Overview** | App type, major components, how they interact | | 2 | **Tech Stack and Versions** | Specific technologies with version numbers, including "not X" clarifications | | 3 | **Curated Knowledge Sources** | Official docs, trusted blogs, internal references (5–10 max) | | 4 | *...