Answer A-123 to A-125: aside's names, a list, the restore in mesh-sdk

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 03:28:15 +01:00
parent aef9bf8453
commit a1faef315f
1 changed files with 6 additions and 0 deletions
@@ -488,3 +488,9 @@ names the principle that settles it, and is cited as "design 47 G A-n".
  by `_`. The recovery module calls those mesh-sdk names; it writes no name of its own.
 - **A-122** (A-116, §324; principle 7) The node-build-image seat's `build` act takes the bound the other build seats
  take, `60m`.
+- **A-123** (§682, §554; principle 2) `aside` takes its bus names from the catalog entry of the fingerprint the
+  node-engine's placement runs for the module: what is set aside is the data that runs.
+- **A-124** (§682; principle 7) The seat's aside names every bus object of the kept data: `Aside.name` becomes the list
+  `names` in the mesh-recovery contract, regenerated; no names joined into one string.
+- **A-125** (§655) The restore of one stream moves into mesh-sdk's bussnap beside its snapshot, and the bus module
+  imports it from there; the recovery module's builder moves it, in the same work.