From 49f08c9e83ff71de90b2aead082fdb5660ef8e47 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 04:17:16 +0100 Subject: [PATCH] Design 47 H: H-A-112, the composer drops its verdict branch and Case.Verdicts Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 4 ++++ 1 file changed, 4 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 56bd0796..ef0c9734 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 @@ -478,3 +478,7 @@ Where two preparers disagreed, the chosen one is named. - **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. +- **H-A-112 (node-engine developer, 04:18)** The composer (mesh-compose) likewise drops the verdict branch of its parse + and its case verdict, and the request field `Case.Verdicts` goes: its one writer was the checker, which goes in H1 + (H-A-57); the assigner's composition step sets no verdicts (H-A-108: the validate step judges before the composition + step). P7. -- 2.54.0