Answer A-474: a module's tests read nothing outside their module

This commit is contained in:
2026-11-17 15:10:52 +01:00
parent 284c32062e
commit 16316da868
@@ -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.