From 14c3e90332f11b10d14af16ce17a70fdefe45681 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 15 Nov 2026 16:13:29 +0100 Subject: [PATCH] Answer A-429: a released build is done for rule 1 --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 4971e8fa..22940906 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -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.