From d50a593d68d8741196fcace7a2da1396bf5300c5 Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 11 Nov 2026 22:37:27 +0100 Subject: [PATCH] Answer A-46: the manifest versions come from builder_versions now Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md index fa7fe896..94141c57 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md @@ -175,3 +175,8 @@ names the principle that settles it, and is cited as "design 47 G A-n". (`SeatPublish`, its subscription); the keeper's process does the work that needs the bus and the files (taking, restoring, removing), handed over and answered through the bus module's own `requests` record, as the bundle hands the keeper its requests today. Where §681 says "the keeper's process serves", read "the bus module serves". +- **A-46** (§368, §372, §411; principle 7) The `version` G's change writes into each manifest is read once now from the + same source §372 fills from: the highest `published` version over the module's artifacts in the builder's + `versions` (`builder_versions`), as its MAJOR.MINOR (mesh-sdk `0.1`), and `0.1` for a module with none published. + The developer reads it through `builder_versions` and writes it into every manifest of every repository in the + group, one commit per repository, listing the values in the commit.