knowledge-base

Knowledge Base Foundation Before You Start Read these docs to orient yourself: docs/glossary.md - Terminology (Cell, Piece, Space, Spell, etc.) docs/specs/pattern-construction/overview.md - Authoritative system design AGENTS.md - Documentation reading list and codebase guidelines Source Hierarchy When sources conflict, this is the authoritative order: 1. Specs (Highest Authority) docs/specs/ - Technical specifications with unambiguous intent When specs contradict other docs, specs win . 2. Working Code Tests and patterns that demonstrate actual behavior: packages/patterns/ - Pattern examples showing what works /test/ - Test files proving expected behavior These show reality, not aspirations. 3. Runtime Code Core system implementation: packages/runner/ - Execution engine packages/runner/src/builder/ - Compilation packages/memory/ - Storage layer Code is always right about what it does. 4. Plain Text Docs (Lowest Authority) docs/common/ - Guides, tutorials, learning materials Good for learning, but may contain outdated or speculative information. Validate against code when precision matters. The Rule Concrete beats abstract. Specifications beat speculation. Code beats comments. Tests beat documentation. When Sources Conflict Check specs first ( docs/specs/ ) Look at working code (tests, patterns) Read runtime implementation Use docs/common as learning guide only If still unclear, surface the conflict explicitly