Order the records the way the system is learned

Jochen asked whether the order made sense. It did not -- it followed when
things happened to be decided, which after consolidation is fictional anyway
since record 5 alone folds decisions taken across a week.

Concretely wrong before: the domain statement sat at 8, after five engineering
rules; the constitution was scattered across 5, 12 and 17; the tiers landed at
15, 16, 21 and 22 with process records in between.

Now it walks: what the mesh is (1-3), its tiers from the bottom up (4-8), what
runs on them and how it gets there (9-10), how it is built (11-16), how it is
checked (17-18), how we work (19-23).

Two things made this safe rather than free. It is a permutation, not a
compaction, so the renames go through temporary names -- otherwise two files
want one slot and one is lost. And the reference rewrite is a single
simultaneous pass, because almost every number moved into a slot another number
was vacating; replacing one at a time would have cascaded and pointed things at
the wrong record while still resolving.

Verified: 284 [ADR NNNN](path) links across the repository, all with matching
text and target.

The ordering principle is now stated in 19 rather than left implicit -- the
repository already said "the numbering is the flow" about its folders, and
there was no reason for the records to be the exception.

01-RESEARCH/012-the-minimum-viable-node/00-overview.md

@@ -2,8 +2,8 @@
 status: active
 initiated: 2026-08-26
 touches:
-  - 02-DECISIONS/0016-the-node-host.md
-  - 02-DECISIONS/0002-managed-files-are-generated-never-edited.md
+  - 02-DECISIONS/0005-the-node-host.md
+  - 02-DECISIONS/0011-managed-files-are-generated-never-edited.md
   - 03-DESIGN/01-to-be/05-the-node-host.md
   - 03-DESIGN/00-as-is/05-runtime-and-installation.md
   - 01-RESEARCH/011-the-module-graph/00-overview.md
@@ -34,7 +34,7 @@ carry everything in the bundle, download at apply time, or have something push t
 first. Downloading fails on the first node, which cannot fetch the image registry from the image
 registry it is trying to start.
 
-> **Qualified by [ADR 0021](../../02-DECISIONS/0021-the-substrate-and-the-control-plane.md).** The
+> **Qualified by [ADR 0006](../../02-DECISIONS/0006-the-substrate-and-the-control-plane.md).** The
 > reframing below still holds for what a *tailored installer* contains — the missing pieces for a
 > given machine. It does **not** have to hold for container images: the installer fetches those
 > by digest, because a real machine has a network and the sealed case is the lab.
@@ -71,13 +71,13 @@ records adoption of a pre-existing machine's configuration as the original mecha
 legacy and explicitly out of scope for the lab. It returns here for a different reason than it
 was dropped for, which is a thing to notice rather than to gloss.
 
-**It creates a state that does not exist today.** [ADR 0002](../../02-DECISIONS/0002-managed-files-are-generated-never-edited.md)
+**It creates a state that does not exist today.** [ADR 0011](../../02-DECISIONS/0011-managed-files-are-generated-never-edited.md)
 has managed files generated and never edited; adoption needs a one-time import before that rule
 starts applying. Three states, and the middle one is new:
 
 > unmanaged → **adopted once** → generated
 
-**And it crosses a boundary just drawn.** [ADR 0016](../../02-DECISIONS/0016-the-node-host.md)
+**And it crosses a boundary just drawn.** [ADR 0005](../../02-DECISIONS/0005-the-node-host.md)
 says the host never touches what it did not create — the rule that stops a converger deleting
 what the mesh never put there. Adoption is the deliberate act of taking ownership of exactly
 that. The rule needs a companion rather than an exception: *never, unless adoption made it the