jschoubben
4f7206702f
Each machine placing the module on the step's branch is asked compose-candidate for its input; one composer.Request per machine (depth compose, the one machine, one case change) carries it with the manifests, verdicts and seat definitions of the step's catalog revision read through mesh-catalog's revision; the request is kept under its run ask (refused at the inputs state's 64 MiB cap, naming the store); one run ask per machine on node-build-go's check queue under the assigner's name, naming no head, its program the node-engine build's catalog entry (the build each machine runs as its running says, read through entry, or the revision's where it differs from the trunk's) with the composer's package. The run's end is heard on the build seat's step-ended and its verdict read through buildstep.StepEnded.ReadOutput; a machine the watchman said away passes with a warning. The step is served from main. Builds: design 47 G §354, §22, §63, §64, §389, A-226, A-238, A-240, A-243, A-252, A-254, A-261 Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
mesh-delivery
Novox Mesh — delivery: the parts that build, check and deliver a change by watching and writing keys on the bus (ADR 0429).
Made by the mesh from the gitea module's config value repositories (novox/hq ADR 0428). Main takes no push: a change reaches it by a pull request whose mesh/repo-check (this repository's merge-check.sh) and mesh/merge-gate passed.