From cbbf17071862416acaf77d06bad749ebf5020ce2 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 16:53:42 +0100 Subject: [PATCH] Answer A-292: a node-engine's failed say is said again within the link, loudly Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 4 ++++ 1 file changed, 4 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 16c9bb3f..95133f94 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 @@ -430,3 +430,7 @@ the principle that settles it, cited as "design 47 G A-n". verb's chunked answer through one helper of mesh-sdk's process package, which subscribes to the call's chunks before it asks and answers the whole body; the checker, the indexer, the assigner and the recovery keeper (whose own receive moves into it) read a step's answer kept as an object through it. +- **A-292** (ยง590, issue 1975; principles 1 and 3) The node-engine's first statement keeps the bootstrapped seats (no + 'not yet'); every later change is said as `manifest-reads-changed` at once. A say the bus does not take is said + again within the same link through the SDK's bus retry until the bus takes it, and each failed attempt is written + to the engine's journal with the event's name; the held-for-the-next-link form stays only for a link that is lost.