Answer A-189: version-delivered and version-released read whole at start

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent 92709ec311
commit 0d153c98e0
1 changed files with 5 additions and 0 deletions
@@ -34,3 +34,8 @@ the principle that settles it, cited as "design 47 G A-n".
 - **A-188** (A-172, §170, §151; principles 3 and 7) A take-in writes its entries (each with its module) into the
  gate's record, so `recovery-merged`'s `module` is filled from the record; no forge-made open path is built, since
  G ends the mark (§151). A record of the old milestone form, made before G, says no branch.
+- **A-189** (§376, §374, A-181; principles 1, 2 and 7) At its start the assigner reads whole, as A-181 reads
+  `build.ended`, the streams of its own `version-delivered` and of the catalog seat's `version-released`, so it says
+  each version delivered once and knows the released ones. A dependent whose want changes fingerprint waits, by an
+  edge of kind 2, 4 or 6, for its dependency's newest released version on the dependent's branch not yet said
+  delivered; on a branch where no version is released there is no wait.