From 1bfbeda9ec4da6cf21bc761c0e382461ad1251dc Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 05:44:43 +0100 Subject: [PATCH] Answer A-183: an unenforced mark is refused by both validators 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 4aafebeb..1e6c0a53 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 @@ -16,3 +16,6 @@ the principle that settles it, cited as "design 47 G A-n". keeps the node `ask-taken` named, and the drop is asked of that node's holder of the build seat; an untaken ask's drop is asked of any holder, which records it in the seat's shared drop key, so no holder takes it. Steps on `mesh-builds` and `mesh-wants`, whose seats serve no `drop`, are only ended superseded. +- **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.