Answer A-278: the seat-definition function lives once in mesh-sdk

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 11:28:25 +01:00
parent f9aa43bf09
commit efcc065f8f
1 changed files with 4 additions and 0 deletions
@@ -369,3 +369,7 @@ the principle that settles it, cited as "design 47 G A-n".
  (the second reader release reads it from 1 to 8192, and since mesh-delivery #206 the grants part carries it onto the
  bucket). The manifest validator refuses an `approvals` state that lacks `key-ttl`, whose `ttl-seconds` is not 172800, or whose
  `max-mib` is above 64; with none declared the bucket takes the default 64 MiB.
+- **A-278** (A-179, A-186; principle 7, and code shared between modules lives in mesh-sdk) The seat-definition
+  function `AnswerSeat` takes is written once, in mesh-sdk's `seatlist` (the definition of a seat from the list a part
+  follows; none until the list is read, none for a seat it does not hold), and every holder passes it. A part that
+  serves a seat verb follows the seat list with its grant, as the pipeline runner and mesh-recovery now do.