From 60b653cbcce860e44cd67f16ac67e09841a3f203 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 22 Nov 2026 03:24:50 +0100 Subject: [PATCH] Design 47 H2: H-A-462, the builder's health judgement in the shared package --- 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 2b795a7f..751cb16f 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 @@ -756,3 +756,8 @@ The lead's one-line answers to the questions H2's develop and review raise (impl the embedded bus. (2) The fixed bounds the review names become settings with those defaults: the indexer's take-in-waiting-line (1m) and take-in-waiting-bound (5m), the builder's slow-event (100ms) and events-behind-bound (5m); P11. (3) The indexer's `heard` is capped at 32 MiB (live fill 4.65 MiB, H-A-437). P3, P11, ADR 0619 §1. +- **H-A-462 (the builder's health judgement lives in the module's shared package, 05:05)** §794, B5, H-A-435. The + judgement (a backlog held six minutes names the builder unhealthy) moves from the tools program's main into the + module's internal/build (or internal/versions, where the backlog it reads lives) as one exported function the tools + program calls, so the builder's whole test proves it as a step; a judgement two programs of one module need is the + module's shared code, not a main's (P3). P3.