From 927ff5184256e2ecf58df9ad7d3d66d0d9493bde Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 11 Nov 2026 22:45:11 +0100 Subject: [PATCH] Answer A-54 to A-56: distribution's old stream name, the builder's setting, mesh TS packages in the locks check Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md | 8 ++++++++ 1 file changed, 8 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 77509097..7d935351 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 @@ -210,3 +210,11 @@ names the principle that settles it, and is cited as "design 47 G A-n". - **A-53** (§681, ADR 0675; principles 3 and 7) A snapshot's record never ages out before its file: the bus module's `requests` state keeps its records 91 days (one more than `snapshot-keep-days`), and the keeper removes a snapshot's record together with its file at expiry, so no file is left without a record and no record without its file. +- **A-54** (§584, ADR 0363; principle 8) Distribution's old-section stream takes the old form's name beside + `-findings`: `distribution-events`, never the mesh's own `events`. +- **A-55** (§672, ADR 0348 §5; principle 7) The builder's `toolchain-wait-minutes` reaches it the way the mesh fills a + part's settings, as mesh-conditions reads its own (the runtime's settings read at start, the manifest marking it + `runtime`), never through the process's environment. +- **A-56** (ADR 0573 §2, §4; principle 5, everything ships the same way) The locks check treats every `@novox/mesh-*` + package as it treats the SDK's, since the builder builds a module against the latest published version of each mesh + package as it does for Go; the order between the contracts' publish and gitea's build is the delivery plan's.