From d16d23e2a27afd27e4c22a52ed27955529260f12 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 03:08:06 +0100 Subject: [PATCH] Answer A-147: a recovery act during a move is refused, naming both fingerprints 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 fdb9204a..f3ebac4a 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 @@ -553,3 +553,5 @@ names the principle that settles it, and is cited as "design 47 G A-n". rules and A-116/A-128's seat reads are G's own validator rules, judged by the change's validator, and stay in G. - **A-146** (A-145, §529, A-30; principle 5) The second reader release also carries §529/A-30's exception for a foundation part's kept old sections, and only that, since the trunk validator must accept the new indexer manifest. +- **A-147** (A-123, A-132, A-137; principle 3) While a module runs at two fingerprints (a move under way), a recovery + act on its kept data is refused, naming both; the caller asks again once the move has ended.