Answer A-242: tiers from the assigner's difference; the view keeps waits

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent 92358ddfd7
commit 534fd88be4
1 changed files with 5 additions and 0 deletions
@@ -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.