Design 47 H: H-A-168, a release pins the revision its entry lives in

This commit is contained in:
2026-11-20 17:40:44 +01:00
parent 95e9ae4e5b
commit 1858e92fa9
@@ -868,3 +868,11 @@ Where two preparers disagreed, the chosen one is named.
the importer becomes a mover (H §745) and the builder builds a new key against the release; a pin is the newest
released version on the branch, an accepted series' older version never standing over a newer release; a failed
re-pin is not acknowledged, so the package-published is delivered again. P3, P5, P7.
- **H-A-168 (a release pins the revision its entry lives in, 17:40)** Met at main.23 (17:36): the pin judge
removes a kept revision that no record pins once its pipeline ended, and its entries with it, while the passed
pipeline's release had just become the want of every machine holding the module; the node-engine asked the entry
by fingerprint and was told "no entry is kept", so the want is held "entry-missing" for good. What a want names
must exist (P2): a passed pipeline's release pins the catalog revision its mover's entry lives in (a release pin,
beside the pipeline's pin of H-A-147), freed only when a newer release of that module on that branch is written
as the want everywhere the module is held (the assigner's `written` says so); removeUnlisted never drops an entry
a release pin keeps. P2, P3, P7.