Archived
This is how a mesh is raised: the installer carries this program and runs it once, before anything exists, to produce the control plane from the same repository and path every later rebuild will use. What raises the mesh is then the same thing that maintains it, rather than a second mechanism exercised once per new mesh — which is how often enough to rot. With nowhere to publish, an image stays in the machine's own runtime and is named by the digest of its own configuration: the same identity the installer has always used for the image it carried.