From 5dee91703f2efe839a74f2728a72e2ee1ab0a056 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 13 Nov 2026 13:02:51 +0100 Subject: [PATCH] Answer A-350: the catalog's fill starts above every number the builder gave, published or not Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 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 43b7d054..b0073858 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 @@ -702,3 +702,8 @@ the principle that settles it, cited as "design 47 G A-n". - **A-349** (sharpens A-345; §529; principle 7) The modules whose old forms the release accepts before G puts them on the foundation list are those §529 and §584 name: gitea, distribution, the node-engine and the pipeline runner (mesh-delivery-pipeline). The runner is new in G, so no trunk verdict moves. +- **A-350** (sharpens §372; principles 2 and 3) The fill takes, for each module, the highest version the builder's state + `versions` gave a number, whether its state is `numbered` or `published`, not only `published`: today's builder numbers + fresh bundle versions without publishing them (the late publish finds no digest), so a fill from `published` alone + would number again below what the builder already said (mesh-config/tools: `published` 0.1.0, numbered up to 0.1.14), + and one version would name two contents in the builder's log, its conditions and the catalog.