From 54f6d4bb5d7eefbdf31fa5209c56bb1ff2aea9c8 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 02:04:35 +0100 Subject: [PATCH] Answer A-140: the wait after a restore's cancel, a busy keeper 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 20fcab27..1a0f312a 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 @@ -533,3 +533,6 @@ names the principle that settles it, and is cited as "design 47 G A-n". - **A-139** (§681; principle 7; code shared between modules is in mesh-sdk) The chunks of a seat verb's answer are received with mesh-sdk's own form (`buscalls`), the one the bus module sends with; where mesh-sdk has no receive, it is added there, never built in the recovery module. +- **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.