Settle how the builder arrives, and what it publishes into

The two questions the design record named as the one gap stopping a fresh mesh from producing anything. They cannot be answered apart: a builder with nowhere to publish has made a file on a disk. The registry's role did not change — the answer to 'must it precede the control plane' did, because the control plane's image is now produced rather than carried, and a produced image must be put somewhere before it can be fetched.
2026-09-13 03:20:07 +02:00
parent 3983188b8a
commit 9f5ac38662
2 changed files with 93 additions and 0 deletions
@@ -105,6 +105,7 @@ python3 00-META/checks/index.py            fail if stale
 - **0070** — [The catalogue owns the module graph, and genesis builds rather than carries](0070-the-catalogue-owns-the-module-graph.md)
 - **0071** — [Genesis clones from a mesh, and checks what it got](0071-where-genesis-gets-its-source.md)
 - **0072** — [Two graphs, and a build chain that orders itself](0072-two-graphs-and-the-build-chain.md)
+- **0073** — [The installer carries a builder, and the registry precedes the control plane](0073-the-installer-carries-a-builder.md)

 ### What runs on them, and how it gets there