From 2ff96d1b7e52c75d7490d7871bfaf620d50f85c6 Mon Sep 17 00:00:00 2001 From: jochen Date: Tue, 17 Nov 2026 01:11:09 +0100 Subject: [PATCH] Answer A-461a: another node's module is laid from the assignment's placed build --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 4 ++++ 1 file changed, 4 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 23f46305..c449c3a7 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 @@ -1418,3 +1418,7 @@ the principle that settles it, cited as "design 47 G A-n". `publish-pause-max`, and after `publish-tries` tries it ends loudly (log, condition) and stays readable in the builder's tools; all three are settings with defaults (30 s, 30 min, 8). (From the develop of A-457: a work-queue stream would need a `bus` restating the builder's whole account, or a second process.) +- **A-461a** (A-461; principles 7 and 1) "The build its want names" for another node's module is read from what the + composer already holds for every node: the assignment's placed build of that module on that node (absent meaning + the newest delivered, as the assignment says). The composer watches no other node's wants. (From the develop of + A-461: the composer holds only its own node's wants.)