Repository navigation
Mru Field 0.2.0: staged updates
Staged updates (docs/spec.md, section 10). A new build of the task comes in one slot at a time, and the old build checks every delivered output until the last switch. Until then, one fault of a slot on the new build takes it out of every slot and starts the old build there again.
On the bench (Apple M4, 5,000 cycles per run, scripts/staged.sh, docs/results/2026-11-14-darwin-arm64/staged):
- All at once, a build that crashes or hangs on cycle 500 halts the run on cycle 500. A build that is wrong from cycle 500 delivers 4,501 wrong outputs, and nothing flags them.
- By staged update, every bad build was rejected on the cycle its bug first showed, with 0 wrong outputs and 3 replicas alive.
- Limit: a bug that first shows after the last switch gets through. The new build must give the same outputs as the old one.
The decision rule is the quorum crate from mruspace/flight v0.4.0, unchanged. Bench only: not on a board in a system, and not qualification evidence. See CHANGELOG.md.