From 16316da868f0f434a61db1bb9a0bf383af0e5dc1 Mon Sep 17 00:00:00 2001 From: jochen Date: Tue, 17 Nov 2026 15:10:52 +0100 Subject: [PATCH] Answer A-474: a module's tests read nothing outside their module --- 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 5431d63c..094109e9 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 @@ -1833,3 +1833,7 @@ the principle that settles it, cited as "design 47 G A-n". reservation's completion (built-at set, every artifact's digest known) queues that version at the holder of each artifact's registry seat, as a holder's `running` does today; a holder that refuses or does not answer leaves the version in version-unreleased with its words. `builder_publish_again` stays the hand recovery. +- **A-474** (G-24 tests on main, mesh-build-go TestAComposeAskIsBuiltOnceAndAnsweredOnTheBus; principles 10 and 9) A + pipeline's test step places no other repository beside the one it tests, and a module's tests read nothing outside + their module: a test that needs a program of another module builds a stand-in from its own testdata (a fixture + composer that answers as the composer's contract says), never that module's source tree.