intent-graphlisted

# The intent graph `intent/` holds small markdown files describing why this repo exists and what is currently being built. Every file has frontmatter and hangs off a parent, forming one chain: **mission → bet → goal → project → story**. `user` and `problem` sit off to the side as the facts about the world that the chain answers to. Run `coherence graph` to see it. Run `coherence focus <id>` to see one artifact's chain up to the mission. (Commands assume `coherence` on PATH; a repo may vendor it at `bin/coherence` instead. Use whichever exists.) ## Before writing code Check what is in focus with `coherence focus`. If nothing is, find the artifact this work serves and focus it. If no artifact covers the work, that is the real finding, so say so before writing anything. Work with no stated intent is exactly what this repo exists to catch. ## The types | type | one per | says | |---|---|---| | `mission` | repo | why this exists at all | | `bet` | several | "I believe X, so I'm doing Y instead of Z", falsifiable | | `goal` | per bet | how you'd know the bet paid off; carries a `measure:` | | `user` | few | a specific person in a specific situation | | `problem` | per user | what goes wrong, told as a moment rather than a category | | `architecture` | per bet | a structural decision and what it forecloses | | `project` | per goal | a chunk of work big enough to matter, small enough to finish | | `story` | per project | one observable change, with acceptance criteria | | `dom