How ROX OS decides

Four verbs. Each one is a line on every record.

READ

Before anything is paid for, ROX OS reads the machine: today's two-qubit errors per coupler, readout error per qubit, T1. It chooses the loop of qubits with the least error and routes around every coupler that would quietly lose the answer.

PREDICT

The forecast is written down before the machine runs: the depth ROX will drive, the expected value, the regime, the price. Then it is sealed — a SHA-256 over the preregistration. Any change to the plan breaks the seal. If the forecast misses, the invoice is void.

OUTPERFORM

Both arms run on the same machine in the same window: the vendor's own default path and ROX. You choose beforehand what counts as a win — more confirmed depth, or the same confirmed result in less machine time. Won means ROX ahead on that metric. Not ahead: reported in the same size, in the loss colour.

PROVE

Every number comes from raw counts you can download. The recompute button on the record rebuilds the verdict from those counts in the browser. Job IDs point to the vendor's own records.

The recommendation, also against us

The forecast step names the regime per machine. Beyond the edge, ROX OS recommends a shallower rung — or tells you the default holds and ROX is not needed today. The run is never refused; the recommendation is written next to your choice.

Sources: the design guide §4 and §4b, the product register §9 (doctrine).