From 307168a7780e9e6ee5cb75eef5a45789eba28ddd Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 04:15:42 +0100 Subject: [PATCH] Design 47 H: H-A-111, the node-engine reads a taken module without a verdict Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 3 +++ 1 file changed, 3 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 8943853c..56bd0796 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 @@ -475,3 +475,6 @@ Where two preparers disagreed, the chosen one is named. - **H-A-110 (node-engine developer, 04:13)** Within one link, the node-engine asks its unanswered entries again when it hears the seat mesh-catalog's `catalog-revision` (one per take-in): the composer consumes that event for this alone and calls the entries client's `AskAgain`; and once more at each link's start. No timer. P1. +- **H-A-111 (node-engine developer, 04:15)** With no verdict state (H-A-79, ADR 0682 ยง4), the node-engine's reading of + a taken module (frombus `taken`) drops the verdict branch and decodes the manifest alone: a module in a catalog + revision is accepted by being there; the validate step judged it before any want. P7.