Repository navigation
v0.11.0
v0.11.0
Pre-alpha: no compatibility is kept; deletions are outright and the durable formats refuse the files the previous release wrote.
This is the consolidated movement since v0.9.0: the documentation is restructured into one place to look each, every reference the code and the documents make is mechanically resolved, and the leader-assignment question is settled in the protocol rather than in the operator's hands.
The protocol
- NOMINATE leader assignment across reconfiguration (#102): the leader of a view is a ballot outcome, and a reconfiguration that changes the positive-weight sequence would move the arithmetic mid-plan. The NOMINATE letter is a view increment carried as a compare-and-swap at a committed slot: the bump publishes the bumped ballot as current and retained on the same transition, so every §1.3 relation holds at every instant, the leader the old arithmetic elected is the leader the new arithmetic re-elects, and crash mid-transition is a no-op. The weighted solver emits the wrap-only nominations; the era-only jump is admitted and proven safe (ViewJump), so the scaling steps need no rider (#103, #105).
- The ABDICATE command is deleted (#106): a leader that must leave issues a StartViewChange to a higher view and shuts down.
- The drop discipline is codified by name (#108): the frontier clause and the view clause, each refusal named in the durability model and pinned in the public interface tests.
The verification
- The uVRR compliance suite (#94): a language-agnostic corpus of state x message -> state' + outputs cases, one JSON case per transition over the abstract host interface, 73 cases in ten families seeded per Lean rung, each case naming its theorem; the reference runner executes the corpus through the crate's public sans-I/O interface and the exporter's regeneration is a CI gate.
- The flavoured-timeout model (#100): the state enum and the timeout enum are closed, the policy matcher is exhaustive over every pair with no default arm, opinions are the legal family with Sorry carrying the recorded runbook for the unflushed stop, and the timeout-policy tool prints the matcher's answer as living documentation.
- The verification gate runs the Lean lane: formal/uvrr-lean is elaborated on every push (#113).
- The documentation reference gate: every doc comment's references are mechanically resolved — cited documents exist, sections name real headings, decision identifiers and rules and citations resolve — and rustdoc's intra-doc links are hard errors. The external works are cited from one references file. A comment that lies about the section it cites is now a failing build.
The durability boundary
- The boot gate and the termination obligations are stated in one document, uvrr-io-obligations.md, with the host notes pointing at it as the normative source; the compliance suite is the host's artefact, uvrr-host-compliance.md; the reconfiguration rules, reincarnation, rejoin gossip and witnesses, the weighted solver, and the NOMINATE letter are consolidated into uvrr-protocols.md.
- Liveness is stated as host documentation (#101): the resend, the heartbeat, and the retransmit are suggestions the host weighs, never obligations the core prescribes.
Identity and naming
- The (era, view) pair is named Ballot across the crate, the tests, the documents, and the Lean formalisation: the code, the proofs, and the paper speak one vocabulary.
- The crate name is uvrr everywhere: the lib target the hosts dlopen is libuvrr, the environment variable is MAELSTROM_UVRR_STATE_DIR (#95).
- Release tags correspond to the manifest version, verified before the build lanes start (#97).
Harness
- The gate-classification flake is dead (#115, #116): gate roots are unique per process, so two harness binaries cannot collide on the same directory.
- Cargo.lock is committed as policy; the maelstrom adapter is compile-gated so the default test lane never boots the harness; CI runs the fast lane then the full lane.