From e7db0df313309734eb6506c8f5f0e25d1e350b33 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 21 Nov 2026 11:21:28 +0100 Subject: [PATCH] Design 47 H: H-A-240, a module declares every finding kind it raises, and a test holds the code to it --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 8 ++++++++ 1 file changed, 8 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 19532125..e31eb30c 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 @@ -1352,3 +1352,11 @@ Where two preparers disagreed, the chosen one is named. the request for its standing"; no timer waits on the router. The request read (the tool's argument) shows the router's standing of the ask beside the keeper's. P-NATS-native (no part waits on a timer for another), P4 (what is said is what was read). +- **H-A-240 (a module declares every finding kind it raises, and a test holds the code to it, 11:21)** Met live: the + indexer's findings writer owns four kinds while its code raises others (pin-missing, generated-types-out-of-step, + a merge not taken in, and packages-not-published of H-A-233), so the writer refused them once a minute for hours and no + finding of the indexer was written. Every kind a module raises is declared where its writer reads its owned kinds + (its manifest's finding kinds), and a unit test of the module lists the kinds its code raises against the declared + ones and fails on one missing; the writer's refusal stays loud (a journal line and the writer's own finding of kind + call-unanswered is not right for it: it says "finding kind X not declared" once, not once a minute). P4, P2 (the + manifest is the declaration the mesh reads).