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/008-delivery-coordinator/00-overview.md

@@ -3,12 +3,12 @@ status: graduated
 initiated: 2026-08-23
 touches:
   - 03-DESIGN/00-as-is/04-delivery.md
-  - 02-DECISIONS/0023-delivery.md
-  - 02-DECISIONS/0023-delivery.md
+  - 02-DECISIONS/0010-delivery.md
+  - 02-DECISIONS/0010-delivery.md
   - 01-RESEARCH/006-mesh-from-scratch/code-skeleton.md
 became:
-  - 02-DECISIONS/0023-delivery.md
-  - 02-DECISIONS/0023-delivery.md
+  - 02-DECISIONS/0010-delivery.md
+  - 02-DECISIONS/0010-delivery.md
 ---
 
 # 008 — The coordinator: a change checked in becomes a deployed state
@@ -49,14 +49,14 @@ working across the transition to self-hosted providers.
 because the first was honest about what it did not fix.
 
 **Does the coordinator dispatch stages, or converge nodes on a declaration?** — *Converge.*
-[ADR 0023](../../02-DECISIONS/0023-delivery.md): a pipeline ends when the
+[ADR 0010](../../02-DECISIONS/0010-delivery.md): a pipeline ends when the
 declaration is updated, and the host applies it and reads back — so the reporter is the applier.
 
 **Does the three-silo split survive?** — *Yes, with the third redefined.* The cardinality
 observation holds; the third silo is not a stage any more.
 
 **How does a change become a pipeline, reliably?** — *It does not become a pipeline at all.*
-[ADR 0023](../../02-DECISIONS/0023-delivery.md) applies 0058's
+[ADR 0010](../../02-DECISIONS/0010-delivery.md) applies 0058's
 move one level up: the control plane holds what source exists and what has been built, and builds
 the difference. **An event makes it fast; nothing makes it necessary.** The failures this effort
 catalogued — a truncated commit list, a broken path match — become latency rather than silence.
@@ -83,7 +83,7 @@ load-bearing question first.
 
 ## What is NOT closed by this
 
-[ADR 0023](../../02-DECISIONS/0023-delivery.md) names four costs
+[ADR 0010](../../02-DECISIONS/0010-delivery.md) names four costs
 and one of them is a real risk rather than a trade: **a reconciler that cannot reach its target
 retries forever, and without something that notices, the failure is silence** — which is the
 fault this effort exists to catalogue, reintroduced in a new place. That belongs to observability
@@ -96,6 +96,6 @@ and it is not designed.
 | What is a **deployed state**, and how does the mesh know it is in one? | Everything follows from this. If a stage reports transport, "deployed" is a claim nobody checked. A desired-state model with reconciliation gives a different answer from a job-completion model. |
 | Does the coordinator dispatch **stages**, or converge nodes on a **declaration**? | The current model is a state machine over stages. The alternative is that a node is told what should be true and reports what is. The second makes drift visible; the first cannot see it. |
 | How does a change **become** a pipeline, reliably? | Detection has failed for reasons unrelated to the change, silently. |
-| What produces a **verdict**, and what is it a verdict about? | Ties to the lab ([ADR 0009](../../02-DECISIONS/0009-the-lab.md)) and to a module carrying its own assertions. |
+| What produces a **verdict**, and what is it a verdict about? | Ties to the lab ([ADR 0016](../../02-DECISIONS/0016-the-lab.md)) and to a module carrying its own assertions. |
 | How does delivery work **before self-hosting**, and across the transition? | From research 006: source and artifacts start external and are re-bound to internal providers. The coordinator has to be indifferent to which. |
-| Does the **three-silo** split survive the artifact/part split? | [ADR 0023](../../02-DECISIONS/0023-delivery.md) is cardinality-driven, and research 006 renames the thing the cardinality is about. |
+| Does the **three-silo** split survive the artifact/part split? | [ADR 0010](../../02-DECISIONS/0010-delivery.md) is cardinality-driven, and research 006 renames the thing the cardinality is about. |