Files
mesh-catalog/modules/distribution
jschoubben d3d9ff5183 M1: the build modules and the registry say their class and name every store's cap; detected-steps is pruned
Each of the four is core. Every state that named no cap names one, from its
live fill read 2026-11-22 01:4x CET (mesh-broker show, nats_streams on novox):
mesh-build-go steps 16.0 MiB (16,783,695 bytes) -> 128 MiB; mesh-build-node
steps 2.35 MiB (2,463,833 bytes) -> 16 MiB; every other state under 2 MiB ->
8 MiB (largest: distribution holds 1,844,287 bytes, mesh-build-go
detected-steps 868,554, distribution transfers 846,359, findings 668,161, idle
401,736, mesh-build-go pauses 254,366). The Go build module's finding-events is
8 MiB for 7 days. The objects stores already name their caps; none keeps a log.
The Go and Node build modules prune their state detected-steps (each key an
artifact's steps as detected, detected again when gone) at their own writes,
past prune-mark 70 % down to prune-target 50 %, and serve
<module>_state_prune_now and <module>_state_keep; no other state of the four is
prunable (each is truth: running steps, pauses, keys, toolchains, findings,
holds, transfers, windows, mirrors, taken asks).

Builds: design 47 H2 §812, §820; H-A-411 (1), (2), (3), H-A-437
2026-11-22 01:39:49 +01:00
..

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).