Answer A-471: a toolchain is agreed by its language version, the patch not counted

This commit is contained in:
2026-11-17 14:47:57 +01:00
parent 304ae5a5fb
commit 68148d886b
@@ -1811,3 +1811,10 @@ the principle that settles it, cited as "design 47 G A-n".
machine not composing keeps that module held and blamed, and the search goes on against the retry's problem within
the same `blame_tries`, until the machine composes or no hold changes it: every module the candidate's composition
refuses is blamed, never only the first.
- **A-471** (the operator, 2026-11-17 ~14:40: "the patch version of Go doesn't/shouldn't matter for the builder to accept
builds, so 1.27 is fine"; principle 7: agreeing on the patch serves no need) A toolchain is agreed, reported and named by its language version alone: Go by
its major.minor (`go1.27`), Node by its major.minor (`v26.13`), with the recipe beside it. A build node whose installed
patch differs takes the ask; builders agree when language version and recipe agree. The one comparison lives in
mesh-delivery-sdk `buildstep` (the agreement every reader uses: indexer, builder, checker, a build node's step guard,
the composer); a fingerprint names the language version, so every module's fingerprint changes once. The first bugfix
through a working pipeline (the operator, 2026-11-17).