From 93985958bc11e5fa474f86ee8fcd66e1ffe3241a Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 11 Nov 2026 22:47:12 +0100 Subject: [PATCH] Answer A-59: the bus module's bundle reads the snapshot files Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md index edb1f33d..c66cf8c3 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md @@ -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.