Answer A-132: the running fingerprint from the node-engine's running event

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 03:28:15 +01:00
parent c764f46577
commit 8d5fcb8236
1 changed files with 2 additions and 0 deletions
@@ -510,3 +510,5 @@ names the principle that settles it, and is cited as "design 47 G A-n".
  the view's own first-view tool on its holder (`<holder>.assignments`), the holder found at runtime by A-126's helper
  and the builder among the view's callers; the seat-form `consumes` of the view covers it, and the seat verb
  `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.