From 4d8c853f469548b436167fa775424bc9b636ffca Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 22 Nov 2026 00:59:37 +0100 Subject: [PATCH] Design 47 H2: H-A-410 addendum, a nak'd ask is listed as waiting again --- 03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md | 5 +++++ 1 file changed, 5 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 807480e6..80eacfbe 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 @@ -355,3 +355,8 @@ The lead's one-line answers to the questions H2's develop and review raise (impl does), never as an object kept for a later read; keepOver's `output.` object goes with the chunks verb, and the two readers move to the chunked form (the builder's and the assigner's developers, one row each). One way for a big answer, P3; §791's "read where it is kept" is the run output's rule. P3, ADR 0525 §6. +- **H-A-410 (addendum, 01:01)** mesh-tools T4 (917195a3) counts as waiting a message lying after the worker's delivered + sequence; an ask handed out and handed back (a nak) is listed neither there nor in `taken` unless the holder keeps it. + Settled: a nak'd ask is waiting again (the stream redelivers it), so the runtime lists a message whose delivery count + is above zero and that is not held by a worker as waiting too, with `again: true`; a one-row change in T4, by the + mesh-tools developer, before the review. P-failure-loud.