From 12c9c1efcfcdea51e98f756665cce46679e86214 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 18:20:59 +0100 Subject: [PATCH] Answer A-294: mesh-wants' step keeps no token; step-progress names the caller its definition lists Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 4 ++++ 1 file changed, 4 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 e0c38260..a8c42d0f 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 @@ -443,3 +443,7 @@ the principle that settles it, cited as "design 47 G A-n". writes the refused key `..` with the event's words, a later done end of the module (at any fingerprint) deletes the refused key such an end wrote, so the state never says refused for a done build, and an end naming a branch moves nothing. +- **A-294** (corrects A-267; ยง600, A-170; principle 7, the seat definition is the one source) The seats mesh-wants and + mesh-builds are not build seats: their accepted kind `step` stays without a token (not `by-caller`), and the + composition step's step-progress names its asker as the one caller its seat's definition lists, read from the seat + list; only the three build seats carry the asking seat's name as a token.