Files

T

jschoubben cb3db6c902 CAT-REG: distribution's references name the seat as their registry part

The reach came from MESH_REGISTRY_REACH, which nothing sets, so every published event
answered /<name>@<digest>. The store answers the path; the holder puts the seat's name
before it, as catalogue.InRegistrySeat reads it back (ADR 0605 §9; lead's ruling on A3n).

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

2026-11-04 14:49:48 +01:00

cmd

CAT-REG: distribution's references name the seat as their registry part

2026-11-04 14:49:48 +01:00

internal/holder

CAT-REG: distribution's references name the seat as their registry part

2026-11-04 14:49:48 +01:00

go.mod

CAT-D2: distribution's verbs and events speak the two seats' contracts from mesh-contracts

2026-11-04 13:07:14 +01:00

go.sum

CAT-D7: distribution's whole-module integration test against a real bus

2026-11-04 13:01:15 +01:00

module.json

A3k finding 2: distribution reads its caller list as mesh-config resolves it, not from an environment nothing renders

2026-11-04 13:54:17 +01:00

README.md

Say on every directory how it treats files it does not know, and check it (issue 1024, ADR 0422)

2026-10-17 16:23:03 +00:00

README.md

distribution

The distribution module of the mesh catalogue: runs the container image registry; claims the seat mesh-artifact-store.

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