Installing ends with a builder, and the record says so #39

2026-09-14T10:34:37Z

jschoubben commented

2026-09-14 10:34:37 +00:00

Two statements in the design were still true this morning and are not now.

"How the builder arrives is unsettled, and it is the one gap that stops everything after this paragraph from being possible on a machine nobody is sitting at" — it is settled and built. The installer carries a builder, because it is what builds the control plane; its last step publishes that image into the mesh's own registry, installs it as an ordinary module, and issues its broker account before the machine is sent anything.

"The builder's own module is not installed by genesis, so the mesh cannot yet be asked to build anything else" — it is, and it can. Verified on a bare machine: the install ended with a builder running, and that mesh then built the shared base images into its own registry and a module on top of them, with nobody helping it.

What remains is narrower and is kept as its own statement rather than folded away: nothing yet asks a raised mesh for the rest of the catalogue, and no bed asserts that it could — that last check is done by hand, which is now the weakest line in the table and says so.

Two statements in the design were still true this morning and are not now. "How the builder arrives is unsettled, and it is the one gap that stops everything after this paragraph from being possible on a machine nobody is sitting at" — it is settled and built. The installer carries a builder, because it is what builds the control plane; its last step publishes that image into the mesh's own registry, installs it as an ordinary module, and issues its broker account before the machine is sent anything. "The builder's own module is not installed by genesis, so the mesh cannot yet be asked to build anything else" — it is, and it can. Verified on a bare machine: the install ended with a builder running, and that mesh then built the shared base images into its own registry and a module on top of them, with nobody helping it. What remains is narrower and is kept as its own statement rather than folded away: nothing yet *asks* a raised mesh for the rest of the catalogue, and no bed asserts that it could — that last check is done by hand, which is now the weakest line in the table and says so.

jschoubben added 1 commit 2026-09-14 10:34:37 +00:00

Installing ends with a builder, and the record says so 256884e671

The design said how the builder arrives was unsettled and that nothing
installed it — the one gap stopping a fresh mesh from producing anything. Both
are now false. What is still true is narrower and worth keeping separate:
nothing asks a raised mesh for the rest of the catalogue, and no bed asserts
that it could.

jschoubben merged commit e773bf4c34 into main

2026-09-14 10:34:43 +00:00

mesh-admin referenced this issue from a commit

2026-09-28 01:59:42 +00:00

Design 28: 5.5 done, the mesh has one bus; issue 131 resolved

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#39