From 682bdb724c24d4df3b7f7e2cbca161986b8ed019 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 15:32:53 +0100 Subject: [PATCH] Design 47 H: H-A-144, a module with no registration held is unlisted --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md index 08251737..31f829b4 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md @@ -691,3 +691,9 @@ Where two preparers disagreed, the chosen one is named. the composition's reason, never silently dropped. The assignment of a module the catalog no longer holds (the retired checker on the control-node) is removed by the assigner's own tool, written in the hand-act log, not by hand in its state. P9 (one rule per interaction), P3. +- **H-A-144 (a module with no registration held, in a composition across branches, 15:33)** Met in the review of + H-A-143's build: once registrations are held, a module no registration names has no watched branches, so it is + "a module no watched branch lists": said as such in the composition's reason, never composed from the branches the + client happens to follow. Only before the first registrations are held do the gate's source's branches stand in, in + the order the source gives them (ยง532). An unlisted module is said on every path of the judgement, whether the + machine composes, fails or could not run. P3.