Answer A-48: the assigner's outside waits, ask, release and rule

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 22:39:19 +01:00
parent da5c034928
commit a8c596c270
1 changed files with 7 additions and 0 deletions
@@ -186,3 +186,10 @@ names the principle that settles it, and is cited as "design 47 G A-n".
  entry as `entry` answers it) and `want.<module>` (the want as `wanted` says it), beside the composition. Its other
  users of `compose/frombus` keep that reader until their own lines move them; only the node-engine's own reads of the
  indexer's and builder's states go in this change.
+- **A-48** (§706, §276; principle 7, one way per part) The assigner's outside waits: a state `waits`, declared in the
+  same form as the assigner's other states, key `<node>.<module>.<fingerprint>`, read by `assigner_waits` and written by
+  the process and by `assigner_release`; the ask goes the way the assigner asks everything, through its state `asks`
+  as a new kind `outside` (key `outside.<node>.<module>.<fingerprint>`, options go on and count as failed), its answer
+  read as the others are; `assigner_release` with `how` releases an outside wait and without it ends a put as today;
+  a want held for M's own network says `RuleNotHeld` with words naming the open `machine.<M>.network`. As the
+  developer proposed on mesh-delivery feat/47-G-outside5.