From edd6cc09a0fdee814a3b8842af9aa8627cdec036 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 21 Nov 2026 20:50:19 +0100 Subject: [PATCH] Design 47 H: H-A-320, a step's end and an ask's answer are journal lines; a work queue has a consumer; every build seat takes checks --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 10 ++++++++++ 1 file changed, 10 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 8bc40cf4..f71fe865 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 @@ -1922,3 +1922,13 @@ Where two preparers disagreed, the chosen one is named. opened to the local network only, each of which an allowance without a source would widen to anywhere. Owed, H2: the node-engine's render marks each derived rule with a comment naming its scope, so the holder reads scope, not shape. P-security, P-failure-loud. +- **H-A-320 (a step's end and an ask's answer are journal lines; a work queue has a consumer; every build seat takes + checks, 20:50)** Read while the 36-mover pipeline looked stalled and was not: the runner writes no journal line when a + step ends and the builder none when it answers a step ask (36 builds answered in seconds, invisible); the seat + mesh-builds' asks ride a work-queue stream no consumer takes, so every ask stays until its age limit (1,524 + messages); only the operator's desktop's Go build module takes the check asks, the home server's takes none (the + laptop's is paused by hand); the runner's unanswered bound did not end asks that waited thirteen minutes untaken. + Owed, H2: (1) one journal line per step end and per ask answered, naming the pipeline, mover and step; (2) the + mesh-builds asks consumed (acknowledged when answered) or the stream bounded by count; (3) every build seat + holder takes check asks or says why it does not (paused, unhealthy), read by a tool; (4) the unanswered bound + counts from the ask's placing on the stream. P-failure-loud, P-NATS-native, tools-are-how-a-module-is-spoken-to.