From 258de078064c39ef05ecb5a0f702b313ddc4b31a Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 13 Nov 2026 13:05:30 +0100 Subject: [PATCH] Answer A-351: the filled edges count the builder's numbers too; no digest where the builder kept none 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 b0073858..5c6a2dff 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 @@ -707,3 +707,7 @@ the principle that settles it, cited as "design 47 G A-n". 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. +- **A-351** (sharpens A-350; principles 2 and 7) The filled edges of kinds 1 and 3 take the same rule: the dependency's + version the builder gave a number, numbered or published, since that is the version the module was built against; a + filled version or edge whose number the builder kept no digest for carries none (the fill needs only the number to + count above it, and a filled edge is stale until the module's next build).