From a7e339d7df312a8fbd69c187179be86ae58dc702 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 09:23:15 +0100 Subject: [PATCH] Answer A-252: the composition step's machines, cases and asks Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 7 +++++++ 1 file changed, 7 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 79eae638..b5de6b0e 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 @@ -278,3 +278,10 @@ the principle that settles it, cited as "design 47 G A-n". - **A-251** (§17, §383, §437; principle 8) The finding `branch-unprotected` has scope `merge`, id the owner, repository and branch escaped as one key name (`~~`), severity warning, and that scope and id as its subject. +- **A-252** (§354, A-167, A-174, A-226, A-243; principles 1, 2 and 7) The composition step's machines are the nodes + whose placement of the module names the step's branch in the seat's assignments (no branch read as the trunk); a + run on request on an unwatched branch takes the nodes placing the module on the trunk. Each request's cases and seats + come from the step's catalog revision through mesh-catalog's `revision` (each entry's manifest digest and verdict, + its `definitions`), depth compose, the one machine, one case `change`. A machine's node-engine build is what the + assigner keeps from the node-engine seat's own events, never read from the node-engine's bucket; where the step's + revision's node-engine entry differs from the trunk's, that build serves every machine. One run ask per machine.