From e69d2693dee460e052e3f1d10086f9859e266668 Mon Sep 17 00:00:00 2001 From: jochen Date: Tue, 17 Nov 2026 01:17:57 +0100 Subject: [PATCH] Answer A-461b: an absent placed build is the trunk build from mesh-catalog's module verb --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 6 ++++++ 1 file changed, 6 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 21f3dfb2..bce9c9fd 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 @@ -1428,3 +1428,9 @@ the principle that settles it, cited as "design 47 G A-n". version), which is how it leaves a stale failure; the node-engine's want on ace still names an older build, and moves when this change's own pipeline passes (ยง29). Trying the failed install of that older build again would put an older node-engine on the machine, so no retry is added. (From the develop of A-460.) +- **A-461b** (A-461a; principles 7 and 9) Where the placement names no build ("the newest delivered"), the composer + takes that module's trunk build from the seat `mesh-catalog`'s verb `module`, as it already does for a module an + assignment adds (`addedModule`), and lays the module from that entry. A-461's fallback applies only to another + node's module, and only when its running build has no entry; and only a store with no known address (the holder + opens no listen, or two) holds the modules that fetch from it: every other fault of finding the store still refuses + the node, as before (principle 3). (From the review of A-461: novox's placement of `distribution` names no build.)