Answer A-296: seat forms in the manifests, own buckets from the credential's module

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 18:54:41 +01:00
parent eed5be9244
commit ef76908e0d
1 changed files with 4 additions and 0 deletions
@@ -451,3 +451,7 @@ the principle that settles it, cited as "design 47 G A-n".
  `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`.
+- **A-296** (A-210, A-131; principles 1 and 2) Where A-210 makes a part find another by the seat it holds, the part's
+  manifest takes the seat forms in the same change (`seat:<seat>.views.<state>` for a consume, the seat's verb for an
+  invoke), and a part names its own buckets from its credential's module, never from a constant. Which seat a module
+  that holds none (the delivery view) or several (the assigner) is found by is a design line (§717).