mesh-delivery

Files

T

jschoubben 38a2492394 RN3 (publish half): a pipeline starts by compare-and-set on its key, and a package-published starts one per dependent behind

A start writes the pipeline's key (watched branch, source revision, module) only when it is absent and says
pipeline-started; a second start of the same revision and module writes nothing. A package-published asks the
catalog's outdated for that package on that branch, a kept call, and starts a pipeline for each dependent behind
by kind 1, keyed by the publication's branch and source revision. The start on take-in.taken, and a gathered
group's one pipeline per branch, wait for take-in.taken's body (design 47 G §476, in review).

Builds: design 47 G §54, §103, §334, §53, §75

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

2026-11-11 12:34:26 +01:00

mesh-delivery-assigner

AS19 (the seat list): the assigner wires its seat list reader through mesh-sdk's seatlist.Part

2026-11-11 12:07:39 +01:00

mesh-delivery-builder

BL2: the build reserves its version at its start; reserved state, tools, verb and findings

2026-11-11 11:44:47 +01:00

mesh-delivery-checker

WM11, CK12, EN1 (manifest half): finding stream, the keeper's ask and MAJOR.MINOR version in the manifests of the watchman, the checker and enrolment

2026-11-11 12:14:24 +01:00

mesh-delivery-forge-bridge

FB3, FB4, FB5: the bridge performs what the gate owes through the seat git and says each outcome, reads groups from the seat, and its owed tools