Answer A-116: a read of a seat holder's state names the seat

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 03:28:15 +01:00
parent c4ad757265
commit 363da8fbab
1 changed files with 4 additions and 0 deletions
@@ -461,3 +461,7 @@ names the principle that settles it, and is cited as "design 47 G A-n".
  `bus`, not inside it: the grants part adds the serve subjects to whichever account that process runs on, the
  module's own when it declares no `bus`, so a process keeps hearing what it heard. Only a seat's verbs move to the
  process: a module tool such as `builder_build` stays its tools bundle's (A-87).
+- **A-116** (§636, §616; principle 7) A read of a seat holder's state names the seat, as §616 does for views:
+  `reads` takes `seat:<seat>.<state>` (route-proxy: `seat:mesh-provisioner.plans`); the grants part resolves it to the
+  holder on record as it resolves a seat's views, and the module finds the holder through mesh-sdk's seat-list reader
+  (the holder of the seat), naming no module in code; the tests that held code to a fixed name hold it to the seat form.