Consolidate: 65 decision records to 52

Jochen: a normal application has 3-5 ADRs, maybe 10 for a large one, and we are at 65. Fair, and the cause is mine -- I recorded every FINDING as a decision rather than every fork in the road. Two merges, both cases where one decision had been split across many records because it was taken over several days rather than at once. 0019 absorbs ten records about how this repository works: what it is and that it is public, the folder flow, the two design layers, the issue front door, status in frontmatter, playbooks, the naming rule, the product name. Those were never ten decisions -- they were one, seen from ten angles as the repository took shape. 0016 absorbs the five about the lab: a node is a virtual machine, a router is scenery, a scenario declares the underlay, a scenario is a closed address space, and the two scenario classes. Same pattern -- one design, split by the order it was worked out in. The consolidated 0019 also raises the bar for what earns a record, since that is what produced 65: a record is warranted when there is a genuine fork -- a direction reversed, an alternative that will be proposed again, something contested. A finding is not a decision, and a bug is certainly not. Everything else belongs in the design document where the reasoning is actually read. The checker earned its place here. Deleting nine records left 13 dangling links across the repository and it named every one, including in AGENTS.md. Nothing was found by reading. Remaining clusters worth the same treatment: the host (8 records), delivery (5), modules (6), connectivity (4), substrate and control plane (4). That would be 52 down to roughly 30.
2026-08-28 18:53:19 +02:00
parent 10365f2eae
commit 5e83ac2c22
48 changed files with 265 additions and 1257 deletions
@@ -38,7 +38,7 @@ This is an instance where it was never applied.
 ## Evidence

 - Observed 2026-08-22 while declaring the virtualisation package required by
-  [ADR 0016](../../02-DECISIONS/0016-a-lab-node-is-a-virtual-machine.md).
+  [ADR 0016](../../02-DECISIONS/0016-the-lab.md).
 - A fix is written and open as a pull request, unmerged since 2026-08-20.

 ## Open questions
@@ -21,7 +21,7 @@ recoverable by retrying — it removes the ability to issue a certificate anyone

 The consequence lands hardest on exactly the work most likely to iterate: standing up a new
 node, changing how names resolve, or testing the lab's certificate authority split
-([ADR 0016](../../02-DECISIONS/0016-a-lab-node-is-a-virtual-machine.md)).
+([ADR 0016](../../02-DECISIONS/0016-the-lab.md)).

 ## Evidence

@@ -59,7 +59,7 @@ checked it — including in the same commit that wrote the rule.
 ## Proposed direction — Nox is the search

 *Added 2026-08-23.* Rather than syncing these documents into the knowledge base, **Nox
-([ADR 0027](../../02-DECISIONS/0027-the-product-is-novox-mesh.md)) works from within this
+([ADR 0019](../../02-DECISIONS/0019-how-this-repository-works.md)) works from within this
 repository and holds its knowledge directly.** Retrieval becomes an agent reading the source,
 not a copy living in a second store.

@@ -44,7 +44,7 @@ The distance between the two is the same one the delivery layer already has a na
 ## Why it matters now

 This is the first requirement of the lab
-([ADR 0029](../../02-DECISIONS/0029-the-labs-first-scenario-has-no-pipeline.md)), which is
+([ADR 0016](../../02-DECISIONS/0016-the-lab.md)), which is
 phase 0 of the entire migration. The first capability the new work depends on is present,
 declared, and unusable — and would have stayed unusable silently.

@@ -74,7 +74,7 @@ It also removes the lab's export-and-push mechanism rather than fixing it, which
 outcome: pushing image tarballs over the hypervisor was always a lab-only invention.

 **Not decided here**, because it is design rather than repair: where the registry runs, whether
-it is scenery like the router ([ADR 0033](../../02-DECISIONS/0033-a-router-is-scenery-not-a-node.md))
+it is scenery like the router ([ADR 0016](../../02-DECISIONS/0016-the-lab.md))
 or a placed artifact, and how images get into it.

 ## Incidental, and already fixed