From 1ff3066bab610b3d8b64a540eaa746fc5541205f Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 00:21:42 +0100 Subject: [PATCH] Answer A-113: a failed restore restarts the newer build; no move without its restore point Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md | 4 ++++ 1 file changed, 4 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 90359c59..f2ffd713 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 @@ -451,3 +451,7 @@ names the principle that settles it, and is cited as "design 47 G A-n". - **A-112** (§633, A-71; principle 7, one way per kind of part) A process reads its settings as the builder does (A-71): a file its manifest declares, its content `${config:}`, read at its start; so the node-engine reads `recovery-wait-minutes` from such a file, default 90 when it is missing. A bundle keeps `stdio.Config`. +- **A-113** (§297, §560, §541; principle 3, failure is loud and leaves nothing broken) A revert whose restore fails + after `Env.Stop` starts the newer build again and holds the move, saying why; a module is never left stopped. A form + change whose entries are not yet answered waits for them, never moves without its restore point. The hold says + `wait-held` (§541) as every wait does.