Tutorial

One path: the tutorial, then the reference, then a real design stepped instruction by instruction. Its first parts open the design tool on an exercise and check your work against the page's own verdicts; its later parts are the verified compiler, in Lean, run in this browser. Your progress is kept in this browser, and on your account when you are signed in. Open the tutorial.

The tutorial

0%of the tutorial
Your progress
Level 1 · Newcomer
0 of 311 exercises0 of 538 stars0 of 13 badges
Finish your first exercise to become an Apprentice.
Your progress is kept in this browser.
Map readerFinish Part A
Ion programmerFinish Part B
Rule keeperFinish Part R
Circuit schedulerFinish Part C
QCCD architectFinish Part D
ModellerSolve Part E's exercises
Proof checkerSolve Part F's exercises
SemanticistSolve Part G's exercises
AuditorSolve Part H's exercises
Compiler builderSolve Part I's exercises
Fault-tolerant architectSolve Part J's exercises
Tutorial completeFinish all 311 exercises
Every starEarn all 538 stars
Part A · 6 lessons · in the design tool

What you are looking at

The map you will build on: sites, junctions, segments, loops and zones, and what one move costs.

0 of 6 doneBadge: Map reader
Part B · 8 lessons · in the design tool

Programming by hand

Ions on the map: a CNOT, a Bell pair and a docked rotation, written by hand in the eleven verbs.

0 of 8 doneBadge: Ion programmer
Part R · 9 lessons · in the design tool

The rules the machine must obey

Every rule the machine obeys, broken on purpose and repaired, or the honest reason it cannot be checked here.

0 of 9 doneBadge: Rule keeper
Part C · 4 lessons · in the design tool

Circuits by hand

A syndrome round and a plaquette, scheduled by hand under all the rules, with the heat paid for.

0 of 4 doneBadge: Circuit scheduler
Part D · 4 lessons · in the design tool

Architecture decisions with the compiler

Let the compiler do it, then judge an architecture from measured numbers on the leaderboard's tasks.

0 of 4 doneBadge: QCCD architect
Part E · 4 chapters live · in Lean, in this browser

The machine as data

Devices as graphs, programmes as data, replay as a function, and the rules as statements Lean can decide.

0 of 33 exercisesBadge: Modeller
Part F · 6 chapters live · in Lean, in this browser

Certificates and the proved checker

What a certificate records, what it means for one to hold, the decision procedure that settles it, and the proof that the procedure is right.

0 of 55 exercisesBadge: Proof checker
Part G · 7 chapters live · in Lean, in this browser

Semantics: which gate the pulses make

Exact numbers, the native pulses as matrices, u3 from two pulses, CX from one entangling pulse, stabilizer tableaux, and measurement — without Mathlib.

0 of 65 exercisesBadge: Semanticist
1i−1−iω⟨a, b, c, d, k⟩(a + b·i +(c + d·i)·√2)÷ 2ᵏone spelling eachG1Exact numbersLesson F1 ended on a gap.Not started0 of 10 exercisesStart q0q1H: R, VZCX: R, MS, R, R, RG2The native pulsesA trapped-ion machine does three things to its qubits, and the compiler emits nothing else (the semantic check, check_cert, calls them NATIVE: "the pulses the hardware executes, and so the only gates the semantic half can compose").Not started0 of 10 exercisesStart VZ(φ+λ)R(θ, π/2−λ)u3(θ,φ,λ)H = VZ(π) · R(π/2, −π/2)as the h certificate's witness has itG3u3 from two pulsesEvery one-qubit gate of a circuit (h, s, t, x, a rotation) is a u3, and the compiler replaces every u3 by two native instructions: one physical pulse and one frame update.Not started0 of 9 exercisesStart q0q1MS(π/2)=e^(−iπ/4)G4CX from MSThe only entangling operation of the machine is the Mølmer-Sørensen pulse.Not started0 of 9 exercisesStart the circuitX₀ ↦ Z⊗1Z₀ ↦ X⊗XX₁ ↦ 1⊗XZ₁ ↦ Z⊗Z=the pulsesX₀ ↦ Z⊗1Z₀ ↦ X⊗XX₁ ↦ 1⊗XZ₁ ↦ Z⊗ZG5Stabilizer tableauxA matrix for n qubits has 4ⁿ entries; a BB[[144,12,12]] round has hundreds of qubits.Not started0 of 9 exercisesStart q|0⟩a readout is a CNOTq|0⟩resetCXMMCXin ordermoved earlyG6Measurement and resetA measurement is not a unitary: it reads a qubit and leaves it in the state it read.Not started0 of 10 exercisesStart = CX·(H⊗1)up to a phasetwo witnesses, composedswap_operandscheckersemanticsG7The semantic checkLesson F1 proved that the Bell certificate holds: where every ion is, cycle by cycle, and that every gate's ions are together in a trap that can gate.Not started0 of 8 exercisesStart
Part H · 4 chapters live · in Lean, in this browser

Verify the website yourself

Every compiled case this site publishes, checked by you: in the page for the small ones, with the downloadable checker for the large ones.

0 of 34 exercisesBadge: Auditor
Part I · 5 chapters live · in Lean, in this browser

Build your own verified compiler

A compiler for a chain of traps written in Lean and proved correct by construction; then a compiler in any language, validated by the checker; then the Compiler board.

0 of 45 exercisesBadge: Compiler builder
Part J · 6 chapters live · in Lean, in this browser

Gadgets and fault-tolerant architecture

Places as boxes with doors and promises; the machine's rules as propositions, and why parallel work is safe; designing a floorplan and its traffic; gates built from places and proved, including the T gadget that was not T; why a program of proved gates is the program it says; and Shor's algorithm, fault-tolerant, end to end.

0 of 48 exercisesBadge: Fault-tolerant architect

The reference

backgroundThe physics, from one trapped ion to the noise modelTraps, qubits, gates, transport, the control system, where the noise comes from and how this website simulates it. the languageEvery statement, with a running exampleThe syntax, what each statement does to the machine, what it costs, and the IR beneath it. the rulesAll 27 rules, each with a programme that passes and one that failsThe verifier's own verdicts, runnable here. compilationFrom QASM to hardware instructions, verifiedThe pipeline on a Bell pair, then every basic gate compiled, mapped, witnessed and checked. evaluationEvery metric, and the noisy circuit a run becomesSpeed, heat, hardware and the logical error rate, each a term of a language; the noise model as text; a Goal 1 entry recomputed. device languageThe architecture description languageOne document describes a machine: its trap graph, zones, wiring and the curves of its primitives. control IRTSIR — the control IRThe eleven verbs a programme is written in, and what each one costs. the rulesThe rules, and what the verifier can honestly say about eachAll 27 rules, what each one checks, and what the verifier can honestly say about it. physics and metalThe electrodes a device impliesFrom the graph to electrodes: the metal a device implies, and its design rules.

A real design

Every leaderboard entry is a worked example: the executing instruction is marked in the programme, the circuit statement it discharges beside it, and #step=N links any step. The fastest verified round of each task: