The numbering is the flow: decisions are 02, design is 03
papa-hq reads 01 research -> 03 decision -> 02 design. The order is a scar, not a choice: 02-DESIGN existed from its initial commit, and when adr/ was finally promoted on 2026-07-13 it took the next free number rather than its place in the sequence. By then design was too settled to renumber. hal-hq was three commits old, so it is not. adr/ becomes 02-DECISIONS and 02-DESIGN becomes 03-DESIGN, and following the folder numbers now walks the process in the order it happens: research produces a decision, the decision authorises a design. 00-GENESIS becomes 00-META, matching papa's rename from the same restructure. Every path reference rewritten across documents, frontmatter, playbooks and skills. All links resolve; all 58 frontmatter blocks parse and their path fields still point at files that exist.
This commit is contained in:
@@ -7,17 +7,17 @@ description: Use when a hal-hq research effort concludes and becomes design, or
|
||||
|
||||
Closes a research effort into a decision and a design, or amends an existing design.
|
||||
**Authoritative playbook:**
|
||||
[`00-GENESIS/process/02-graduation.md`](../../../00-GENESIS/process/02-graduation.md) — read
|
||||
[`00-META/process/02-graduation.md`](../../../00-META/process/02-graduation.md) — read
|
||||
it; this skill adds only the scaffolding.
|
||||
|
||||
## Steps
|
||||
|
||||
1. **Check against GENESIS** — `mission.md`, `context.md`, `effect.md`. If the conclusion
|
||||
conflicts, say which is wrong, in writing, before proceeding.
|
||||
2. **Write the decision record** in `adr/`, next free number, frontmatter per
|
||||
[`adr/README.md`](../../../adr/README.md). `reconstructed: false` — this one is being taken,
|
||||
2. **Write the decision record** in `02-DECISIONS/`, next free number, frontmatter per
|
||||
[`02-DECISIONS/README.md`](../../../02-DECISIONS/README.md). `reconstructed: false` — this one is being taken,
|
||||
not recovered. Record the rejected options.
|
||||
3. **Write the design** under `02-DESIGN/01-to-be/` with `layer: to-be`, `status: designed`,
|
||||
3. **Write the design** under `03-DESIGN/01-to-be/` with `layer: to-be`, `status: designed`,
|
||||
empty `code:`, today's `updated:`, and `decisions:` pointing at the record.
|
||||
4. **Close the effort** — the research `00-overview.md` gets `status: graduated` and `became:`
|
||||
pointing at both.
|
||||
@@ -31,7 +31,7 @@ Then edit the design and set `updated:`.
|
||||
|
||||
## When something ships
|
||||
|
||||
Write or update the matching `02-DESIGN/00-as-is/` document so it describes what now runs,
|
||||
Write or update the matching `03-DESIGN/00-as-is/` document so it describes what now runs,
|
||||
including anything that shipped differently from the intent. Set the to-be document's
|
||||
`status: implemented` and its `code:`. **The to-be document does not move** — both stand.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user