01
Start with the public decision
Every program names the decision it could inform: a water permit, a battery chemistry, a procurement rule, a classroom. If we cannot name one, the project is not ready.
Research / 2026
We work on the parts of quantum computing that must be solved before the technology can serve anyone: error correction, honest simulation, field-ready sensing, and the shared infrastructure that keeps it open.
How we choose problems
Every program has to pass four tests: the physics has to be interesting, the classical alternative has to be considered honestly, the result has to be publishable, and someone outside the lab has to be able to use it.
We publish our failures alongside our results. If a program cannot survive that, it should not be a program.
Program 01 / Hardware / theory
Can we make a quantum computer whose errors are ordinary engineering?
A useful quantum computer cannot be a laboratory demonstration that holds coherence for a few microseconds. It has to survive thousands of hours of operation, tolerate component failures, and produce results that another group can reproduce. That is an architecture problem as much as a physics problem.
Our group works across the stack: superconducting transmon modules, cryogenic control and readout, quantum low-density parity-check codes, and decoders fast enough to keep up with the machine. We are particularly interested in modular designs, where many small processors are linked into a larger logical machine. Modules are easier to build, test, and replace — and they make failure modes visible.
The test of success is not a single record fidelity. It is a logical qubit whose error rate falls as the code distance grows, measured repeatedly, on hardware that a graduate student can calibrate without a specialist.
Program 02 / Algorithms / chemistry
Which materials problems are worth a quantum computer — and who needs the answer?
Quantum computers may one day calculate the behavior of electrons in materials with an accuracy that classical methods cannot reach. The operative phrase is 'may one day.' Our job is to replace that vagueness with specific claims: which molecule, which accuracy, which machine size, which cost, and which decision would change if we had the answer.
The group focuses on iron–sulfur clusters in battery electrolytes and catalysts for low-energy nitrogen fixation. Both are scientifically hard, socially consequential, and poorly served by a short-term commercial case. We work with electrochemists and grid planners to define the questions before we run the algorithms.
We publish negative results and resource estimates that make a problem look impractical. A field that only reports the promising cases is not doing science; it is doing sales.
Program 03 / Metrology / field science
What if the most useful quantum technology is a sensor that fits in a van?
Quantum sensing is often treated as the practical little sibling of quantum computing. We think it deserves the front seat. A magnetometer that can map groundwater recharge, a compact clock that keeps a grid synchronized, or a sensor that detects a contaminant at parts-per-trillion can matter to a public agency this decade, not next.
Our sensing group builds field instruments with explicit tradeoffs: sensitivity against portability, automation against repairability, and precision against the cost of calibration. We test in real conditions — on farms, in utility substations, and in partner clinics — because a sensor that only works in a basement is not yet a public capability.
Every design file, calibration routine, and failure log is released under an open hardware license. The point is not to sell instruments. The point is to lower the cost of knowing.
Program 04 / Infrastructure / policy
Who gets to use quantum computing, and on what terms?
Technology does not become public infrastructure by accident. It becomes public infrastructure when the tools are inspectable, the standards are open, the workforce is broad, and public money comes with public conditions. This program works on all four.
We maintain Kestrel, our open control stack; publish benchmark suites that compare machines on tasks rather than marketing claims; run Quantum Classroom for schools and teachers; and advise public agencies on procurement that avoids lock-in. None of this is a side project. It is how the lab stays accountable to the public that funds it.
We also study the lab itself. Our annual public-benefit review asks which of our results were used, by whom, and whether the benefits reached people who did not pay for the research. The answers are sometimes uncomfortable, which is the point.
05 / Method
01
Every program names the decision it could inform: a water permit, a battery chemistry, a procurement rule, a classroom. If we cannot name one, the project is not ready.
02
Negative results, noise models, calibration drift, and cost overruns belong in the record. They are often more useful to another lab than the headline.
03
A tool is not done when its authors can run it. It is done when a student at another institution can install it, break it, and fix it without emailing us.
04
We do not accept exclusive licenses, classified work, or publication vetoes. Funding that requires those terms is not funding we can take.
06 / Facilities
01
Dilution refrigerator
A custom Bluefors-style system with vibration isolation, a 48-line wiring loom, and a base temperature of 7.8 mK. Named after a small falcon that nests on the building.
02
Instrumentation
A shared machine shop, vacuum bench, and cryogenic test stand. Every fixture is designed to be rebuilt from published drawings.
03
Sensing
A vibration-isolated table for NV-diamond and squeezed-light experiments, plus a field-test locker that can be packed into a van in under an hour.
04
Everyone
A small library and the best whiteboard in the building. Also where Public Lab Night begins, every second Thursday.
07 / The people
Work with us
We collaborate with public agencies, universities, and community organizations. We do not accept exclusive licenses or publication vetoes.