Answer A-98: a stop act that removes nothing, for a revert

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 23:32:21 +01:00
parent 720cff7271
commit fa8c046682
1 changed files with 3 additions and 0 deletions
@@ -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.