From 7225f752c62653280e3a9c02042496240c56b9ec Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 18 Nov 2026 00:22:36 +0100 Subject: [PATCH] Answer A-483: a running build with no entry keeps what its running composition keeps --- 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 ba8b86f9..90eae421 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 @@ -1942,3 +1942,10 @@ the principle that settles it, cited as "design 47 G A-n". 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.) +- **A-483** (A-113, §296, A-480; principles 2, 7 and 3) Where the running build of a module has no entry, what it keeps + on the bus is read from the composition it runs on this node, as A-480 reads what it provides. When neither that + composition nor the wanted build's manifest keeps data on the bus, no form can change: the move needs no restore + point and goes on. When either keeps data and the running build's entry cannot be read, the module still waits for the + entry, as A-113 says. (Live, 2026-11-18 00:16, g14: feh 0.1.8 passed its parts check and was then held "whether feh's + kept data changes form between f4cf42de… and 2130f05a… is not known … the entry of src2:f4cf42de… is not-found"; its + running build is from before G and has no entry.)