Quantuva is not a black box — the code, the notes, and the papers are all public, and the people who run the experiments on real hardware are the ones who catch what we got wrong. There are several ways in.
Found a bug, or a place where the simulator and the hardware disagree? Open an issue with a minimal circuit that reproduces it — that's usually all we need.
GitHub issues →A faster simulator kernel, a better routing pass, a clearer error message. Small, well-tested pull requests are the easiest to review and merge.
Contribution guide →Every publication ships with the code and data that produced its figures. Try to break a result — that's how we know which ones hold.
Papers →The community runs on a single rule: critique the argument, not the person. We discuss circuits and estimators with the same care whether the author is a first-time contributor or a maintainer. Abusive behavior ends the conversation, not the science.
If Quantuva contributed to a result you're publishing, cite the software. Here's a BibTeX entry to start from.