# 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**.

`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

```sh
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:

```sh
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

```sh
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`.