From e1af8b445c52f56289285fd69100cf4c94b90a46 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 22 Nov 2026 01:33:34 +0100 Subject: [PATCH] Design 47 H2: H-A-435 addendum, builder_health in the runner's form --- 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 34bd1899..5b832db6 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 @@ -559,3 +559,8 @@ The lead's one-line answers to the questions H2's develop and review raise (impl indexer's watch of `heard` (the bus's expiry marker); the re-pin revision is written at that expiry or at the first pipeline-started or step-ended of the pipeline, whichever comes first. A context deadline is a timer the test does not see and breaks the same rule. P-NATS-native. +- **H-A-435 (addendum, 01:41)** A tools bundle cannot read a consumer's info, so builder_health takes the runner's form + whole: the builder's events hub is wrapped in a process.ConsumerLedger that writes each consumer's facts at every + delivery and every apply into a new builder state `consumers` (8 MiB), and the tool reads that state; "read when the + health is asked" reads so (the bus is read at each event, no timer). The ledger's oldest-unacknowledged covers + delivered messages only, as the runner's does. P3.