Answer A-477a: the build node's guard compares the recipe only when the ask names one

This commit is contained in:
2026-11-17 20:58:49 +01:00
parent d757200010
commit b27004f74d
@@ -1886,3 +1886,9 @@ the principle that settles it, cited as "design 47 G A-n".
on a real difference. (Live, 2026-11-17 20:50 and 20:56: every test step of main.1013.feh was declined by every
build node, "the ask is for go1.27 (recipe ) and this node builds with go1.27 (recipe 74744709d277ded9)", because
the runner left the recipe out; the asks were taken and never run.)
- **A-477a** (withdraws A-477; A-104 stands; A-471; principles 7 and 3) The runner cannot name the recipe: the
toolchain-agreed event carries none (§574, §472). So the build node's guard compares what the ask names: the
language version always, the recipe only when the ask names one. An ask naming no recipe is taken by any node on
the agreed language version; a node sits out only on a real difference. (From the develop of A-477: the agreement
event has no recipe field; adding one would change the contract, the builder and the runner for what the guard
settles in one place.)