Answer A-386: a runner kept as it runs still gains the runner grants of what it carries

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-14 01:32:07 +01:00
parent 77a6a9aa68
commit 240f6401ce
1 changed files with 6 additions and 0 deletions
@@ -837,3 +837,9 @@ the principle that settles it, cited as "design 47 G A-n".
  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.
+- **A-386** (completes A-385 for runners kept as they run; live 01:31: grants 3c582b1b in, novox.node-tools unchanged
+  (2004 publish rights, none on KV_mesh-delivery-gate_records_state), since `runnerUsersKept` keeps a runner whose running
+  manifest does not say it is the tool runner whole (ADR 0601 §4); principles 7 and 3) A runner kept as it runs is written
+  as the union of the list in force and the runner grants its carried modules' bindings and events give (the ledger
+  readers, the new-event rights of A-384, the streams' names of A-382): what a carrying runner is given, never what a
+  plain module is given, so ADR 0601 §4 stands.