| Filename | Latest commit message | Latest commit date |
|---|---|---|
9258a0739f
The apps branch's documents join the version contract. The answer layer's documents (wai.quantum.answer/1: an answer read, carried out, a seal's request and result, a stored answer checked), described as a draft whose form may change before the extension settles; a correctness record and its corpus (wai.quantum.telemetry/1); the views page's manifest (wai.quantum.views-bundle/1); and the command line's harness report, corpus and token counts (wai.quantum.eval-report/1, eval-answers/1, token-cost/1). The engine's test holds every answer of the layer's conformance set (read, carried out, half arrived, and stored and verified), records, the corpus and the committed manifest to them; the eval tests hold a scripted run's report, a model server's, the corpus and the committed token counts; check_schemas.py holds the committed documents too. The tool and diagnostic schemas take the answer layer's outcomes, dropped and defaulted. The result view's own tool, poll_quantum_job, listed only to a host that draws views, answers to the job's schema, and the strict test holds it. The basis rename reaches the views: a compile's words and its view name the gate set by its basis (both read the certificate's old target), and a test in each holds it. The service's job summary now lives in engine::views (the apps branch moved it there); it carries the durable branch's set summary and the processor packages' energy wording with it. The answer set's stored seal was made at 0.6.16; the values it seals name their engine, so it is written again at 0.7.0 (WAI_ANSWER_BUNDLE_WRITE=1). The views crate's lock moves to wai-quantum 0.7.0. Co-Authored-By: Claude Opus 5.5 <[email protected]> |
||
| .. | ||
| cases | ||
| bundle.json | ||
| manifest.json | ||
| README.md | ||
Answer conformance
Answers in the answer view layer (quantum-answers.md,
wai_quantum::engine::answer), each with what the layer must make of it.
| Path | What |
|---|---|
cases/*.wqa |
The answers: a program, a sample, a verdict and a seal; an intent named by a reference program; the equivalence ladder; an intent that fails; expectation values, amplitudes and a Bloch vector; an engine call named apart from its view; no root; and one case for each code of the layer (J100 to J112) and for a program the reader refuses (Q103). bell-crlf is bell with CRLF line ends. bell-stored is bell with the receipt marker its seal gives under the key whose seed is 32 bytes of 3, and bell-stored-changed the same with one sample's shots changed. |
manifest.json |
Each case: its file, what it covers, and what it must give (the manifest's expect says what each field means). |
bundle.json |
The manifest's cases with every answer inline, for builds that read no files. |
A case is held to the codes of its errors (the diagnostics whose outcome is
dropped or refused, the ones a model is sent back) and of its warnings, in
the order of their lines; to its root; and to the order its views are drawn
in. A case with run has its views carried out on the engine and held to what
they show: a sample's total and its outcomes, a verdict's level and whether it
holds, an equivalence's decision, expectation values, a Bloch vector, the
names a seal covers and its receipt. A stored case's receipt is checked by
running the answer again: the engine is deterministic, so the same answer
gives the same sealed bytes on every build, and a changed one does not verify.
Native
cd wai/wai-quantum
cargo test --release --features full --test answer_conformance
Two tests: every case against its manifest, and the bundle (and the stored cases) held equal to the files. After changing a case or the manifest, write them:
WAI_ANSWER_BUNDLE_WRITE=1 cargo test --release --features full --test answer_conformance the_bundle_is_the_corpus
WASI (the edge)
CARGO_TARGET_WASM32_WASIP2_RUNNER=wasmtime \
cargo test --target wasm32-wasip2 --features full --test answer_conformance
Browser
wai-web's wasm32 tests (--features quantum_engine, under
wasm-bindgen-test-runner) read every case of the bundle with
engine_answer_parse and verify the stored cases with engine_answer_verify.
CI: wai-quantum-verdict.yml (native and wasm32-wasip2) and
wai-web-wasm.yml (the browser build).