mesh-delivery-builder.builder_versions answered no numbered version for any name asked (mesh-sdk go and ts, mesh-host, node-tools, mesh-delivery-builder, mesh-conditions), so every module takes 0.1, the floor §368 gives a module with none published: all 144 manifests (141 from "1", distribution, mesh-provisioner and mesh-provisioner-client from "2", which carries nothing over, §583). Builds: design 47 G §368, §411, §583, A-46 Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
distribution
The distribution module of the mesh catalogue: runs the container image registry; holds the seats container-image-registry
and oci-artifact-registry, and mesh-artifact-store until its window closes. It provides no provision: the store's address
is its listen registry, open to the mesh, which every node-engine finds through the seat's holder (novox/hq ADR 0632). Its
seats' list answers what the store holds, read from the store's own files through its container mesh-registry.
Files it does not know
Each directory or archive this module declares says how it treats a file it did not write (ADR 0422, ADR 0416).
/var/lib/mesh/registry: everything in it is the program's; the mesh moves nothing out (ADR 0422 §2)./var/lib/mesh-registry: everything in it is the program's; the mesh moves nothing out (ADR 0422 §2).