Answer A-92: the node-engine's bound keys

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 23:26:25 +01:00
parent 03813cce78
commit d0c7373d38
1 changed files with 3 additions and 0 deletions
@@ -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 `<what>.<id>` with its own time to live; the node-engine's account holds it as it holds its other states.