From 3c6b24fe0c7568401c7c9d5560cc90fb167a3b39 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 21:40:39 +0100 Subject: [PATCH] Design 47 H: H-A-193, the grants holder learns the newest revision from the event --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 5 +++++ 1 file changed, 5 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 0b827f53..e9908b21 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 @@ -1027,3 +1027,8 @@ Where two preparers disagreed, the chosen one is named. registry seat's package-published event of that path and series (H-A-165) and pins the version that event carries, never a number it derives; a build module given no pin refuses the build, loud, never takes another path's version. P1, P4, P7. +- **H-A-193 (the grants holder learns the newest revision from the event, 21:40)** Met in the build of the grants-for + cache: a call still read the first page of each revision (up to 768 KB) only to learn the branch's newest number. + The grants holder already hears the catalog-revision event; that event names the branch's newest revision, so the + holder asks the catalog seat's revision verb only for a revision it does not hold, never to learn the newest (P4: + events first; a verb only where an answer is needed). Before the first event after a start it asks once. P4, P7.