Answer A-210: other modules found as seat holders when called; callers by seat

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent ab03e427f4
commit a56c9b6262
1 changed files with 5 additions and 0 deletions
@@ -125,3 +125,8 @@ the principle that settles it, cited as "design 47 G A-n".
  `keys.EscapeName`, the one escape form for every name in a key, in both gates: `<node>.act.<escaped digest>`. The
  kind (a test's in-memory state accepting a key the bus refuses) is fixed where it lives: mesh-sdk's in-memory state
  for tests refuses every key the bus would.
+- **A-210** (§7, §428, A-126, A-131, ADR 0596; principles 3 and 7) A module that calls another module's tool or hears
+  its module events finds that module as the holder of the seat it holds, with `seatlist.HolderOf`, when it calls,
+  asking again after a failure and never stopping its start for it; a read of another module's bucket goes (each by
+  its own row). A tool's callers list names no module: it takes the holders of the seats `node-tool-runner` and
+  `mesh-healers` from the seat list when a call is checked, beside `operator`.