Skip to main content
Verification · 2026

How to read a verification-suite result

Every card in the verification suite runs a published benchmark in your browser and stamps the result. This is what each line means, and how to check it yourself rather than take our word for it.

The lines on a card

Our value vs the reference
The number our engine produced beside the number in the published source. The two are shown together so you can see the gap, not just a pass mark.
The published reference
Where the expected number comes from — the worked example in the named standard, textbook or software verification manual. A benchmark only counts if a person can look it up there.
The tolerance
How close is close enough, stated in advance. Rounding in the source, reading a figure off a chart, and unit conventions all move a number slightly; the tolerance is the honest margin, not a hidden one.
The verdict
Whether our value sits inside the tolerance. A card that fails shows the failure — a benchmark you can only pass is not a check, it is an advertisement.
The SHA-256 stamp
A content hash over the inputs and the verdict. Re-run the same benchmark and the hash is identical, so you can confirm on your own machine that a run reproduces and was not edited for the screenshot.

Four ways to check us

  1. 01

    Open the reference

    Every card names its source. Go to the standard or manual it cites and find the worked example yourself. If you cannot find the number there, the benchmark is not anchored — that is the first thing to check on any vendor’s claim, ours included.

  2. 02

    Run it yourself

    The suite runs the actual engine in your browser, not a recording. Run the card and watch it produce the number. Then run it again — the SHA-256 stamp should be identical, which is what proves the run reproduces.

  3. 03

    Check the gap, not the tick

    A pass inside a wide tolerance is weaker than a pass inside a tight one. Look at how far our value is from the reference and ask whether you would accept that gap on a project you were signing.

  4. 04

    Re-type it into your own tool

    The strongest check is independent. Take the same inputs into the software you use today and compare its answer to both numbers. Three answers that agree are worth more than any one of them.

The whole registry, with every benchmark and its source, is on the verification page. The suite that runs them live is at /verification/suite.

Run one benchmark before you read another word.

Open the suite, run a card, check the hash. Then put the same inputs into the tool you use today.