From 61b2a273f2bc5b60bf7b483205b7cfcc1d23ba90 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 02:13:05 +0100 Subject: [PATCH] Answer A-141: the recovery module acts on its own stop Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md | 3 +++ 1 file changed, 3 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 1a0f312a..d444cc21 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 @@ -536,3 +536,6 @@ names the principle that settles it, and is cited as "design 47 G A-n". - **A-140** (§681; principles 3 and 7) After its cancel is asked at the bound, the recovery module waits one more bound of `snapshot-restore-wait-minutes` for that act's snapshot-restored; none heard is "answers neither". A keeper that answers `busy` ends the act failed before any aside, naming the keeper's running act. +- **A-141** (§562; principles 1 and 7) The recovery module learns of a move from its own stop: from the stop signal + on it answers every new call with an error naming the stop, cancels the running act so its own failure path runs, + and ends every accepted act not ended `stopped` with its ending event; a restart is the same.