From bb344445f7d8134e3498df01f4a8329fc736fe51 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 21 Nov 2026 01:04:21 +0100 Subject: [PATCH] Design 47 H: H-A-222, the revision verb answers the store; the builder's picture holds by number --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 8 ++++++++ 1 file changed, 8 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 842297d9..3d9d9112 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 @@ -1218,3 +1218,11 @@ Where two preparers disagreed, the chosen one is named. pipeline-ended, wait-held and wait-ended subjects carried the source in their last token. The token is named `` and carries the pipeline's revision number, the same number as its key (P1: the name matches the value); no consumer filters on that number, every reader takes the body, so only the value changes. P1. +- **H-A-222 (the revision verb answers the store; the builder's picture holds by number, 01:04)** Met live: the catalog + seat's `revision` verb answered from the tools bundle's in-memory view of the trunk, which ran one or more revisions + behind what the indexer kept (every reader waited: the runner four minutes for revision 52, the builder past its + bound), while the kept revisions were on the bus all along. The verb answers the newest kept revision read from the + store at the time of the ask (and a given number from its kept object), never a view in memory; the view stays a + cache for entries. And the builder's picture holds an ask when the ask names a revision number the catalog keeps + (read by number, H-A-205), whatever the source comparison says; the source is compared only for an ask naming no + revision. P1 (the truth is on the bus, a view is a cache), P4.