From 8d5fcb823633efe7e2ac01a1bd29452a82794d54 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 01:32:15 +0100 Subject: [PATCH] Answer A-132: the running fingerprint from the node-engine's running event Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md | 2 ++ 1 file changed, 2 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 63f0649c..bf1cf8d3 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 @@ -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 (`.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.