From bb04c5b089b43185398a340742fa78f0c3b723b2 Mon Sep 17 00:00:00 2001 From: jochen Date: Tue, 17 Nov 2026 23:42:18 +0100 Subject: [PATCH] Answer A-482: a running build is one the node's own record says runs --- 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 3f78e8bd..ba8b86f9 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 @@ -1935,3 +1935,10 @@ the principle that settles it, cited as "design 47 G A-n". resolve that holds each built artifact's texts), and read by the node-engine's parts check; one change across those repositories. (From the develop of A-481: the composition's layout is the seat's strict wire type, and no field of it fits.) +- **A-482** (A-480a; principles 2 and 3) "A held module's running build" is one this node's own record says runs: the + module is heard running here, is in what the agent runs, or its have names a build in the phase running or held (a + held module keeps running what it runs). A module wanted here with none of these is not running, whatever it was + heard of: its trunk build is not laid for it, and what only it would provide stays "nothing provides". (From the + review of the heard-running change: it counted every wanted module not heard stopped, so a module placed here that + never ran provided what it does not run. Live, g14: xorg runs from a build placed by hand, said by no running event, + and its have says running at that build.)