Answer A-231: an asker names its queue in invokes

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent 24a0fc7272
commit 1c29c4bc56
1 changed files with 4 additions and 0 deletions
@@ -201,3 +201,7 @@ the principle that settles it, cited as "design 47 G A-n".
 - **A-230** (§554, §565, A-124; principle 7) A restore point's `Point` gains `names`, the bus names it took, one per
  bus object as `Aside`'s; the recovery module fills it when it takes a point, and the grants part reads
  `points[].names` and `asides[].names` from `kept-points`.
+- **A-231** (§544, §601, A-163, A-170; principles 3 and 7) An asker names the queue it asks in its manifest's `invokes`
+  as `seat:<seat>.accept.<queue>`, read by one mesh-sdk `catalogue` helper that the validator, the indexer's kind-6
+  edge and the grants part share; every asker of a build seat gains that entry in G, so the named workers stand from
+  G's delivery and the purge finds nothing to remove.