From 534fd88be41cacb0cbccee9db3f0781c619e20b4 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 06:26:04 +0100 Subject: [PATCH] Answer A-242: tiers from the assigner's difference; the view keeps waits Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++++ 1 file changed, 5 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 d21c2fae..ef4cbfa4 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 @@ -240,3 +240,8 @@ the principle that settles it, cited as "design 47 G A-n". - **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. +- **A-242** (§512, §186, §376, §378; principles 1, 2 and 7) The assigner's `difference` fills `Tiers` and each + change's `after` (the kind of edge that orders it), computed in its compare; the view orders nothing itself. A + `view_tiers` call for a source revision compares the kept assignment revision whose catalog for that branch is that + source revision with the revision kept before it. The view keeps a state `waits` (key owner, step, node, module) + written by its process from every part's `wait-held` and `wait-ended` it consumes, read by its own read tool.