Answer A-248: the run asker names its asker

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent 41b2345ba4
commit 20e3e1a3cd
1 changed files with 2 additions and 0 deletions
@@ -264,3 +264,5 @@ the principle that settles it, cited as "design 47 G A-n".
  accepted at), so a revision held for another indexer is never asked again; `validation` sits on the newest pending
  value of the revision alone. The answer is read from the `step-ended` event's own output and output object, never
  through the build seat's `steps`; the ask is put through the delivery SDK's `buildrun.Asker`.
+- **A-248** (A-163, A-232; principle 8) `buildrun.Asker` gains the asker its subject names (the caller's seat name,
+  A-163), empty meaning the builder until the asker rename at the join; the ask's own `Asker` field is left as it is.