Answer A-59: the bus module's bundle reads the snapshot files

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 22:47:12 +01:00
parent 5b54cfdad1
commit 93985958bc
1 changed files with 4 additions and 0 deletions
@@ -227,3 +227,7 @@ names the principle that settles it, and is cited as "design 47 G A-n".
  `change` value `owner`, added to the seat `mesh-conditions`' enum in mesh-contracts; `words` stays for a change of the
  text. `seed-waits` waits on the operator through the finding's own `waiting-on`, which the indexer sets and the keeper
  copies, with no rule of the keeper's for that kind.
+- **A-59** (§681, A-45; principle 7, and who may do what is no question) The bus module's snapshots directory is made
+  readable by its tools bundle's account in its manifest (a group read, nothing more), so the bundle reads a
+  snapshot's file and sends its chunks as A-45 says; the keeper still writes and removes the files, and a protected
+  snapshot is still never handed out, by the bundle's own check.