Answer A-117: the node-engine's early pass, its entry-not-found, why on recovery endings

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 03:28:15 +01:00
parent 363da8fbab
commit 6af2aecb73
1 changed files with 6 additions and 0 deletions
@@ -465,3 +465,9 @@ names the principle that settles it, and is cited as "design 47 G A-n".
  `reads` takes `seat:<seat>.<state>` (route-proxy: `seat:mesh-provisioner.plans`); the grants part resolves it to the
  holder on record as it resolves a seat's views, and the module finds the holder through mesh-sdk's seat-list reader
  (the holder of the seat), naming no module in code; the tests that held code to a fixed name hold it to the seat form.
+- **A-117** (§683, §614, §560, A-95; principle 7) At a start, until its assignments, haves and resolved values are read,
+  the node-engine's pass composes only the modules whose kept want and kept entry it holds, a kept want standing for
+  their placement, and leaves every other module as it runs; the full pass follows once the inputs are read. It writes
+  `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.