project-cortex

# Project Cortex: ADR + Epic + Task + Wiki > Automation over memory. Use CLI for IDs and templates. Use index for discovery. ## Three Systems ``` Epic (WHY) ADR (HOW) Task (WHAT) requirement origin technical decision executable work derives tasks guides tasks links to epic/adr ``` **OS analogy**: Think of the governance system like an operating memory model. | Component | OS Analogy | Role | |-----------|-----------|------| | **Epic** | Memory segment (heap) | Stores the full context — background, requirement tree, zoom-in map. **Workflowy-style**, not a todo list. | | **ADR** | Code segment (text) | Stores ratified decisions — options considered, consequences, follow-ups. Immutable once accepted. | | **Wiki** | Shared library | Reusable knowledge extracted after tasks complete. Patterns, FAQs, lessons. | | **Task** | **Pointer / Reference** | A task card is a `pointer` to epic/adr context plus executable instructions. It does **not** inline the full epic or ADR body — that would be "pass by value" and create drift. | **Pass by reference, not by value**: A task card should contain precise pointers (`Refs: EPIC-xxx`, `See ADR-yyy §Decision`, `Modify: src/path.ts`) so a subagent can navigate to source of truth. The card is a **map**, not a warehouse. A new team member reading only AGENTS.md + the task card should be able to find everything needed without asking for clarification. ## CLI Commands ```bash # Create documents (CLI assigns time...