Answer A-429: a released build is done for rule 1

This commit is contained in:
2026-11-15 16:13:29 +01:00
parent cac334e749
commit 14c3e90332
@@ -1121,3 +1121,9 @@ the principle that settles it, cited as "design 47 G A-n".
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.)
- **A-429** (§379, A-421; live 2026-11-15 16:07: the assigner's rule 1 said a released build "is being built", since
it knew build ends only from a stream it read from its start on, kept by age, not one per subject as the builder's
manifest declares; principles 2 and 7) A build whose version is released (`version-released` heard for its
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.