From d0c7373d386e310c07919904e4c28e2b0ab80005 Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 11 Nov 2026 23:26:25 +0100 Subject: [PATCH] Answer A-92: the node-engine's bound keys 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 2fee1462..4212e612 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 @@ -355,3 +355,6 @@ names the principle that settles it, and is cited as "design 47 G A-n". operator-channel contract's `AsksByAskerIDValue` gains the field. A step the module's policy does not name is no step of its pipeline, so `Status` has no open question for it. The runner places a pipeline's steps when it starts it and asks each build seat for its step, as its asking half; that half is built in G. +- **A-92** (§560, A-77, §627; principle 7, and who may do what is no question) The node-engine's bound keys live in a new + state `bounds` of the seat `node-engine`'s definition, declared in its old section as a foundation part's states are + (§627), key `.` with its own time to live; the node-engine's account holds it as it holds its other states.