From 46b6b741485d03c0201e6cb02398307bff4bb134 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 22:47:32 +0100 Subject: [PATCH] Answer A-408: the builder reads the kept versions-filled at its start --- 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 5272694d..1017c2d2 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 @@ -968,3 +968,8 @@ the principle that settles it, cited as "design 47 G A-n". its want says is being built (the newest of its first watched branch), read through the seat `mesh-catalog`'s `entry` as any entry: what it provides, claims and requires there stands for the running build, for resolving the node alone. A want that names no newer build leaves the module as today (a name alone), said once. +- **A-408** (live, the build node 2026-11-14 22:45: the builder held every build "wait-held, the catalog has not said + versions-filled", while the indexer said it once at 01:33 UTC and keeps it as said; the builder keeps the mark in memory + alone and its durable consumer took the event once, so a restart lost it; principles 1 and 3, §369, §372) The builder + reads at its start the last `versions-filled` the seat's stream keeps (it is kept with no age limit, §372) by a direct + read of the last message on its subject, and takes it as heard; the event heard later sets it as before.