Design 47 H2: H-A-410 addendum, a nak'd ask is listed as waiting again

This commit is contained in:
2026-11-22 00:59:37 +01:00
parent 9ca54b463e
commit 4d8c853f46
@@ -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.<ask>` 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.