From 20e3e1a3cd05085aaf0e0420309ed3eaf0180dd0 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 09:19:34 +0100 Subject: [PATCH] Answer A-248: the run asker names its asker Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 2 ++ 1 file changed, 2 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 6b506019..aa7b6bc7 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 @@ -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.