From f1036802510b5d52c6fc269f19ddbdf4a49c5a90 Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 11 Nov 2026 23:24:00 +0100 Subject: [PATCH] Answer A-89: every asker reads its warrant from the router's record Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md index 6c4c1ab6..db84c24c 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md @@ -344,3 +344,6 @@ names the principle that settles it, and is cited as "design 47 G A-n". read by the tools bundle following the catalog half itself, as A-70 has it for `reserved`. - **A-88** (§610, the main file's item 85; principle 7) mesh-networking's A-N1 (callers named in its seven seat definitions) is not brought in: from G no verb names its callers (§610), which supersedes item 85's reading. +- **A-89** (§37, §700, A-74; principle 7, one way for every asker) The runner reads its approval ask's warrant from the + router's record of its ask, through the seat `operator-channel` as A-74 has it, never from the decided event's body; + the decided event only wakes it.