jschoubben
e4ef67adcd
The delivery repository's contracts and SDK live under modules/ as mesh-delivery-contracts and mesh-delivery-sdk, their Go module paths renamed to match the folders (the TypeScript names already did), and every importer in mesh-delivery, mesh-catalog, mesh-host, mesh-tools and mesh-sdk follows in the same group: a design as it should be, one path per module, checked by the group's check building every importer. Builds: design 47 G §427, §88 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).