Answer A-295: a callers list names a seat, resolved from the seat-holders view the SDK follows

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 18:54:41 +01:00
parent 12c9c1efcf
commit eed5be9244
1 changed files with 4 additions and 0 deletions
@@ -447,3 +447,7 @@ the principle that settles it, cited as "design 47 G A-n".
  mesh-builds are not build seats: their accepted kind `step` stays without a token (not `by-caller`), and the
  composition step's step-progress names its asker as the one caller its seat's definition lists, read from the seat
  list; only the three build seats carry the asking seat's name as a token.
+- **A-295** (A-210; principles 1 and 7, one shared mechanism in the SDK) A tool's callers list names a seat as the entry
+  `seat:<seat>`, resolved in mesh-sdk's verb callers by a holder function the part is given; that function follows
+  the assigner's seat-holders view (as the watcher does) and answers from what it last heard, never one call per
+  checked call; each part's list becomes the operator, `seat:node-tool-runner` and `seat:mesh-healers`.