logo
Kurashizu Blogwhere ideas flow
  • Home
  • News
  • Blog
  • About
  • Home
  • News
  • Blog
  • About

© 2026 Kurashizu. All rights reserved.

Admin·New Post·Service Status
Powered by Cloudflare·31.10.26
← Back to news

I'm teaching an introductory 12 week course on Quantum Oracle Engineering

Original article
shukla.io|33 points|10 comments|by BinRoo|Sep 6, 2026

Quantum Oracle Engineering: A Programmer’s Guide to Building the Right Oracle

Venue: IEEE Quantum Week 2026 (QCE26) | Toronto, Canada

Many claims regarding quantum speedups are based on "paper oracles"—theoretical constructs that don't actually exist in hardware. This 12-week introductory course focuses on the craft of constructing functional quantum circuits from the ground up.

🛠️ The Hardware Paradigm

We must distinguish between the roles of different processing units:

  • CPU: General purpose.
  • GPU: Parallel throughput.
  • QPU: Designed to provide fewer samples for average queries rather than raw speed.

When evaluating a quantum advantage, we must ask three critical questions:

  1. What is the task randomness?
  2. What is the required precision?
  3. What is the actual oracle cost?

Warning: Applying Grover's algorithm to a database often fails because the cost of data loading outweighs the search speedup.


📅 Course Curriculum

The following lessons are released as they are published.

Phase 1: The Fundamentals of Speedup

DateLessonFocusKey Concepts
Sept 802Monte Carlo SpeedupQuery count≠Runtime\text{Query count} \neq \text{Runtime}Query count=Runtime. Using Amplitude Estimation to read the payoff qubit's angle to precision ϵ\epsilonϵ.
Sept 1503"Ship It" (The Contract)Defining the board, moves, and randomness. Implementing a d20 as a 5-bit comparison.
Sept 2204Reversible DesignUsing "shadow boards" to maintain state; in-place updates and erasing move-selection scratch.

Phase 2: Resource Management

  • Sept 29 (Lesson 05): Garbage Collection Reversible circuits cannot simply "delete" data; entangled scratch space destroys interference. We employ Bennett's Method:

    Note: The inverse pass must receive the exact same inputs as the forward pass.

  • Oct 6 (Lesson 06): Measurement as Erasure While textbooks discourage mid-circuit measurement, compilers use it to reclaim qubits.

    • Gidney’s AND†\text{AND}^\daggerAND†: Replaces a Toffoli gate with an X-basis measurement.
    • Benefit: Reduces T-gate count for adders by half.
    • Condition: Safe only when scratch holds a basis function of the data.
  • Oct 13 (Lesson 07): Calling Conventions Managing scratch space requires strict contracts. We categorize scratch into three types:

    1. Clean
    2. Borrowed
    3. Conditionally Clean

    We use Hoare contracts over subspaces to ensure boundary restoration. For example, a 12-bit oracle might be optimized from 20 qubits down to 13.


Phase 3: Verification and Theory

Oct 20 (Lesson 08): Proof-Carrying Circuits Truth tables are blind to phase. Full-basis checking is prohibitively expensive at O(2n)\mathcal{O}(2^n)O(2n). Instead, we use:

  • Lean Kernels: To replay certificates.
  • Theorem Families: Checking one theorem per family in milliseconds rather than exponential gate-by-gate verification.

Oct 27 (Lesson 09): The Locus of Quantumness Where does the "quantum" actually reside? If a process is just step-by-step, classical bits suffice. The quantum advantage lives in the memory between steps.

  • Example: The SHIFTS channel (1 qubit in →\rightarrow→ 2 qubits out).

Nov 3 (Lesson 10): Memory Scaling Quantum memory does not amortize. For nnn copies, the requirement is either zero or linear—nothing in between.

  • SHIFTS Theorem: Requires at least 0.030.030.03 qubits per copy.

Nov 10 (Lesson 11): Black-Box Testing Don't trust the hardware; test it. A device with insufficient memory will fail a single-qubit measurement test with exponential probability: P(pass)≤too little memoryP(\text{pass}) \leq \text{too little memory}P(pass)≤too little memory


Phase 4: The Final Audit

Nov 17 (Lesson 12): Auditing Claims In the AI era, there is a false assumption that compute can close any gap. We encounter "The Wall":

  • Query counts as runtimes →\rightarrow→ Ignore parallelism.
  • Solver randomness →\rightarrow→ Confused with task randomness.
  • Hidden Costs: "Assume oracle access" often hides the hardest part of the problem.

Audit Checklist for Headline Claims:

  • Is the gap irreducible or just a result of weak baselines?
  • Is the oracle cost explicitly calculated?
  • Is the precision ϵ\epsilonϵ realistic for the hardware?

🎓 Live Tutorial Agenda

Target Audience: Researchers and practitioners proficient in qubits, controlled gates, and circuit diagrams.

  • Session 1 (90 min): Lessons 1 & 2 →\rightarrow→ Identifying problems worth accelerating.
  • Session 2 (90 min): Lessons 3 & 4 →\rightarrow→ Constructing the rollout oracle.

Example Oracle Contract (Conceptual):

def quantum_oracle_contract(board, moves, randomness):
    # 1. Apply uniform move choice over legal cells
    # 2. Roll the d20 (5-bit comparison)
    # 3. Update shadow board
    # 4. Flip payoff qubit if win condition met
    return payoff_qubit

Course Art Placeholder

Instructor: Nishant Shukla Artwork: Lazybuns