Answer A-89: every asker reads its warrant from the router's record

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 23:24:00 +01:00
parent c096c4af1c
commit f103680251
1 changed files with 3 additions and 0 deletions
@@ -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.