Narrow A-428: only the pipeline runner's own want skips the passed-pipeline gate while no runner runs

This commit is contained in:
2026-11-15 16:04:05 +01:00
parent aad8f7c921
commit cac334e749
@@ -1114,9 +1114,10 @@ the principle that settles it, cited as "design 47 G A-n".
held, and the trunk's newest build of it would replace it; principles 2 and 4) A put may name the build a node
runs now, read from the node's running statement, and holds the want there; the builder's store is not asked for it.
- **A-428** (§29, A-328; read from the code 2026-11-15 16:05: a want follows a passed pipeline, and no pipeline can
pass while no holder of the seat `mesh-pipeline-runner` runs, so the runner itself, and every module whose
fingerprint moved, never gets a want; the gate returned before the want rules without a word; principles 3 and 7)
While no module holding `mesh-pipeline-runner` runs on any node, a want does not wait for a passed pipeline: the
assigner writes wants from the trunk's entries by its other rules, and says once that it does and why. As soon as a
runner runs, wants follow passed pipelines again, from the next pass. (Whether a want waits for a passed pipeline at
all is a gate for the generic gating research to make configured.)
pass while no holder of the seat `mesh-pipeline-runner` runs, so the runner itself never gets a want; the gate
returned before the want rules without a word; principles 3 and 7) While no module holding `mesh-pipeline-runner`
runs on any node, a want of a module whose manifest claims `mesh-pipeline-runner` does not wait for a passed
pipeline: the assigner writes it from the trunk's entry by its other rules, and says once that it does and why.
Every other module still waits for a passed pipeline, so nothing else moves before a runner runs; once one runs,
A-328 has the runner's own changes pass on it. (Whether a want waits for a passed pipeline at all is a gate for the
generic gating research to make configured.)