From cb0efaf9a6ac8305033b05db89f7d2211f118d1a Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 01:06:29 +0100 Subject: [PATCH] Answer A-118: bound keys in the builder, the outgoing checker as it is 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 be20ac91..dce7c049 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 @@ -471,3 +471,6 @@ names the principle that settles it, and is cited as "design 47 G A-n". `entry-not-found` itself through its own writer (kind added, scope `module`, id the fingerprint, escaped). The seat `mesh-recovery`'s `ended` and `restored` events gain `why` (the hand act's words for a cancel), regenerated, which the recovery module fills and the node-engine's hold says. +- **A-118** (A-77, A-101, ยง167's checker that goes with G; principle 7) The shared `Asker` takes optional bound keys; + the builder arms them in its `bounds` state. The checker, which the runner replaces and which goes after G, keeps its + step bound as today and gains no `bounds` state.