Answer A-137 to A-139: what a keeper's restore sets aside, the recovery bounds, chunks from mesh-sdk

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 03:28:16 +01:00
parent 8392ec5c2d
commit 4e121e37cd
1 changed files with 9 additions and 0 deletions
@@ -524,3 +524,12 @@ names the principle that settles it, and is cited as "design 47 G A-n".
 - **A-136** (§483, §496; principle 1) The watchman's read of the build seats' steps goes, as §483 says: it times a
  running ask from the build seat's step-progress event; its `reads seat:node-build-*.steps` and the holder lookup
  for it go with it, and no holder event is needed.
+- **A-137** (§681, A-123; principle 2) Before a keeper's snapshot is restored, the recovery module sets aside the bus
+  names of the restore's module and kept data from the catalog entry of the fingerprint the node is running; for an
+  unprotected snapshot, the `stream` snapshot-get answers.
+- **A-138** (§557, §551, A-77, A-130; principles 1 and 7) The wait on snapshot-restored and the expiry are bounds as
+  well: settings `snapshot-restore-wait-minutes` (default 90) and `expire-every-hours` (default 24); every bound of
+  the module may be a fraction, so a whole test sets seconds; the expiry runs on a bound key's expiry, not a timer.
+- **A-139** (§681; principle 7; code shared between modules is in mesh-sdk) The chunks of a seat verb's answer are
+  received with mesh-sdk's own form (`buscalls`), the one the bus module sends with; where mesh-sdk has no receive,
+  it is added there, never built in the recovery module.