Glossary
Every technical term this platform uses, with what it means and — the part that is harder to find elsewhere — the mistake it prevents. On this subject the intuitive reading is often the wrong one, so each entry says what a reader would otherwise get wrong.
Evidence
- Execution class
Whether a result came from a simulator, real hardware, or synthetic demo data.
Easy to get wrong: A simulated result is never evidence about hardware. This registry refuses results labelled HARDWARE because it cannot verify them.
Seen in use on /runs
- Reproducibility hash
A fingerprint of everything that defines a result, so an identical rerun is recognisable.
Easy to get wrong: A matching hash proves the record is self-consistent, not that the numbers came from where it claims. Anyone can compute a correct hash over a fabricated result.
Seen in use on /runs
- Benchmark suite
A versioned definition of an experiment, so two people can run the same thing.
Easy to get wrong: Runs from different suite versions are not comparable, and a leaderboard that mixes them is a ranking of different experiments.
Seen in use on /benchmarks
- Confidence interval
A range that would contain the true value most of the time, given the data.
Easy to get wrong: It is not a range the true value is 95% likely to sit in for this one experiment — it is a statement about the procedure, repeated.
Seen in use on /leaderboard