From 40be107a7eb888629c3aaf5df22d54d445a2c0a6 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 12:20:18 +0100 Subject: [PATCH] Design 47 H: H-A-134 names delivery from new messages only Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) 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 02b1ad74..b490189e 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 @@ -607,7 +607,8 @@ Where two preparers disagreed, the chosen one is named. work is H4b), so the indexer never hears a source revision after its start and takes a merge in only at a restart. Until H4b, the indexer makes that durable itself when its bind finds none, with the configuration the mesh gives a module's seat-event consumer (mesh-sdk's SeatEventConsumerConfig, one message at a time, filtered to the branch, the ack wait of 30 s and - at most 5 deliveries the grants part gives a module's consumers, so that H-A-133's bound holds here too), and + at most 5 deliveries the grants part gives a module's consumers, so that H-A-133's bound holds here too, and + delivering from new messages only: the start's read by the verb covers the current revision, H-A-129), and the grants part matches it as it matches a module's consumers. It is the indexer's own kept consumer (P12: a module writes only its own); H-A-30 is read so. P1, P3. - **H-A-135 (the earlier model's trunk revisions and current mark go at the first branch take-in, 12:08)** Met live: