The installer carries a builder and builds the control plane it raises

It carried the thing it was going to run; it now carries the thing that makes
it. One artifact either way — but a mesh raised this way holds a control plane
it built from a repository and a commit it can name, and can therefore build
again. A mesh handed a finished image could not, and had no way to find that
out until somebody needed it to.

A build step sits between load and bundle, because the bundle must name an
image and that image no longer arrives finished. Everything after it is
unchanged: a locally built image is named by the digest of its own
configuration, which is exactly what the carried one was named by.

Refused in preflight when nothing says what to build, so a run that cannot
finish says so before it has changed anything.

internal/bootstrap/load.go

@@ -30,7 +30,7 @@ type Loaded struct {
 	Predicted bool
 }
 
-// Load puts the carried control-plane image into this machine's container runtime, and reports
+// Load puts the carried builder image into this machine's container runtime, and reports
 // what the runtime decided to call it.
 //
 // **The digest of a configuration is not portable across runtimes, and that is why the id is read