novox/hq
3
0
Fork 0
Code Issues 2 Pull Requests Releases Wiki Activity

The numbering is the flow: decisions are 02, design is 03

Browse Source 
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:
jschoubben
2026-08-23 18:05:11 +02:00
parent f05e4a0dce
commit c0b35652d0
72 changed files with 217 additions and 204 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.claude/skills/hal-handoff/SKILL.md
+4 -4
View File
@@ -6,18 +6,18 @@ description: Use when a hal-hq design is settled and implementation is about to
# hal-handoff
Hands a settled design to a code repository. **Authoritative playbook:**
[`00-GENESIS/process/04-build-handoff.md`](../../../00-GENESIS/process/04-build-handoff.md).
[`00-META/process/04-build-handoff.md`](../../../00-META/process/04-build-handoff.md).
## Steps
1. **Confirm it is settled.** `status: designed`, and every claim traceable to a record in
`adr/`. An open question in the text is a reason to run `hal-new-research`, not to build
`02-DECISIONS/`. An open question in the text is a reason to run `hal-new-research`, not to build
around it.
2. **Name the owner.** Set `code:` from
[`00-GENESIS/repos.md`](../../../00-GENESIS/repos.md). If the repository does not exist yet,
[`00-META/repos.md`](../../../00-META/repos.md). If the repository does not exist yet,
add it to `repos.md` in the same change.
3. **Read the as-is counterpart.** What is being replaced must be written down in
`02-DESIGN/00-as-is/` before it is changed. Building against an undocumented as-is is how
`03-DESIGN/00-as-is/` before it is changed. Building against an undocumented as-is is how
shipped behaviour gets lost.
4. **Flip the status** to `in-progress`, `updated:` today.
5. Build in the code repository. hal-hq never carries implementation.