7 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	792352dfad	Read a rebuild of an unchanged source as no move, whatever image digest it made (hq issue 280) ... An image is not byte-reproducible, so ADR 0236's 'same artifacts is no move' never held for one: a catalogue merge that did not touch the bus rebuilt it, and every send to the control node waited for a planned bus upgrade. The builder now records a source fingerprint per build (module tree, context trees, bases and toolchains by digest). A rebuild with the fingerprint of the build it repeats is registered with that build's artifacts, handed to modules standing on it, holds no push, demands no bus step, and a plan sends and gates nothing for it. Identical artifacts remain a second way to be no move.	2026-10-06 22:09:11 +02:00
jochen	2bfa6ae4a0	No build reaches a machine without a gate; a release plan walks what waits (hq ADR 0236) ... A send carries the machine's whole declaration, so at the switch to roll the next send of anything would have carried the old default's backlog, unjudged, to every machine. A gated send now carries and judges everything waiting on its machine; every other send is refused or leaves the machine; a release plan walks what waits one machine at a time, the control node last, and one that fails holds the next until a person releases it.	2026-10-06 19:14:25 +02:00
jochen	41f7b2c152	Tell a rebuild that changes nothing by its artifacts and its manifest (hq ADR 0236)	2026-10-06 18:56:54 +02:00
jochen	37229b4db5	Refuse every send that would replace the bus outside its planned step (hq ADR 0236) ... A plan's send to the bus's machine for another module carried the bus's new build and restarted it under every machine with nobody asking (2026-10-06). The guard is in the one send everything uses; only the bus step passes it. A rebuild that made the same artifacts is no move.	2026-10-06 18:56:54 +02:00
jochen	d7bf1bae83	Name the decision this builds: hq ADR 0236 (0235 is the bus's snapshot)	2026-10-06 18:56:54 +02:00
jochen	c6f3d8cdfa	Take the bus's snapshot through its machine's backup holder before the planned step (hq ADR 0235, 0236)	2026-10-06 18:56:54 +02:00
jochen	d9289ef6d4	Gate a release plan's first machine and roll a failed build back there (hq ADR 0236) ... A build that reported applied was sent everywhere; one that then did nothing, served no tools or broke its machine's word reached every machine. Now the first machine is judged by the component's health (the core's definitions, as doctor probes H-*, or a module's own) three times over two minutes within ten; a failing gate puts the previous build back there once, marks the build, and says it as a condition and an event. Upgrades roll out by default; the bus is a planned step; a module deleted at its source is not built (the public-acme plan failure).	2026-10-06 18:56:54 +02:00