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 765a437d..60c9470a 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 @@ -1892,3 +1892,13 @@ the principle that settles it, cited as "design 47 G A-n". the agreed language version; a node sits out only on a real difference. (From the develop of A-477: the agreement event has no recipe field; adding one would change the contract, the builder and the runner for what the guard settles in one place.) +- **A-478** (the operator, 2026-11-17 ~21:45 CET, step 5 of the delivery walkthrough: "all nodes that have that module + assigned installs the latest version"; then "yes, do the fix"; narrows §376, §711 and A-189 for the assigner's want; + principles 7 and 2) A machine's want of a module names the newest released version of that module whose pipeline + passed, on every machine the module is placed on; that is the assigner's whole want rule. (a) The acting-part hold + ends: a want is never held because an acting part of a step does not run a given build on its machine. (b) The + delivery-dependency hold ends: a want is never held for a dependency's `version-delivered` (§376, A-189); the order + between modules moves into the pipeline later, as the walkthrough's step 4 says. (c) What a module that keeps data + needs stays as it is: the backup before the apply (§296) and the operator's yes on a failed backup or a held revert + (§710) are the node-engine's and the asker's, not a hold of the want. (Live, 2026-11-17 20:57 and 21:15: feh 0.1.8, + released 21:39 with its pipeline passed, was held on shanks and g14 by both holds, though nothing depends on feh.)