Answer A-421: a trunk entry with no fp-src is matched to its release by the digests its build made

This commit is contained in:
2026-11-15 03:17:45 +01:00
parent 1de67e76ed
commit 9a60a312a0
@@ -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.