a75592502483d7aaca9cf67661e363052d298af7
A take-in.taken with entries starts one pipeline keyed <branch>.<source> by compare-and-set, its movers the entries; each mover's steps are placed from its own registration and entry, each step and ask id naming its mover; a step end is matched to its mover's commit and fingerprint; the pipeline passes when every mover's required steps passed, a required "nothing to run" counting as passed. The movers get tiers from the delivery edges (kinds 2, 4, 5, 6; a cycle one tier, said). pipeline-started and pipeline-ended are said on <branch>.<source>, the end once with per mover its fingerprint, version, steps and tier, in tier order; waits on <branch>.<source>; step events on <module>.<branch>.<commit>; no group-ended. Approval is one step per mover. A run on request is one pipeline keyed <branch>.run.<id>, its source the branch's newest, members of one branch only. A running pipeline is superseded no more. A composition step names the runner as its asker. The seat's verb place is served, refusing every pipeline until the queue (R11, R14). The seat list part takes no callers (H-A-66). Unit tests 77 to 80, integration 3. Builds: design 47 H §746, §747 (run, start, a publish's key), §748 (a running pipeline runs to its end), §764 (group-ended, the key per module); lead answers H-A-3, H-A-35, H-A-51, H-A-52, H-A-53, H-A-66, H-A-70, H-A-72, H-A-83 (1), H-A-85, H-A-88 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%