Files

T

jschoubben 9f01b9e79a CAT-D3: mirror answers at once and the holder says the copy's end on the seat's events

A large base could outlast a call's bound. The ask is kept in the state mirrors and the copy runs on that state's
watch, so a copy a restart cut is taken on again; published (or refused, with why) on container-image-registry's
events is the end the caller waits on, the place the seat's contract already gives mirror.

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

2026-11-04 13:19:46 +01:00

cmd

CAT-D3: mirror answers at once and the holder says the copy's end on the seat's events

2026-11-04 13:19:46 +01:00

internal/holder

CAT-D3: mirror answers at once and the holder says the copy's end on the seat's events

2026-11-04 13:19:46 +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

CAT-D3: mirror answers at once and the holder says the copy's end on the seat's events

2026-11-04 13:19:46 +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).