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
2026-11-13 13:05:30 +01:00
parent 5dee91703f
commit 258de07806
1 changed files with 4 additions and 0 deletions
@@ -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).