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/cases.md

@@ -13,7 +13,7 @@ it is simply up. *A relational store, a message broker, an object store, a dashb
 
 **2 — A system package with configuration.** Not a container. Installed into the machine,
 configured through files, run by the service manager. *A firewall, a resolver, an overlay.*
-Note: [ADR 0016](../../02-DECISIONS/0016-the-node-host.md) says applying
+Note: [ADR 0005](../../02-DECISIONS/0005-the-node-host.md) says applying
 these is the host's job — so what the module contributes is the *deciding*, not the doing.
 
 **3 — An application a person launches.** Installed on a node, started by a human, running only
@@ -35,7 +35,7 @@ provider behind an assistant interface.*
 
 **9 — A standalone application in its own repository.** Same shape as any of the above; the
 difference is only where its source lives
-([ADR 0006](../../02-DECISIONS/0006-applications-live-in-their-own-repository.md)). Worth
+([ADR 0015](../../02-DECISIONS/0015-applications-live-in-their-own-repository.md)). Worth
 listing because a schema that assumes a monorepo path would exclude it.
 
 ## The cases that break a naive schema