novox/hq
3
0
Fork 0
Code Issues Pull Requests 1 Releases Wiki Activity

Rewrite 0073: the registry does not move, and the argument fails

Browse Source 
Written an hour ago claiming a produced image must be published before anything
can fetch it, so the registry had to precede the control plane. The premise is
false: the machine that builds the image is the machine that runs it, and the
temporary control plane names a built image exactly as it names a carried one —
by the digest of its own configuration, which requires nothing to have served
it. Building changes where the bytes came from, not where they are.

Rewritten rather than superseded because nothing has been built on it and
nobody has read it: a record that contradicts itself is a draft, not a decision.
The argument is kept, because it was asked for and a negative answer is the
result.
This commit is contained in:
jschoubben
2026-09-13 03:22:05 +02:00
parent 9f5ac38662
commit aabaaf2bb4
2 changed files with 24 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files
02-DECISIONS/README.md
+1 -1
View File
@@ -105,7 +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)
- **0073** — [The installer carries a builder, and the registry stays where it is](0073-the-installer-carries-a-builder.md)
### What runs on them, and how it gets there