Answer A-150: restic's night process gets its own bus

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:27 +01:00
parent 855149b25b
commit 9e737e7c4c
1 changed files with 3 additions and 0 deletions
@@ -561,3 +561,6 @@ names the principle that settles it, and is cited as "design 47 G A-n".
 - **A-149** (§634, §527, A-120; principles 2 and 7) The node-engine knows its own name at start from its applied
  store: the record of the module whose fingerprint is its own `MESH_FINGERPRINT`; the finding writer, discovery and
  the vault login use it. Only on a first start with no such record do they wait for the first composing to name it.
+- **A-150** (§563, A-107, A-115; principles 1 and 7) restic's `night` process, which dumps, gets a `bus` of its own
+  (its own broker account, as the recovery module's process has) and says item-started and item-ended and reads the
+  recovery module's events itself; no local request to the tools runtime, and the backup does not move into it.