From e58be12323f464be075803047da2896861167a15 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 09:53:17 +0100 Subject: [PATCH] Answer A-267: the composition step's progress names the runner as its asker Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 3 +++ 1 file changed, 3 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 1e4e84cf..2549408f 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 @@ -331,3 +331,6 @@ the principle that settles it, cited as "design 47 G A-n". process; no holder changes and no mark moves. - **A-266** (A-264, A-265, ADR 0132; principle 7) `approvals` is the gate's verb, served wherever a marked verb is: `CanHold` and the validator's same rule ask no holder to name it in its claim's `serves` or its tools. +- **A-267** (§496, §481, §22, A-170; principle 7) The composition step's `step-progress` carries `asker` `runner`, the + one asker that sends the accepted kind `step` on `mesh-wants`; the asker rename after join 11 (A-163, A-170) reads + it from the accept subject's asker token instead.