From 8834af8bd020e6ee7d0bf21a9a8cd3a07d6a70ad Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 05:45:27 +0100 Subject: [PATCH] Answer A-184: main's subject keeps the checker's asks until it goes 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 1e6c0a53..83fa5e40 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 @@ -19,3 +19,6 @@ the principle that settles it, cited as "design 47 G A-n". - **A-183** (design 46 approval mark §4, §23; principles 3 and 7) A manifest that marks a verb nothing enforces is refused by the validator wherever it runs, as every rule's problem is; the indexer's "set aside to wait" is only its reading of a field it does not yet know (the reader edge of §23), so no new waiting verdict is added. +- **A-184** (clarifies A-170; §543; principle 3) Until main's subject goes, it also takes the checker's `check` and + `recheck` asks, so no ask that runs today is refused by G; a queue is only `delivery`, `check` or `recheck`, and + steprun's `AskKinds` lists no `step` queue.