ultragoal

1# Ultragoal — the closed loop for goals too big to ship in one run
2 
3An **ultragoal** is the term for a north-star that spans many sessions: fork the repos, combine the strong parts, ship one product. A `/closed-loop` run is one task through the loop. An ultragoal is a *chain of phases*, each of which is its own full closed-loop run, tracked so any cold session can resume.
4 
5**Core rule (from dwarves-kit, adopted fully): the worker never grades its own homework, and wrongness compounds across sessions — so verify every phase, not just the end.**
6 
7## When to use
8 
9- `/ultragoal <name>` — resume or advance an existing ultragoal
10- `/ultragoal new "<north-star>"` — charter a new one
11- `/ultragoal status` — report all ultragoals from the registry
12- Trigger phrases: "make this an ultragoal", "this is a long-running goal", "combine these into one product over time"
13 
14Do **not** use for single-run work (that is `/closed-loop`), and do not start one on a request that never asked for one. Rule of thumb: if it needs a phase decomposition and won't finish today, it is an ultragoal.
15 
16## Files (one goal = one folder)
17 
18| File | Role |
19|---|---|
20| `04-projects/harness/ultragoals.md` | Registry: every ultragoal, status, current phase |
21| `04-projects/<goal>/spec.md` | Contract: north-star + `AC-n` acceptance criteria + phases `P0…Pn` + traceability matrix |
22| `04-projects/<goal>/STATUS.md` | Living ledger: phase state, current phase, open `AC-n`, next action (resume from here) |
23…