From 04fb9e749972663c7673cba72e7f01fe18811a98 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 22 Nov 2026 01:31:39 +0100 Subject: [PATCH] Design 47 H2: H-A-435, the builder's health is a tool --- 03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md | 7 +++++++ 1 file changed, 7 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 8e3b0191..3c64a4e7 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 @@ -546,3 +546,10 @@ The lead's one-line answers to the questions H2's develop and review raise (impl - **H-A-373 (addendum, 01:36)** The delivery SDK's publishParts refuses an empty version on the Go package registry seat and for every publish of kind `bundle`, whatever the language (the Node build module's bundles carry the version too); an archive may still publish by digest where no version is reserved for it. No language argument. P3. +- **H-A-435 (the builder's health is a tool, as the runner's, 01:37)** ยง794, B5. The builder gains `builder_health`, the + form of the runner's runner_health: healthy when it answers, each of its durable consumers' oldest unacknowledged + message waits less than five minutes and no handler stands still; its manifest's health asks that tool (the health + kind the runner uses) in place of `kind: unit`. The oldest message is read when the health is asked, from the + consumer's info on the bus (the probe is the read; the builder keeps no timer and polls nothing); the mesh's health + probe raises the condition, so no finding of the builder's own. Every module declares how its health is checked + (ADR 0240); tools-are-how-a-module-is-spoken-to; P-NATS-native.