From 0d19a01ea71df8d3929fe7a2f39011870f869b94 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 03:06:30 +0100 Subject: [PATCH] Answer A-146: the reader release carries the foundation part's exception Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md | 2 ++ 1 file changed, 2 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 080b34b4..fdb9204a 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 @@ -551,3 +551,5 @@ names the principle that settles it, and is cited as "design 47 G A-n". - **A-145** (§621, §494, §697, ADR 0633 §6; principle 7) The second reader release carries only §621's words and what the trunk validator needs to judge the new indexer's manifest and the `by-caller` definitions; §529's finding-stream rules and A-116/A-128's seat reads are G's own validator rules, judged by the change's validator, and stay in G. +- **A-146** (A-145, §529, A-30; principle 5) The second reader release also carries §529/A-30's exception for a + foundation part's kept old sections, and only that, since the trunk validator must accept the new indexer manifest.