Renumber the records 1 to 23

The consolidation left a sparse sequence -- 1, 4, 6, 7, 9, 10, 12, 15, 16, 18,
19, 25, 34, 35, 36, 37, 40, 42, 44, 45, 48, 49, 58 -- where the gaps were only
the archaeology of what used to be there.

Renumbered contiguously. Renames run in ascending order, so every target number
is already free and no two files ever collide.

The reference rewrite is one simultaneous pass rather than a sequence of
replacements. Numbers moved into slots other numbers were vacating -- the node
host went 37 to 16 while the lab went 16 to 9 -- so replacing one at a time
would have cascaded and silently pointed things at the wrong record.

Seven plain-text references survived the merges as prose rather than links,
naming records that no longer existed: the enrolment token, the link boundary,
what a declaration is, reachability, the repository structure. Each mapped to
the consolidated record that now holds it.

Verified rather than assumed: every [ADR NNNN](path) link now has matching text
and target, checked across the whole repository, and the checker passes.

Frontmatter `consolidates:` lists dropped -- they named records that are gone,
and each consolidated record already says in prose what it absorbed.

03-DESIGN/00-as-is/00-overview.md

@@ -5,8 +5,8 @@ code: [hal]
 updated: 2026-08-23
 decisions:
   - 02-DECISIONS/0001-nodes-communicate-over-a-broker.md
-  - 02-DECISIONS/0044-modules-and-the-graph.md
-  - 02-DECISIONS/0048-the-substrate-and-the-control-plane.md
+  - 02-DECISIONS/0019-modules-and-the-graph.md
+  - 02-DECISIONS/0021-the-substrate-and-the-control-plane.md
 ---
 
 # The mesh as it stands
@@ -28,11 +28,11 @@ onto it and can be regenerated.
 containerised service is a module. A set of capabilities with no service behind them is a
 module. A bare marker whose whole content is that a node has it is a module. The mesh's own
 components are modules on exactly the same terms as everything else it carries
-([ADR 0044](../../02-DECISIONS/0044-modules-and-the-graph.md)).
+([ADR 0019](../../02-DECISIONS/0019-modules-and-the-graph.md)).
 
 **An agent** is a participant. Some agents are human. What differs is modality — how the agent
 acts — and not category: both hold identity, both act, both accumulate memory
-([ADR 0012](../../02-DECISIONS/0012-agents-are-persistent-employees.md)).
+([ADR 0007](../../02-DECISIONS/0007-agents-are-persistent-employees.md)).
 
 ## Where truth lives
 
@@ -40,10 +40,10 @@ The repository defines **what exists**: the modules, what each declares, how eac
 
 The mesh database defines **what runs where**: which node is assigned which module, at which
 selection, with which overrides, plus the settings every node reads. No node-to-module mapping
-is ever committed ([ADR 0048](../../02-DECISIONS/0048-the-substrate-and-the-control-plane.md)).
+is ever committed ([ADR 0021](../../02-DECISIONS/0021-the-substrate-and-the-control-plane.md)).
 
 Everything on a node's disk is **derived** from those two, and is regenerated rather than
-edited ([ADR 0004](../../02-DECISIONS/0004-managed-files-are-generated-never-edited.md)). A node that
+edited ([ADR 0002](../../02-DECISIONS/0002-managed-files-are-generated-never-edited.md)). A node that
 loses its database keeps running from a local cache, which is deliberate and has the obvious
 cost: the cache carries no indication of its own age.
 
@@ -65,9 +65,9 @@ goes to where the capability is.
 A push to the forge is the only trigger. What follows is three silos with deliberately
 different cardinality: compile once, package and upload once, then install-configure-start-
 verify **on every assigned node**
-([ADR 0058](../../02-DECISIONS/0058-delivery.md)). What travels between
+([ADR 0023](../../02-DECISIONS/0023-delivery.md)). What travels between
 build and node is a self-contained build output, so a deploy is extract-and-run and touches no
-network ([ADR 0058](../../02-DECISIONS/0058-delivery.md)).
+network ([ADR 0023](../../02-DECISIONS/0023-delivery.md)).
 
 Modules are resolved into dependency levels and a level completes before the next begins, so a
 module always builds against its dependencies as they were just published.
@@ -78,7 +78,7 @@ A module declares what it **provides** and what it **requires**. The mesh satisf
 requirement: it creates the resource, generates the credential, records the grant, and writes
 the values where the module will read them. The module never learns which node its database
 lives on, and nobody ever writes a credential by hand
-([ADR 0044](../../02-DECISIONS/0044-modules-and-the-graph.md)).
+([ADR 0019](../../02-DECISIONS/0019-modules-and-the-graph.md)).
 
 This is the property the mesh's whole shape rests on, and it is why provisioning is treated as
 a core concern rather than as plumbing.
@@ -92,7 +92,7 @@ named for a feature the module does not declare, a stage that reported it had di
 message rather than that the effect happened, a package that 404ed from every mirror while the
 job went green.
 
-[ADR 0058](../../02-DECISIONS/0058-delivery.md) is the response, and it is applied
+[ADR 0023](../../02-DECISIONS/0023-delivery.md) is the response, and it is applied
 instance by instance rather than enforced by a mechanism. New instances are still being found.
 That is an as-is fact, not a criticism: it is the single most useful thing to know about this
 system before changing it.