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.

01-RESEARCH/003-service-supervision/analysis.md

@@ -196,7 +196,7 @@ hand.
 This is worth recording for two reasons. It weakens any argument that systemd-adjacent
 self-healing is already wired — it is not. And it is another instance of the pattern this
 whole refactor is about: **a documented mechanism that does not exist, believed because it
-was written down.** `00-GENESIS/how-we-build.md` calls this out as a rule; here it is again,
+was written down.** `00-META/how-we-build.md` calls this out as a rule; here it is again,
 found by grep.
 
 ---
@@ -208,7 +208,7 @@ found by grep.
 **This no longer gates Phase 0.** When this was written, the local mesh was assumed to be
 built from application containers, which forced the question — there is no natural way to
 run an init system inside one. The decision of 2026-08-22 to build development nodes as
-**system containers** (see [`02-DESIGN/01-end-to-end-testing.md`](../../02-DESIGN/01-to-be/01-end-to-end-testing.md))
+**system containers** (see [`03-DESIGN/01-end-to-end-testing.md`](../../03-DESIGN/01-to-be/01-end-to-end-testing.md))
 removes that pressure entirely: a system container runs a real init, so the existing model
 works unmodified and the lab needs no answer here to exist.
 
@@ -223,7 +223,7 @@ fate-sharing reason in §3.
 ## References
 
 - [`002-local-mesh`](../002-local-mesh/analysis.md) — the effort this came out of
-- [`adr/0001`](../../adr/0015-mesh-brokers-nodes-host-agents-think.md) — agent modality, which
+- [`02-DECISIONS/0001`](../../02-DECISIONS/0015-mesh-brokers-nodes-host-agents-think.md) — agent modality, which
   decides what cannot leave the host
 - `modules/hal/meshware/daemon/src/cerebellum.ts:815-828` — the self-restart workaround
 - `modules/hal/meshware/systemd/hal-module@.service` — the per-module Docker lifecycle