From 1dbc2844dcc5a49b54be1f0c918eb42ea090d9b1 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 22 Nov 2026 00:28:47 +0100 Subject: [PATCH] Design 47 H2: H-A-394 addendum, class stays out of the baseline --- 03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md index b30f0193..2f1349af 100644 --- a/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md @@ -213,3 +213,7 @@ The lead's one-line answers to the questions H2's develop and review raise (impl as long as its holder says progress within the bound, and a holder silent for the whole bound ends the step could-not-run naming the silence (P-failure-loud: a holder that works and says nothing is the fault, and the delivery SDK's step run says progress at each phase). H-A-238 (3)'s unbounded asks end. ADR 0668 §3. +- **H-A-394 (addendum, 01:14)** `class` does not join the baseline manifest reads: the running engine does not read it + (the baseline states what the running engine reads, ADR 0614 §4; state.max-mib joined because it does). The + node-engine's manifest at `class: core` and `declaration-reads: 2` is held for a yes once at this delivery, one hold + for both words, said to the operator with H-A-383's.