Exact

Exact Union RegExp

Repository files (latest commit first)

Filename	Latest commit message	Latest commit date
Transaction Science 75898a5b97 quantum-ops: the encoding in the text, four more records registered, and an unmetered form that never reads zero joules ... quantum-ops named its records' fields and deferred everything else to the reference, so no verifier could be written from the text, and it allowed `0` as the unmetered marker, which quantum-landscape and wasmQ/2 forbid. - extensions/quantum-ops.md §3, written from quantum_ops.rs and quantum_energy.rs: the primitives and their framing (§3.1), reading a receipt's JSON (§3.2), each kind's payload and Merkle leaves (§3.3), the identity (§3.4), the energy forms (§3.5), the reasons a verifier gives (§3.6), and the links and content hashes (§3.7). What is read and decides nothing is named: the written receipt_hash, a decode/compile/rearrange receipt's written merkle_root, an evidence summary (not sealed), members no text names. - Registered: wai.quantum.mitigate, .decode, .compile, .rearrange (SPEC §5, quantum-ops §1.3 to §1.6; registry.rs, the export regenerated). wai.quantum.qbom and .fabric are stated not to be part of the standard (quantum-ops §8) and stay unregistered with that reason. §5 of the text no longer names third-party tools. - The unmetered form (quantum-ops §3.5, energy-measurement §2.8): quantum_energy::Unmetered, for every Labellable family (calibration, job, mitigation, decode, compile, rearrange, circuit, phasor, sparse-Pauli, resource). Under the 0x02 domain the figure 0 is followed by tag 0 and the reason (u32 BE length, UTF-8); its JSON writes joules_micro null beside energy_unmetered. MaybeLabelled gains the variant and unmetered()/joules_micro(), the latter never Some(0); an unlabelled 0 still verifies and reads as unmetered (legacy). wai_quantum_meter and wai-quantum-serve seal unmetered runs in the new form, and serve's POST /verify verdict says why. quantum-sim's receipt text says so. - Reading tightened where the JSON showed what the seal does not say: a member named twice (sig::unique_members), a kind of another family, rounds/swaps/atoms_moved past u32 (read before as their low 32 bits), a funds_ceiling that is no count and an optional hash that is no string (each read before as none) no longer read; a str()-framed string holding U+0000 no longer verifies (two receipts could sign the same bytes). Vectors (wai/quantum-ops-conformance): 12 receipts the reference made, every kind and every energy form (the three earlier ones byte-identical), and 49 crafted by generate.py, each one defect away or one change that decides nothing, with hand-written reasons. ops_verify.py, written from §3 alone and sharing no code with the engine, gives the 12 their identities and the 49 their exact reasons; wai_quantum_ops_vectors verify gives all 61 their verdicts and stages. CI: the corpus's verify in cargo-classes as before; ops_verify.py and generate.py --check as a new independent verifier (verifiers/quantum-ops.sh). Failing first: the crafted receipts given to the reader before this change (origin/main 1f5bc7225, a scratch test over MaybeLabelled::from_json and verify) verified nine of the defects this change refuses: a member named twice (plain and escaped), a calibration whose kind is a job's, one with no kind, rounds of 2^32 + 1 sealed as 1, a funds_ceiling "50" sealed as none, a parent_receipt_hash of 0 sealed as none, and a device_id and a grant capability holding U+0000. The six crafted receipts of the unmetered form did not read there, since the form did not exist. Tested on the build host: wai-quantum --features full --lib --tests (lib 1560 passed, 26 ignored; every integration test passed, landscape_conformance's 54 among them); default features (127), quantum_ops alone (51), quantum_receipt alone (50); wai-rs with the energy-receipts workflow's feature set, --lib --bins --test video_receipt (906, 4, 15, 130); wai-rs codecs::registry (15) and `wai registry export --check`; wai-quantum-serve (12); wai-quantum-cli's test build; wai-web cargo check; wai_quantum_ops_vectors verify and ops_verify.py on the corpus; clippy: no finding on a changed file of wai-quantum, serve or the two wai-rs bins. Locally: check-wai-section-refs, check-spec-refs, check-wai-quantum-names, check-public-names --maintainer-products-only, changelog-assemble --check, check-tests-in-ci, check-wai-core-freeze, wai-conformance-lists check, check-wai-corpus-licences: clean. wai breaking against main: the two breaks the changelog entry acknowledges. quantum_ops.rs is one of the sources the wasmQ modules of record pin (quantum-conformance/wasmq/modules/modules.json): its digest is updated, and on x86_64 Linux (build.sh --check) both modules still build byte for byte as committed. Rebased on 15b7f810d: the registry export is up to date, and the registry, ops, energy, pins and sig tests, serve's tests and wai_quantum_ops_vectors verify pass again. Changelog entry: wai/changes/2026-11-10-quantum-ops-encoding-and-unmetered-form.md Co-Authored-By: Claude Opus 5.5 <[email protected]>		2026-11-10 15:30:53 -05:00
..
atom_planner.wasm	wai: wasmQ, an OpenQASM 3 program and the WebAssembly its externs call, run the same everywhere, metered and receipted	2026-11-09 13:22:09 -05:00
modules.json	quantum-ops: the encoding in the text, four more records registered, and an unmetered form that never reads zero joules	2026-11-10 15:30:53 -05:00
qldpc_decoder.wasm	wai: wasmQ, an OpenQASM 3 program and the WebAssembly its externs call, run the same everywhere, metered and receipted	2026-11-09 13:22:09 -05:00