From 272fe8bdb5e1f59a36e1ccd4251cb7f157a60908 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 21 Nov 2026 15:53:36 +0100 Subject: [PATCH] Design 47 H: H-A-279, a build whose number a registry holds elsewhere is built again at the next free number --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md index 7a17ce78..fa2fbcfe 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md @@ -1601,3 +1601,9 @@ Where two preparers disagreed, the chosen one is named. whose content is version-free (a program, a bundle, an archive) keeps its digest. Where the publish cannot form it from the kept output, the build is built again at the new number. The finding version-held-elsewhere clears at the module's version-released. P2, P4. +- **H-A-279 (a build whose number a registry holds elsewhere is built again at the next free number, 15:53)** Corrects + H-A-278 on the fact: every artifact carries its version at build time (the Go zip's paths, a program's stamped + version, an image's and a bundle's environment), so no digest survives a move. A done build whose number a + registry holds at another digest is built again at the next free number (the reserve skips held numbers, H-A-275, + and records fresh digests); no move keeps digests; the finding version-held-elsewhere names both digests and + clears at version-released. P2 (the published bytes carry the number they are published under), P4.