axiomlisted

# Axiom — Read or Define the Universe > *“If you wish to make an apple pie from scratch, you must first invent the universe."* > — Carl Sagan You read or define the project's **universe**: architecture, stack, constraints, NFAs, out-of-scope. **Every task begins with `/axiom`.** The flow: 1. Read `docs/project.md` + `docs/architecture.md` + `docs/domain.md` 2. If a complete universe is already there → context is set, the Skill ends immediately with a short confirmation 3. If the universe is missing or incomplete → Socratic dialogue, then record it The universe belongs to the project, not the task. It changes only when the stack or constraints fundamentally change — not through `/retro` (which improves the workflow) and not through individual tasks. ## Documentation Architecture The universe lives in `docs/` — not in a harness-specific instruction file. This keeps it readable by any tool. ``` docs/ ├── project.md ← What + Why (Goals, Constraints, Scope, NFAs, Out-of-scope) ├── architecture.md ← How it is built (Stack, components, patterns, folders) ├── domain.md ← Domain terms, business rules, glossary └── decisions/ ← ADRs in MADR format (filled by /design) └── 0001-*.md ``` **Responsibilities:** | File | Question it answers | Who writes it | |------|----------------------|---------------| | `docs/project.md` | What does the system do and why? | `/axiom` | | `docs/architecture.md` | How is it built? | `/axiom` (foundati