From 706e76b566a1c391af57407f846c7f99e98d20d8 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 22:46:19 +0100 Subject: [PATCH] Answer A-407: a running build with no entry is described for resolving by the entry of the build its want says is being built --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++++ 1 file changed, 5 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 66d1193e..5272694d 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 @@ -963,3 +963,8 @@ the principle that settles it, cited as "design 47 G A-n". 2026-11-13, and its candidate carried no parts; the operator, as for A-405; principles 5 and 7) The pipeline's manifest is made to pass the judge, as any module's; its first build is asked of the builder once by hand, the way a run on request asks it, since only a pipeline asks builds and none runs yet. +- **A-407** (A-405; principles 7 and 2: the node keeps no manifest of a build that has no entry, and the running event + carries only a digest) A running module whose wanted build has no entry is described from the catalog entry of the build + its want says is being built (the newest of its first watched branch), read through the seat `mesh-catalog`'s `entry` as + any entry: what it provides, claims and requires there stands for the running build, for resolving the node alone. A + want that names no newer build leaves the module as today (a name alone), said once.