Files

T

jschoubben d03ffa8038 G findings: mesh-config's and mesh-vault's owner views are followed by the reader (Follow), not adopted: they hear the owner's own views event

Adopt subscribes a seat's event with further parts (<seat>.<event>.>), which never matches the plain views event of an owner; the reader's Follow hears it and asks again on a gap. Also the distribution whole test counts its own two events by subject, as the writer's are said beside them.

Builds: design 47 G A-28, A-26, A-30

2026-11-11 22:22:24 +01:00

cmd

G findings: mesh-config's and mesh-vault's owner views are followed by the reader (Follow), not adopted: they hear the owner's own views event

2026-11-11 22:22:24 +01:00

internal/holder

G findings: distribution-tools and package-registry make the held writer at once and start it after Serve, as it seeds at Start

2026-11-11 22:19:22 +01:00

go.mod

G findings: the modules with findings of their own write them through mesh-sdk's writer

2026-11-11 21:58:08 +01:00

go.sum

Require every mesh package of the group at the floor version (ADR 0573 sections 2 and 4, issue 1966)

2026-11-05 16:56:39 +00:00

module.json

G findings: claude-code, mesh-provisioner, distribution, mesh-config and gitea declare the writer's three events

2026-11-11 22:10:19 +01:00

README.md

distribution: provide and serve no artifact-store, and answer the seats' list from the store's own files (ADR 0632 §1, §3, §4; issue 1966)

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

README.md

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