From 10d6d75902293433e00d3b9265460989ef01b6b2 Mon Sep 17 00:00:00 2001 From: jochen Date: Tue, 17 Nov 2026 11:56:06 +0100 Subject: [PATCH] Answer A-470j: a module that can never be built is blamed, not a reason to judge no machine --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 7 +++++++ 1 file changed, 7 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 f9043c18..32e48974 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 @@ -1760,3 +1760,10 @@ the principle that settles it, cited as "design 47 G A-n". withdrawn: `Fill`'s `cap` is the cap setting's value, the one that refuses, and no field is added. The read verbs `test-runs` and `compositions` are answered by the runner's and the assigner's process, which hold the setting, as their drops are (A-469g); the tools call the verbs. +- **A-470j** (G-24 H3; §721, §722, ADR 0578 §3; principles 10 and 3) A module of the case whose build is awaited but can + never be made, because the revision gives it no fingerprint (its `none` names why: builders disagree, no build module), + does not leave its machine not judged: the composer judges the machine from the composition with that module held as + its node-engine holds it, and names the module in `blamed` with the revision's `none` words, so only its own pipelines + fail and every other step passes with a warning (§722). An awaited build that has a fingerprint keeps the machine not + judged, as today. (Live, 2026-11-17 11:40-11:46 CET: lidarr, radarr and gitea have no fingerprint at revision 449, + "builders disagree" on the Node toolchain, so every composition of ace and novox ended `could not run`.)