Answer A-186: the seat server takes the definition from its caller's seat list

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent ae6d3ddecc
commit 0a10272f3d
1 changed files with 3 additions and 0 deletions
@@ -25,3 +25,6 @@ the principle that settles it, cited as "design 47 G A-n".
 - **A-185** (A-180; principle 7) The catalog client (`meshcatalogclient`'s catalog follower), which already hears every
  `catalog-revision`, hands a candidate's revision it does not keep to a hook its caller sets; the runner sets it to
  place a run's pipelines. mesh-sdk's event hub keeps its one handler per pattern.
+- **A-186** (A-179; principles 3 and 7) `conn.AnswerSeat` takes the seat's definition from its caller, which reads it
+  from the seat list it already follows; a verb the definition does not hold, or a definition not yet read, is
+  refused for every caller and said so, so a holder answers only once its seat list is read.