Answer A-385: a kept account is the union of the list in force and this pass's composition

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-14 01:06:35 +01:00
parent 9e619006c7
commit 77a6a9aa68
1 changed files with 6 additions and 0 deletions
@@ -831,3 +831,9 @@ the principle that settles it, cited as "design 47 G A-n".
  the next message, mesh-tools node-tools internal/bus/subscribenew.go) asks of the stream that carries the events its
  bundles hear: the create of an unnamed consumer filtered to those events' subjects, its next-message fetch, its info and
  its delete, on EVENTS and on every kept seat stream; the same form for every runner, composed in one place.
+- **A-385** (generalizes A-383, met a fourth time: live 01:00 "mesh-delivery-gate's bundle asked mesh/ledger.get and it
+  failed after 10s", the gate's ledger `records` exists and is bound, and novox.node-tools holds no right on
+  KV_mesh-delivery-gate_records_state, since a held runner account is copied whole from the list in force; principles 7
+  and 3; A-363's union) An account grants keeps beyond a pass, a runner's included, is written as the union of the list
+  in force and what this pass composes for it (its carried modules' grants from the trunk's manifests and their
+  bindings), never the list in force alone; a pass that only adds still never takes from a loaded user.