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
2026-11-12 09:41:28 +01:00
parent ea4cb84ce1
commit 01d8328758
1 changed files with 4 additions and 0 deletions
@@ -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: <error>"
  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.