Answer A-118: bound keys in the builder, the outgoing checker as it is

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 03:28:15 +01:00
parent 6af2aecb73
commit cb0efaf9a6
1 changed files with 3 additions and 0 deletions
@@ -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.