From 19f5ad86d21af4fe0fb7ce8bb616d2bb113a392d Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 04:03:00 +0100 Subject: [PATCH] Answer A-391: the indexer's start replay writes the view once, and says its length Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 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 ecd335c6..34170f21 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 @@ -871,3 +871,8 @@ the principle that settles it, cited as "design 47 G A-n". grants part reads a single `*` as every seat verb; principles 7 and 3) The verb revision's callers are the parts whose entry in the newest trunk revision declares `seat:mesh-catalog.revision` or a single `*` in invokes, as the grants part reads invokes; the holder stays off the list. +- **A-391** (live on novox: the indexer's start ran 50 minutes of CPU in its first hour without reaching its take-ins + watch, so the seed was never asked; it wrote the whole catalog view again after each finished build of the build log, + though none changed a module; principles 7 and 3) A finished build writes the view again only when it changed a module; + at the start the build log's finished builds are applied first and the view is written once, the replay said in one + line at its start and one at its end with its count and duration.