Answer A-113: a failed restore restarts the newer build; no move without its restore point

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 03:28:15 +01:00
parent 69771a4d8e
commit 1ff3066bab
1 changed files with 4 additions and 0 deletions
@@ -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:<key>}`, 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.