From 01d8328758c9d29ccef55f5769990182fc58fddf Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 05:31:47 +0100 Subject: [PATCH] Answer A-163: an ask's asker is its seat's name, checked against the definition's callers Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md index accd1134..6830bea5 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md @@ -608,3 +608,7 @@ names the principle that settles it, and is cited as "design 47 G A-n". build, carrying `outcome` (done or failed) and, when failed, `error`; the assigner's hold says "failed: " from it and "is being built" while no `build.ended` of that fingerprint is heard. The assigner never reads the builder's `builds` bucket; its read there (put.go:85, the manifest's `reads`) goes. +- **A-163** (§543, §544; principles 7 and 8) The asker in an ask's accept subject is the asking seat's own name + (`mesh-pipeline-runner`, `mesh-catalog`, `mesh-wants`, `mesh-builds`, `mesh-delivery-checker`), not a nickname, so + steprun checks it against the callers the build seat's definition lists, read from the seat list; no table of its + own and no name map. A body's kind is the word the seat definition gives; a queue keeps its own name.