From 7dd6563ab5eae50b04c9d24773c6bc088e63d4e9 Mon Sep 17 00:00:00 2001 From: jochen Date: Mon, 16 Nov 2026 14:53:14 +0100 Subject: [PATCH] Answer A-451: a machine whose node-engine is not heard running composes with the revision's node-engine entry --- 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 e3dc19f0..1b77bb65 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 @@ -1304,3 +1304,9 @@ the principle that settles it, cited as "design 47 G A-n". checker's, until the checker is removed at G's delivery, G-6 ยง321) keeps the inline input and its 900 KiB bound; an ask with a token gets the input in chunks only, with no bound. The assigner reads an inline input only from an engine that answers no `chunks` (one before A-237b); both forms go with the checker. +- **A-451** (completes A-226, A-243 and A-252; principles 2 and 3) Where a machine's node-engine is not heard running + (no `running` of the module holding the seat `node-engine` on that machine, or one with no fingerprint), the + composition step builds that machine's composer from the revision's node-engine entry, the build the catalog says + 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`.) -- 2.54.0