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/010-lab-inner-loop-cost/00-overview.md

@@ -3,8 +3,8 @@ status: active
 initiated: 2026-08-24
 touches:
   - 03-DESIGN/01-to-be/03-scenario-lifecycle.md
-  - 02-DECISIONS/0009-the-lab.md
-  - 02-DECISIONS/0009-the-lab.md
+  - 02-DECISIONS/0016-the-lab.md
+  - 02-DECISIONS/0016-the-lab.md
 became: []
 ---
 
@@ -23,7 +23,7 @@ Measured on a workstation, 2026-08-24. Numbers in [`measurements.md`](measuremen
 
 ## Why it matters
 
-[ADR 0009](../../02-DECISIONS/0009-the-lab.md) makes the
+[ADR 0016](../../02-DECISIONS/0016-the-lab.md) makes the
 bootstrap scenario the inner development loop for tiers 0 and 1 — the argument being that
 raising a node from nothing stops being the least-exercised path and becomes the most-exercised
 one. **That argument is only true if raising and resetting are cheap.** A loop that costs

01-RESEARCH/010-lab-inner-loop-cost/measurements.md

@@ -13,7 +13,7 @@ image.
 
 | Fact | Value | Consequence |
 |---|---|---|
-| Hardware virtualisation | present | virtual machines run at native speed; the choice in [ADR 0009](../../02-DECISIONS/0009-the-lab.md) is not paying an emulation penalty |
+| Hardware virtualisation | present | virtual machines run at native speed; the choice in [ADR 0016](../../02-DECISIONS/0016-the-lab.md) is not paying an emulation penalty |
 | Storage drivers the daemon offers | **`dir` only** | no copy-on-write, therefore no cheap snapshot |
 | Host filesystems | ext4 throughout | nothing copy-on-write to put a pool on |
 | btrfs kernel module | **available** | the kernel can do it |
@@ -72,7 +72,7 @@ worst, before any of the mesh's own work begins.
 
 **This is too slow for an inner loop**, and the reason is not the design.
 
-[ADR 0009](../../02-DECISIONS/0009-the-lab.md) argues that
+[ADR 0016](../../02-DECISIONS/0016-the-lab.md) argues that
 making the bootstrap path the inner development loop turns the least-exercised code in the
 system into the most-exercised. That argument holds only while resetting is cheap. At a minute
 and a half a cycle, with occasional multi-minute stalls, the loop is one a person works around
@@ -120,7 +120,7 @@ A four-machine reset-and-rerun cycle, the operation the inner loop repeats most:
 | **cycle** | **~90 s, unbounded at worst** | **~15 s, dominated by boot** |
 
 At fifteen seconds, dominated by a boot that cannot be avoided, the inner loop is viable and
-[ADR 0009](../../02-DECISIONS/0009-the-lab.md)'s argument holds.
+[ADR 0016](../../02-DECISIONS/0016-the-lab.md)'s argument holds.
 At ninety it did not.
 
 ### One honest counter-observation