Quantum Powerhouse

The builder

Said Mohaddes Sadeqi

I build quantum software. The numbers on this site come out of calculations that run in your browser, the research claims link to the primary sources I read, and the tools are things another engineer can install from source.

this site's sourcepytest-qequivresearch repositoryCV & contact → sadeqi.me

What I decided

  • I wrote the physics myself: a statevector and density matrix engine in TypeScript, a parameter shift VQE and Richardson extrapolated zero noise extrapolation. The browser does the computing, so nothing on the site is a recording.
  • I made the checks part of the build. CI fails if a research claim on the site drifts from the evidence record, every arcade card says what computes its numbers, and the pet cannot state a number the engine did not produce.
  • I let the research correct me. I set out to show a gap, found QUTest and Benchpress, narrowed the claim in public, and then built the tool the remaining gap called for.

How I work

Rules first, then code: nothing fake, every claim sourced, tests before merge. Unit and end to end suites run on every push, the research record is cross checked in CI, and I only cite sources I opened. The physics and the research judgment are mine. Ask me why the parameter shift rule gives an exact gradient, or why the pet uses a semi implicit Euler integrator.

By the numbers

26
interactive quantum games & labs
14
research claims with verdicts
22
prior art systems inspected
3
SDKs bridged by pytest-qequiv

Repository activity: live from GitHub

Counts are capped at 100 per repository by the API page size.

What's next

  • · Run the CHSH experiment on real IBM hardware and publish the device column.
  • · Archive the research record with a DOI and submit the gap analysis as a short paper.
  • · Push the engine past 16 qubits with workers/WebGPU and benchmark it in public.

Start with the arcade, read the research, then poke the pet.