Answer A-126 and A-127: one seat-holder helper; serves beside the bus only

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 03:28:15 +01:00
parent a1faef315f
commit 401f5dcb8b
1 changed files with 5 additions and 0 deletions
@@ -494,3 +494,8 @@ names the principle that settles it, and is cited as "design 47 G A-n".
  `names` in the mesh-recovery contract, regenerated; no names joined into one string.
 - **A-125** (§655) The restore of one stream moves into mesh-sdk's bussnap beside its snapshot, and the bus module
  imports it from there; the recovery module's builder moves it, in the same work.
+- **A-126** (A-82, A-101; principle 7) Who holds a seat now is read by one mesh-sdk helper beside the seat list
+  (`seatlist`), through the assigner's `assignments` verb; operatorask and the view call it, and no part keeps its own
+  copy. The builder's holder at a catalog revision (`versions.HolderOf`) answers another question and stays.
+- **A-127** (A-115 over A-109, A-110) `serves` is read only beside a process's `bus`: mesh-sdk's process parse, the
+  grants part's process-serve composition and the indexer's manifest check test follow A-115; a `serves` inside `bus` is refused.