From 89b5ac656a7a9938964f184214c410754eb1f998 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 21 Nov 2026 11:28:14 +0100 Subject: [PATCH] Design 47 H: H-A-243, a seat that says no first word: the ask is put again when its holder starts; one long silent bound --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 13 +++++++++++++ 1 file changed, 13 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 50816e39..436bccba 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 @@ -1376,3 +1376,16 @@ Where two preparers disagreed, the chosen one is named. (2) Each writer keeps its kinds in code, and the module's unit test lists the kinds its code raises against each writer's list; no manifest field. (3) A kind a writer does not own is said once in the journal, never retried. In mesh-sdk (the views package) and the indexer's test. P4, P7, G ยง580. +- **H-A-243 (a seat that says no first word: the ask is put again when its holder starts; one long silent bound, 11:28)** + Amends H-A-241 for the seats whose holder says nothing before the step's end (mesh-builds, mesh-wants today) and + for the second id. (1) The root: a holder takes its asks on a plain subscription, so an ask put while it is down is + lost. Until the asks of these seats travel through a work queue the holder consumes (owed, named in the report: + the seat's asks as a work queue, the SDK's form), the runner puts every open ask of the seat that has no end again + when the seat's holder starts (the node-engine's running event for the holder's module, which the runner hears), + with a journal line; that is what main.76 needed. (2) For such a seat there is no re-ask at the first bound (it + would double a running build); one silent bound, the setting ask-silent-bound (default forty-five minutes), ends + the step could-not-run "its ask had no end" with the finding call-unanswered, so a lost ask is caught within + it and no build of ordinary length is cut; the two seats' ask-taken is owed. (3) A second id is derived in the + accepted form: the first id's time part plus six hex digits of sha256 of the first id and ".2"; the runner matches + an end under either by deriving it from the step's ask. P-NATS-native (an event, not a timer, is the first + recovery), P4, P7.