—
Shots Run
—
Doom Rate
—
Total Cost
—
Usable Shots
—
Shots Run
—
Doom Detected
—
Total Cost
—
Usable Shots
An abort stops further execution when early evidence shows the job is statistically likely to fail. Partial results are preserved for diagnostics, but remaining shots are not run to avoid wasted cost.
Run an initial probe phase (~10% of budget) using probe circuits or workload-specific doom detectors.
Calculate statistical confidence interval on doom rate. If confidence lower bound exceeds threshold, abort is triggered.
Early abort prevents wasting budget on remaining doomed shots. Savings depend on workload and abort timing.
LiveGate's doom detection is validated through ShotValidator hardware experiments on IBM Fez — 27 QEC configurations, 216K shots, 74% mean error reduction. The hardest config (d=7, r=8, f=3) eliminated all 63 logical errors.
216K
Shots validated
74%
Mean error reduction
63 → 0
Errors eliminated (d7)
Yes. Live Gate is a conservative safety layer. It may abort borderline jobs to protect budget when early evidence indicates elevated failure risk.
Abort decisions are based on a statistical confidence interval, not point estimates. Abort only triggers when the lower bound of the confidence interval exceeds the configured threshold.
Live Gate uses backend-calibrated doom detectors but applies uniformly across workloads. Policy inputs are tunable per backend, cost tier, or experiment class.
Live Gate performs per-shot doom detection during an initial probe phase using probe circuits. As shots accumulate, a statistical confidence interval is computed over the observed doom rate. If the lower bound of this interval exceeds the configured abort threshold, execution halts early to prevent further budget waste.