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/011-the-module-graph/analysis.md

@@ -36,7 +36,7 @@ another module's provision is treated as an implicit edge to that module**, so a
 not have to declare the same relationship twice.
 
 So *ordering by the graph* — which
-[ADR 0016](../../02-DECISIONS/0016-the-node-host.md) says
+[ADR 0005](../../02-DECISIONS/0005-the-node-host.md) says
 the control plane will do — is not a thing to build. It is a thing to call.
 
 ## Finding 3 — the most important edges in the mesh are invisible
@@ -82,7 +82,7 @@ means.
 ## Finding 4 — the resolver continues past faults it should stop on
 
 Two behaviours, both contrary to
-[ADR 0023](../../02-DECISIONS/0023-delivery.md):
+[ADR 0010](../../02-DECISIONS/0010-delivery.md):
 
 - **A cycle warns and falls back to input order.** A cycle means no correct order exists; the
   resolver proceeds with an arbitrary one and logs a line.
@@ -91,7 +91,7 @@ Two behaviours, both contrary to
 
 Neither has fired in the current catalogue — there are no cycles and nothing dangling — which
 is why nobody has noticed. They are latent, and they are in the component that
-[ADR 0016](../../02-DECISIONS/0016-the-node-host.md) makes
+[ADR 0005](../../02-DECISIONS/0005-the-node-host.md) makes
 responsible for the ordering a host will apply without question.
 
 ## Finding 5 — placement is decided in the catalogue