From e17cffa59e99c87e4d0fe29f4971e3aa745492fa Mon Sep 17 00:00:00 2001 From: jochen Date: Tue, 17 Nov 2026 00:14:20 +0100 Subject: [PATCH] Answer A-452: an unanswered requirement costs its consumer, not the machine --- 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 1b77bb65..a3fc2903 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 @@ -1310,3 +1310,10 @@ the principle that settles it, cited as "design 47 G A-n". the machine runs, and its log says so with the machine and the entry's fingerprint; the step does not stop on it. (Live, 2026-11-16: main.953's composition could not run, "novox: no build of mesh-host is heard running there": a node-engine running a build the catalog holds no entry for says no `running`.) +- **A-452** (extends A-405 and A-407 as ADR 0636 ยง3 does for claims; principles 10 and 3) A requirement nothing on the + node or in the rest of the mesh answers costs the modules that want it, not the machine: each such consumer stays on + the build it runs, its have saying why (the same "nothing provides" words, naming the provision), as a refused claim's + claimant does, and every other module of the node composes. The machine is refused only when what fails is the node's + own composition or no module could be composed at all. (Live, ace 2026-11-16 23:11: the node refused its whole + composition on ten unanswered requirements, eight of them of modules already staying on their builds with + `entry-missing` or no part digest, so the tool runner's released build 7df8e170 (`node-tools`) was never composed there.)