Answer A-45: the bus module's bundle answers mesh-broker's verbs, the keeper does the work

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 22:37:07 +01:00
parent 315cd7ec24
commit 6818f61ce0
1 changed files with 6 additions and 0 deletions
@@ -169,3 +169,9 @@ names the principle that settles it, and is cited as "design 47 G A-n".
  the act's id, `busy` with the running act's id, or `error` with why), and records its caller as `by` from the proved
  caller (`by-caller`), as every acting verb does. mesh-sdk's seat definition reader gains the verb field `chunks`
  (§681) in the same change, with the bootstrap copies of `mesh-broker` laid again byte for byte.
+- **A-45** (§681, ADR 0675; principle 7 and the standing rule that a process answers no call, mesh-sdk 1171/AC3) The bus
+  module answers the seat `mesh-broker`'s verbs through its tools bundle, as every bundle answers a seat verb
+  (`SeatAnswer`, the proved caller from the runtime), and sends a snapshot's chunks and hears their acks from there
+  (`SeatPublish`, its subscription); the keeper's process does the work that needs the bus and the files (taking,
+  restoring, removing), handed over and answered through the bus module's own `requests` record, as the bundle hands
+  the keeper its requests today. Where §681 says "the keeper's process serves", read "the bus module serves".