From 5b1d068de39d3bb16220692362a4c5e880fa94ba Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 01:46:39 +0100 Subject: [PATCH] Answer A-133: the recovery module's manifest follows the validator Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md index bf1cf8d3..f5b6fc8e 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md @@ -512,3 +512,7 @@ names the principle that settles it, and is cited as "design 47 G A-n". `assignments` keeps its own answer. - **A-132** (A-123, §556; principle 1) The recovery module learns the fingerprint a node runs for a module from the node-engine seat's `running` event, kept last per subject and read as §556 (a `consumes` of its manifest); no call. +- **A-133** (§657, §567, §554; principles 3 and 7) The recovery module's manifest follows the validator: (a) its health + check is its tool beside the process check the other modules declare; (b) the `digests` state's cap is given in the + template's own form at 4 MiB, never as a second option beside it; (c) the template states `digests` and `findings` + are the module's own by its `requires` and are not listed again in the process's `bus`, which keeps its own account.