Answer A-133: the recovery module's manifest follows the validator

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 03:28:16 +01:00
parent 8d5fcb8236
commit 5b1d068de3
1 changed files with 4 additions and 0 deletions
@@ -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.