Answer A-107: a process answers its seat's verbs, the operator's yes

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 23:48:03 +01:00
parent 362c8074d1
commit f29a8f0ebe
1 changed files with 7 additions and 0 deletions
@@ -424,3 +424,10 @@ names the principle that settles it, and is cited as "design 47 G A-n".
  minutes are a constant; an expired step ends `could not run` and the others run on. The runner's write verbs wait on
  the operator's answer whether a process may answer calls (then the process writes `pipelines` by compare-and-set
  itself); the runner gains a whole-module integration test against the bus in G.
+- **A-107** (the operator, 2026-11-11 about 23:45 CET: yes, a process may answer calls; principles 1 and 7; withdraws
+  A-45, A-59, A-60's bundle principal, A-70, A-87's bundle part and A-104's bundle part) mesh-sdk's rule that a process
+  answers no call (issue 1171, AC3) is removed: a process answers its seat's verbs directly over the bus, with the
+  proved caller, through one mesh-sdk call. The part that holds the data answers for it: the bus module's keeper serves
+  `mesh-broker`'s verbs and sends the chunks itself; the builder's process serves `reserved` and `builder_build`; the
+  runner's process serves `review`, `rerun`, `accept` and `cancel`, writing `pipelines` by compare-and-set; the chunk
+  subjects go to the process that answers.