From 47583173db60b4edcd4ccd9598b9d90c331cb2c1 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 02:19:43 +0100 Subject: [PATCH] Answer A-143: the recovery module's waits are bound keys 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 a1550953..7189d5f8 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 @@ -542,3 +542,5 @@ names the principle that settles it, and is cited as "design 47 G A-n". - **A-142** (§496, §602; principles 1 and 7) A `step-ended` said while the watchman was down reaches it on its start through its durable consumer of EVENTS, and ends the stuck ask then; nothing re-reads the steps and no expiry is added. +- **A-143** (A-77, A-138; principle 1) The recovery module's dump wait and snapshot-restored wait are bound keys in + its state `bounds` as well, their expiry heard on its watch; no timer stays in the process.