From 1c29c4bc5691b403538833f76f0737125f6f4428 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 06:15:41 +0100 Subject: [PATCH] Answer A-231: an asker names its queue in invokes Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 027d03e2..65a60099 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -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:.accept.`, 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.