open-standards/wai/byte-exact-conformance
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Transaction Science d14f583d92 Cargo: no minimum-supported-version floor, because the policy is latest stable
The repository tracks the latest stable Rust, pinned at the root. A
`rust-version` key states a *floor* -- the oldest toolchain a crate supports --
which is a different promise, and one this repository does not make. It also
said 1.97 while the pin was 1.98.0 and nothing verified it, so it was a claim in
the wrong direction and unchecked in both.

So it goes, everywhere:

    59  rust-version = "1.97"            (workspace and package declarations)
   417  rust-version.workspace = true    (members inheriting them)
   476  files, 476 deletions, 0 insertions

The 417 are why this is not the sixty-file change it looks like from a grep for
the value. A member inheriting a key that no longer exists does not fall back to
a default -- its manifest stops resolving. Removing the declarations without the
inherits would have broken every workspace that has members.

Deliberately untouched: `joule-code-rs/vendor/wtransport/Cargo.toml`. That is a
vendored third-party crate declaring a floor about itself, not about us, and our
pin is above it. Editing vendored source to satisfy our own policy would make
the copy diverge from upstream for no benefit.

Verified rather than assumed:

- all 493 `Cargo.toml` files in the tree parse (`tomllib`)
- `cargo metadata --no-deps --locked` resolves on `joule-code-rs`, `wai-rs`,
  `openpay`, `mesh-rs`, `sandbox-rs` and `jcp-rs` -- the check that actually
  exercises workspace inheritance, which a TOML parse does not
- no `Cargo.lock` changed; `rust-version` is not lockfile state

`wai/wai-verify/Cargo.toml` already carried a comment saying it omits
`rust-version` on purpose, so this makes the rest of the tree agree with the one
crate that had already decided.

What this gives up, stated plainly: cargo can no longer greet an older
toolchain with "requires rustc 1.97" and will instead fail wherever the code
first needs something newer. That is the cost of not maintaining a floor, and
it is the right cost when the floor was fiction.

Co-Authored-By: Claude Opus 5 <[email protected]>
2026-11-03 17:42:20 -05:00
..
src WIV1 and WIR1 gate 5 (WIP, committed before running): the 32-bit form behind a feature, held to the exact form 2026-10-17 11:28:23 -04:00
Cargo.lock D2c M1 gate 2: int_synth's decode through its lowering equals every golden 2026-10-13 02:50:33 -04:00
Cargo.toml Cargo: no minimum-supported-version floor, because the policy is latest stable 2026-11-03 17:42:20 -05:00
README.md wai: every corpus states the provenance of its content 2026-10-07 10:09:21 -04:00

byte-exact-conformance — cross-architecture byte equality

A crate that compiles WAI's pure-integer decode paths (the rANS entropy coder and the integer fixed-point syntheses, #[path]-included from wai-rs) without the system codec libraries, so the byte-equality matrices (.github/workflows/wai-byte-equality.yml, and cross-arch byte-equality in wai-conformance.yml) run them on every OS and architecture. cargo test --release here decodes the committed vectors and the staged-delivery corpus to the goldens in src/*_golden.rs, generated once on a reference machine, and must match them on every machine.

Provenance. The goldens are digests of decodes of the vectors under ../wai-rs/tests/vectors/ and of the staged-delivery corpus; that directory's README states each vector's provenance. Among them, the int_video half-pel clip (video_real) is not generated content (see there).