From 525a9590cd479d0f967d1fd25a3fba78d761f00a Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 12:09:52 +0100 Subject: [PATCH] Answer A-396: every module is composed as invoking the tool runner's own reads Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index f46182d7..4d0bd4ff 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -889,3 +889,7 @@ the principle that settles it, cited as "design 47 G A-n". declare it in invokes, while the runner reads the catalog half for every module it serves; principles 7 and 4) Every part the newest trunk revision holds may read the verb revision, and so may the tool runner; the holder stays refused. ADR 0663 ยง2's rule that a part reads it only by declaring it is proposed for its end. +- **A-396** (live: the shanks build runtimes' seat list and catalog-half reads were refused on their caller-named subjects, + since no build module's manifest invokes them; principles 7 and 4) Every module is composed as invoking the tool runner's + own reads (the seat list's verb, the catalog half's revision and registrations, the delivery seat's source), so each + account the runner serves a module on may ask them.