From fa8c046682f8d209bd4b7d4773c5920123728ff7 Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 11 Nov 2026 23:32:21 +0100 Subject: [PATCH] Answer A-98: a stop act that removes nothing, for a revert 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 316acd99..397e93f5 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 @@ -387,3 +387,6 @@ names the principle that settles it, and is cited as "design 47 G A-n". unit and integration on the build seats. With the candidate coming that way, the builder's watch of the gate's `source` for candidate base merges goes. A kind-3 dependency's `part` is the entry's kind-3 edge, as built in 2dc51626. +- **A-98** (ยง297; principles 3 and 7) The node agent gains one act, `Env.Stop`: it stops a module's units and containers + and removes nothing, so a revert's data survives; the revert stops the newer build with it, asks `restore-kept`, and + then `Apply` starts the reverted build. `Remove` keeps its meaning.