From 6fde0ff09d7f5c1629cee900b100808b3a3f8cc5 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 04:14:01 +0100 Subject: [PATCH] Design 47 H: H-A-110, the node-engine asks entries again on catalog-revision Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 3 +++ 1 file changed, 3 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 5ea2f007..8943853c 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 @@ -472,3 +472,6 @@ Where two preparers disagreed, the chosen one is named. - **H-A-109 (readers developer, 04:12; the view's held take-ins)** A held take-in names no module in the view: its movers are not known until it is taken in, so the view says the branch's held take-in in the tiers' pending words (branch, source, why, since) and holds no module for it (option b). P3 (no module named on a guess). +- **H-A-110 (node-engine developer, 04:13)** Within one link, the node-engine asks its unanswered entries again when it + hears the seat mesh-catalog's `catalog-revision` (one per take-in): the composer consumes that event for this alone and + calls the entries client's `AskAgain`; and once more at each link's start. No timer. P1.