| Filename | Latest commit message | Latest commit date |
|---|---|---|
b894f1bbc5
The course's documents join the version contract. The course as kept and as served (wai.quantum.course/1) and each exercise (wai.quantum.exercise/1) move from course/schema/ to the crate's schemas/, named and versioned as the rest; a check, a lesson as served and a hint are wai.quantum.course-check/1, and a check now names its engine beside its schema; the command line's progress file is wai.quantum.learn-progress/1. The engine's test holds the course, every exercise, every lesson in each locale and a check and hint of some to them; the learn test holds the progress file; the contract workflow requires both, and the eval and lease tests, by name, and runs when the answer and eval sets its tests read change. The docs runner reads every page the branches added: the error-correction page, the version policy, the deprecations page, the service's self-hosting, scheduler and provenance pages, and the views' README. Each block the other branches wrote either runs or says why it cannot (a sweep fixture added), and the job service it starts keeps its store in its scratch. The crate's README names wai-quantum 0.7. The Chinese READMEs hold the English pages' code again: the sections for error correction, sets and sweeps, the service's dry runs, the scheduler, scoring a model, the answer layer, views and versions are translated, and the compile pages name the gate set basis. The command line's Chinese words cover task, qec, eval and version, and submit as it reads now. The documentation index links the policy, the deprecations, the error-correction page and the service's pages in both languages. The policy lists every schema file and says the answer layer is a draft outside its promise. The 0.7.0 heading names what the four branches bring. The views page bundles the Studio components that now read their words through the locale module; build-views.mjs gives it the English words alone, so no other language's words reach a host. The result parts the Studio and the views share read their words through it too, so the Studio's result pane stays translated, its English unchanged. Co-Authored-By: Claude Opus 5.5 <[email protected]> |
||
| .. | ||
| compiler.md | ||
| estimate.md | ||
| job-refusals.md | ||
| qasm-diagnostics.md | ||
| qasm-feature-matrix.md | ||
| qec.md | ||
| README.md | ||
| README.zh-CN.md | ||
| verdicts.md | ||
WAI Quantum documentation
Every command and code snippet on these pages runs in CI, and its output is checked against the real output or its receipt (below). A page that cannot run one says why.
Start here
- Learn: the circuits course, from a first circuit
through superposition, entanglement, interference, the standard algorithms,
noise and its mitigation, error correction and fault tolerance to resource
estimates. Each exercise is checked by the engine. It runs in the Studio and
on the command line (
wai-quantum learn), in English and in Simplified Chinese. Beside it, Quantum, reconsidered, a seven-module course on interference and learning, runs in the browser at https://wai.transaction.science/quantum-learn. - The command line:
wai-quantum: run, check, draw, compile and estimate programs, verify receipts, and serve the tools to agents. - In the browser and on the desktop: the Studio and the desktop app.
- From Python:
wai_quantum.
The engine and its reference pages
- The crate: the simulator, the operational layer, the research tools and the receipts.
- Verdicts: how far the engine checked an answer, the intents and the repairs.
- The compiler: the passes, the ε budget and the certificate.
- Resource estimates: every number of an estimate and what it assumes.
- The reader's diagnostics and what it does with each construct.
- The job layer's refusal codes.
- Error correction and mitigation: codes with their certified distances, the decoders, thresholds, and mitigation in a job.
Other surfaces
- The job service, over HTTP and MCP: running it yourself, as a batch scheduler's resource, and what a result's provenance records.
- Views inside agent hosts: the engine inside them.
- The answer view layer, a draft extension: its specification.
- Editors: the language server, the debugger and the formatter.
- Your own hardware and the provider crate.
- The workbench's specifications.
- For agents: the Agent Skill
and
llms.txt, generated from the servers' own tool lists.
Changes between versions
- The changelog:
wai/CHANGELOG.md. - What is stable, for how long, and how a change is announced, the schemas of every document included: the version policy.
- Each item deprecated, the version that deprecated it and its replacement: the deprecations page.
In other languages
Simplified Chinese: this index, the
command line's README, the
Studio's, the
Python package's, the
crate's, the course, the Studio's interface, and the
command line's own words (--lang zh-CN, or as LANG says). Each is a
machine-assisted translation, marked so, to be reviewed by a fluent reader.
How these pages are checked
wai/tools/quantum-docs/check_docs.py reads every page named in its
docs.json. It runs each shell block marked runnable in a scratch
directory with the command line built from this checkout, runs the Python
blocks against the package and builds the Rust ones, and holds each shown
output to the real one. It verifies every receipt a block writes with
wai-quantum verify. A block that cannot run here (one that needs an
account, a server that does not return, or data the repository does not
hold) says so in its info string, and its commands must still name commands
and flags that exist. Every wai-quantum … in the prose must name a real
command, every relative link must reach a file, and every dependency a page
shows must be one this repository's version satisfies. A translation must
hold the same code as its English page. .github/workflows/wai-quantum-docs.yml
runs it, with the course's tests and the locale checks.