From 92358ddfd76b92b902f03f8bdf9eeca9314c83af Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 06:25:43 +0100 Subject: [PATCH] Answer A-241: the validation always judges against the whole seat list Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 3 +++ 1 file changed, 3 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 45703dbe..d21c2fae 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 @@ -237,3 +237,6 @@ the principle that settles it, cited as "design 47 G A-n". manifest's `uses` gains `mesh-grants` beside the `invokes` of `seat:mesh-grants.withheld` H-21 added. - **A-240** (§354, ADR 0596; principle 1) The assigner waits on its composition run's answer by hearing the build seat's `step-ended` for that ask, never by reading the seat's step state. +- **A-241** (§712, A-234; principle 3) The validation's `seats` are the branch's revision's seat definitions (A-234) + with the merges' changed definitions laid over them, so a revision that touches no definition is still judged + against the whole seat list.