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/004-lab-network/00-overview.md

@@ -1,8 +1,8 @@
 ---
 status: active
 initiated: 2026-08-22
-touches: [02-DESIGN/00-as-is/01-mesh-and-transport.md, 02-DESIGN/01-to-be/01-end-to-end-testing.md]
-became: [adr/0016-a-lab-node-is-a-virtual-machine.md]
+touches: [03-DESIGN/00-as-is/01-mesh-and-transport.md, 03-DESIGN/01-to-be/01-end-to-end-testing.md]
+became: [02-DECISIONS/0016-a-lab-node-is-a-virtual-machine.md]
 ---
 
 # 004 — Reproducing the mesh network in a lab

01-RESEARCH/004-lab-network/analysis.md

@@ -199,5 +199,5 @@ Several manifests declare `scope: public` on firewall rules — `wireguard`, `tr
 `modules/unifi/module.yml:52-93` does deliberately.
 
 So a manifest can appear to restrict a port to the public scope and in fact restrict nothing.
-This is the same shape as the rule in `00-GENESIS/how-we-build.md` — *an unenforced rule is
+This is the same shape as the rule in `00-META/how-we-build.md` — *an unenforced rule is
 indistinguishable from a wrong one, and costs more, because people believe it.*