mesh-delivery

Files

T

jschoubben 496989ccfb CT10: meshcatalogclient follows the registrations, a first view then each registration-changed

The assigner and the forge module's merge switch on their first registrations (design 47 G §353), so the
seat's client carries the typed follower on go/views: a first view asked of the verb registrations, a newer
version heard asked again until the picture holds it, an answer read before the change asked once more.

Builds: design 47 G §353, §245

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

2026-11-11 11:43:53 +01:00

candidate.go

The checker's event layouts are its own published package, the try group key and wording are the mesh-catalog client's; one limit for try (ADR 0634 sections 1 and 2, issue 1966)

2026-11-05 20:50:14 +01:00

catalog_test.go

No client names a holder: each reader keeps its own constant, held to its manifest (ADR 0625 section 4, issue 1966)

2026-11-05 18:37:28 +01:00

fingerprint_test.go

mesh-delivery-contracts: the artifact reference forms move to the registry seats' client and the fingerprint key part to a new client of mesh-catalog; mesh-delivery-sdk serves Delivery modules only (ruling 3, ADR 0634 §1, §2; issue 1966)

2026-11-05 14:44:23 +01:00

fingerprint.go

2026-11-05 14:44:23 +01:00