From dcaad0c6a41006a53015d6d8d6d624087c4279a8 Mon Sep 17 00:00:00 2001 From: jochen Date: Tue, 17 Nov 2026 01:23:38 +0100 Subject: [PATCH] Answer A-456b: the release record is bounded per module; a publish item ends with its release or its reservation --- 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 f021cb34..2b29e9a8 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 @@ -1435,3 +1435,10 @@ the principle that settles it, cited as "design 47 G A-n". node's module, and only when its running build has no entry; and only a store with no known address (the holder opens no listen, or two) holds the modules that fetch from it: every other fault of finding the store still refuses the node, as before (principle 3). (From the review of A-461: novox's placement of `distribution` names no build.) +- **A-456b** (A-456a, A-457a; principles 7, 11 and 3) The builder's record of releases is one key per module, + `released.`, holding its last `released-kept` releases (fingerprint and version; a setting, default 16), the + oldest dropped when a newer one is written; a rerun of an older build's step than those is judged as a build with + no reservation. A publish item is deleted when its reservation is dropped or taken over, and when its release is + written; never because its artifacts are published, so a release that never comes is tried again. At its start the + builder asks an item for every reservation of a done build, whatever its artifacts. (From the review of A-456a and + A-457a: one key per release filled the 1 MiB state for good, and an item went before its release.) -- 2.54.0