From 50e6d1638186798fecc8376dd5bd1854b56d0e70 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 03:56:12 +0100 Subject: [PATCH] Design 47 H: H-A-103, the indexer's derived state between take-ins Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy --- 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 92a010df..17807c7e 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 @@ -437,3 +437,8 @@ Where two preparers disagreed, the chosen one is named. - **H-A-102 (readers developer, 03:53)** `indexer_pending` answers `{"held": [{branch, source, why, since}]}`, `since` in RFC 3339, one form with the indexer's state `held` (H-A-97); the watchman reads it with a local type over the seat's `TakeInPending` plus `since`. P7, P8. +- **H-A-103 (indexer developer, 03:55; two things held in memory)** (1) Between take-ins the indexer's view of a module + change (a build's imports, a toolchain change, the reconcile) is derived state: the kept revision is the truth and a + restart rebuilds the view from it and the events after it, so nothing kept lives only in memory. (2) A held + message's acknowledgement handle is the bus consumer's; after a restart the bus redelivers the message and the state + `held` says why it was held. Neither is a kept truth in memory; the review reads them so. P2, P3. -- 2.54.0