From 9a60a312a031ef5aa8216faa457ea48d7f655533 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 15 Nov 2026 03:17:45 +0100 Subject: [PATCH] Answer A-421: a trunk entry with no fp-src is matched to its release by the digests its build made --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++++ 1 file changed, 5 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 0250e72b..c841f2d0 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 @@ -1063,3 +1063,8 @@ the principle that settles it, cited as "design 47 G A-n". say in their log that they give the message up, naming its subject, the artifact and version it carries, and the last refusal. (Quick fix, said: the same silence holds for every part that hears an event; the thorough fix is the SDK's hearing saying it once for every part, noted on the issue of the hand start.) +- **A-421** (A-419, ADR 0601 ยง1; read live 2026-11-15: six entries of trunk revision 225 carry no `fp-src`, since a + fingerprint that moves without a merge clears it, so A-419 finds no release for them; principles 2, 3 and 7) A trunk + entry with no `fp-src` is matched to the release whose parts' digests are the digests its fingerprint's `build.ended` + made, as the assigner already hears it; an entry with `fp-src` is matched as A-419 says. An entry neither finds is + said as A-419 says, with which of the two was tried.