| Filename | Latest commit message | Latest commit date |
|---|---|---|
3fac029a71
Each *-conformance/README.md now has a line that begins **Provenance.**: the generator that writes the corpus and its input, and for an input not generated here its source and licence. OER/2's corpus is settled and left as it is. byte-exact-conformance and quantum-ops-conformance get a README. wai-rs/tests/vectors/README.md gives a row per vector directory. Where the staged-delivery, staged-measurement and telemetry READMEs called their content "synthetic", that sentence is now their provenance line. Two vectors are recorded as not generated, from the provenance audit: int_video's video_real (a pan over a third-party picture) and neural-conformance's photo (a third-party picture, with a decoder trained on unrecorded images). Their lines say so and that they are to be replaced; the photo bullet no longer names the picture's source product. tests/corpus_provenance.rs requires the line in every corpus and a row for every vector directory; CI runs it with the carriage tests. CONTRIBUTING states the rule: corpus content is generated here, or recorded with a licence that permits redistribution, and a word like "synthetic" is not a provenance line. Co-Authored-By: Claude Opus 5.5 <[email protected]> |
||
| .. | ||
| vectors | ||
| browser_verify.mjs | ||
| expected_hashes.json | ||
| README.md | ||
quantum-conformance
Statevector-equivalence for the wai.quantum.circuit extension: given the same
WQC circuit, a conforming sink MUST reconstruct the identical fixed-point
statevector — hash equality, no tolerance.
Provenance. Generated here by wai_quantum_vectors from circuits authored in code. No media.
vectors/*.wqc plus expected_hashes.json are the pinned corpus. They are the
one reference all three surfaces are checked against, rather than being checked
against each other.
Native
cargo build --release --no-default-features --features quantum --bin wai_quantum_vectors
./target/release/wai_quantum_vectors verify wai/quantum-conformance
WASI (the edge)
Same binary, same source, different architecture:
cargo build --release --target wasm32-wasip2 --no-default-features --features quantum \
--bin wai_quantum_vectors
wasmtime run --dir wai/quantum-conformance::/corpus \
target/wasm32-wasip2/release/wai_quantum_vectors.wasm verify /corpus
Browser
node wai/quantum-conformance/browser_verify.mjs [path/to/quantum-ml/pkg]
Drives the deployed wasm-bindgen bundle in headless Chromium. Note that
statevector_hash_hex() is empty until run() is called — the circuit is built
eagerly, the state is not.
Scope
The corpus covers the byte-exact dyadic core, where hash equality is the right
bar. The floating-point layers (quantum_source, quantum_channel) are held to
exact IEEE-754 bits by unit tests instead, since they have no WQC circuit to
pin — see entropy_is_bit_identical_across_architectures.