Place the two new records in the reading order, and fix a link the merge moved

Both carried a topic outside the six the index knows, so neither had a place to be read in — 0067 had none at all. Both are 'the tiers', beside 0036 (bootstrap ends at a usable mesh) and 0007 (connectivity), which is what they extend. 0067 cited 0041 for tier 0's property; on this trunk 0041 is events, and the record it meant is 0005. A citation that resolves to the wrong record reads as corroboration, which is worse than a dead link. Claude-Session: https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF
2026-09-11 00:48:20 +02:00
parent 56d0dcc4ff
commit 423fde8534
4 changed files with 71 additions and 3 deletions
@@ -1,4 +1,5 @@
 ---
+topic: the tiers
 status: proposed
 date: 2026-09-10
 deciders: jochen
@@ -121,7 +122,8 @@ machine auditable. An installer connects to plenty. Same tier, same delivery, di

 - [ADR 0006 — the substrate and the control plane](0006-the-substrate-and-the-control-plane.md),
  which pinned images by digest and named what a first node fetches.
- [ADR 0041 — the host depends on nothing that must be installed first](0041-the-host-depends-on-nothing.md),
-  the tier 0 property this keeps true by not putting the installer inside the host.
+- [ADR 0005 — the node host](0005-the-node-host.md), which makes tier 0 the one thing installed by
+  hand and the only thing that changes a machine — the property this keeps true by shipping the
+  installer beside the host rather than inside it.
 - [`04-ISSUES/029`](../04-ISSUES/029-the-artifact-store-cannot-be-delivered-by-the-artifact-store/00-report.md),
  the same cycle one layer down, and the rule that a registry module is named and never built.