From 4866f7991de9127c836d1579ba8317e725640585 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 21:46:32 +0100 Subject: [PATCH] Design 47 H: H-A-195, what the grants holder keeps of the catalog --- 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 0f1e5b3d..e101bdb2 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 @@ -1038,3 +1038,9 @@ Where two preparers disagreed, the chosen one is named. the package registry seat's `versions` verb once for that path and takes the newest version in the accepted series (H-A-184/185); only then does it hear the published events (P1: the truth is on the bus, a memory is a cache of it; P4: a verb where an answer is needed). P1, P4, P7. +- **H-A-195 (what the grants holder keeps of the catalog, 21:46)** Met in the review of H-A-193: the kept revisions had no + design line and their bound stood in the code. The grants holder keeps, in memory for the process's life, the catalog + revisions it read whole, keyed by branch, kind, group, heads and number; at most `grants-for-revisions-per-branch` + of them per branch (a setting of the module, default 4, oldest dropped; a run's candidate counts within its branch's + bound), and only for the branches it follows (the watched branches; a branch dropped from them frees its revisions). + A kept revision is a cache of the catalog seat's own truth, never a state of the mesh. P1, P4, P11.