2a93cbcd9bef0ee187abd8872f957ff18b709a74
The runner started whole with pipelines-at-once 1 and pipelines-waiting-cap 1: a second take-in waits, saying wait-held, and is placed with wait-ended on the first's end; a newer waiting take-in takes its shared movers out of an older waiting one, which ends superseded; a start over the cap waits and raises queue-full, cleared on the count; a cancel places the next; a pipeline on its approval alone gives up its place and, answered while it still runs, is keyed running at once; a placing the bus refuses raises pipelines-stalled, cleared when the next start places the waiting from the runner's own state, which starts no pipeline of its own. The tools runner_rerun, runner_accept and runner_ask_again are shown to take the mover's module. Builds: design 47 H §748, §774; acceptance test 112 (the runner's half); lead answers H-A-14, H-A-36, H-A-52, H-A-53, H-A-96, H-A-101, H-A-106, H-A-107 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%