Answer A-109: a process's serves, their grants, chunks on the core bus

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 23:56:42 +01:00
parent ccfac82fd1
commit 9ff6368e82
1 changed files with 6 additions and 0 deletions
@@ -435,3 +435,9 @@ names the principle that settles it, and is cited as "design 47 G A-n".
  the reverted build, it calls the point's recorded `{tool, arguments}` as that module's tool on its own node through
  the tool runner, as `holder:node-engine` is granted (§406); `restore-kept` carries the snapshot only. §630's "passes
  its catch-up to restore-kept" reads "runs its catch-up after it".
+- **A-109** (A-107, §681, ADR 0675; principles 6 and 7) A process that answers its seat's verbs declares them in its
+  manifest's process section as `serves` (mesh-sdk's `ProcessBus` takes the field, its old "a process serves nothing"
+  gone), and the grants part composes the process account's subscribe of `mesh.seat.<seat>.call.<verb>.*` and
+  `.tool.<verb>` from it, plus, for a `chunks: true` verb, the publish of `.chunk.<verb>.>` and the subscribe of
+  `.ack.<verb>.*.*`. A snapshot's chunks are a transfer, published on the core bus with no stream; any caller of
+  `snapshot-get` receives the chunks (who may hear them is no question), a protected snapshot never.