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.

03-DESIGN/00-as-is/04-delivery.md

@@ -4,9 +4,9 @@ status: implemented
 code: [hal]
 updated: 2026-08-23
 decisions:
-  - 02-DECISIONS/0023-delivery.md
-  - 02-DECISIONS/0023-delivery.md
-  - 02-DECISIONS/0023-delivery.md
+  - 02-DECISIONS/0010-delivery.md
+  - 02-DECISIONS/0010-delivery.md
+  - 02-DECISIONS/0010-delivery.md
 ---
 
 # Delivery — from a push to a running node
@@ -31,7 +31,7 @@ merge that created no pipeline, and nothing said so**.
 ## Three silos
 
 Cardinality is the whole point, and the three differ
-([ADR 0023](../../02-DECISIONS/0023-delivery.md)):
+([ADR 0010](../../02-DECISIONS/0010-delivery.md)):
 
 | Silo | Runs | Where | Does |
 |---|---|---|---|
@@ -50,7 +50,7 @@ later stage runs.
 ## The artifact
 
 The artifact is **build output** — compiled and bundled with its dependency graph inlined —
-never a filtered copy of source ([ADR 0023](../../02-DECISIONS/0023-delivery.md)).
+never a filtered copy of source ([ADR 0010](../../02-DECISIONS/0010-delivery.md)).
 A deploy is extract-and-run and touches no network.
 
 The consequence is the whole cost of the decision: **anything not in the build output does not