Answer A-426a: every rule waiting on a serving part counts any healthy running build that serves it
This commit is contained in:
@@ -1127,3 +1127,10 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
fingerprint's parts) is done for rule 1, as §379 takes its parts from that event; `build.ended` counts for a build
|
||||
not released (another watched branch, a kept build). The assigner reads the builder's build ends whole at its start.
|
||||
That the bus keeps that stream by age, not one per subject as declared, is a fault of the grants part, noted.
|
||||
- **A-426a** (A-426, ADR 0614 §2; live 2026-11-15 16:15: rule 8 holds the pipeline runner's want, "the verb
|
||||
seat:mesh-hand-acts.hand-act mesh-delivery-pipeline invokes is served by no running build", while mesh-hand-acts runs
|
||||
on the control-node and serves that verb with a build from before G; principles 2, 3 and 7) A-426 holds for every
|
||||
rule that waits on another part, the acting waits and rule 8 (an invoked verb served) alike: a part counts as
|
||||
serving when a node runs a build of it that serves the seat or verb and is healthy, from its running statement and
|
||||
the tool runner's announcement, whatever its version and whether or not the catalog lists that build. The rule says
|
||||
which build it counted.
|
||||
|
||||
Reference in New Issue
Block a user