8da18c37c5596d66c7c46fd22b9198ec3f83801d
A package-published is heard in the running pipeline of the source revision that published it, where its dependents wait (R7); every module the catalog half holds a kind-1 edge from the package into that this pipeline does not move (a publish again of an older build, a dependent it does not move) is a mover of one pipeline keyed <branch>.<source>.published.<package>.<version>, at the publishing source's catalog revision and call. The dependents come from the edges the runner holds: the runner asks outdated no more (its invoke leaves the manifest). A publish heard before its branch's half is held is heard again once it is; the durable consumer delivers one heard after a stop, the key written once. Unit tests 83 to 84. Builds: design 47 H §747; lead answers H-A-19, H-A-52 Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
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.
Description
Novox Mesh — delivery: the parts that build, check and deliver a change by watching and writing keys on the bus (ADR 0429).
36 MiB
Languages
Go
99.3%
JavaScript
0.7%