From 37fdc292f7e208ed15271756e2ce6db0124ed08a Mon Sep 17 00:00:00 2001 From: jochen Date: Tue, 17 Nov 2026 00:17:38 +0100 Subject: [PATCH] After G: retire held and kept for a module left on its build; a composition that judged nothing is no pass --- 03-DESIGN/01-to-be/47-milestones/G-23-after-delivery.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-23-after-delivery.md b/03-DESIGN/01-to-be/47-milestones/G-23-after-delivery.md index 01728081..9bb29e6c 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-23-after-delivery.md +++ b/03-DESIGN/01-to-be/47-milestones/G-23-after-delivery.md @@ -144,3 +144,9 @@ deals with it, which is how the list is kept true. `build` of the seat `mesh-builds`: correct them. - A pipeline the runner set aside before A-446 with steps already written (`main.940.mesh-delivery-sdk`) is started again by neither of the runner's start paths. +- The node-engine's journal and the have's phases say a module is "held" and that the node "keeps running what it + runs" for one thing: a module left on the build it runs, its new build not applied. The operator, 2026-11-17, wants + those words gone: retire "held" and "kept" in that sense from the node-engine's lines and the glossary, with one + glossary word in their place. +- A composition that passes on every machine as "not judged: the composer was handed no seat list" is reported as + passed: a composition step that judged nothing must fail or say so (principle 3).