Understand the failure.
Verify the repair.
Small, reproducible software failures. The broken implementation, the fix that didn’t work, and the one that passed—preserved together.
Explore the cases ↓How results are verified ↗WHAT THE ARCHIVE CONTAINS
100840 executable cases. 20168 are open.
Every case records the implementation that fails, the fix that did not work, and the repair that passed its checks—with recorded outputs and source hashes. This release adds 100840 cases across 20168 failure mechanisms and 254 domains.
The open tier gives you the failure and the unsuccessful fix for one case in every mechanism. The remaining 80672 cases, 5 variants per mechanism, are member-only: the verified repair, its recorded checks, and the full fixture suite are held in the member archive. Read the methodology ↗
A RECORD OF WHAT WENT WRONG
Browse the archive / 100840
Clock reacquisition ignores negative jumps or treats allowed boundary as fault · case 01
The decoded time state disagrees with the explicit regression oracle for jumped.
Clock reacquisition ignores negative jumps or treats allowed boundary as fault · case 02
The decoded time state disagrees with the explicit regression oracle for jumped.
Clock reacquisition ignores negative jumps or treats allowed boundary as fault · case 03
The decoded time state disagrees with the explicit regression oracle for jumped.
Clock reacquisition ignores negative jumps or treats allowed boundary as fault · case 04
The decoded time state disagrees with the explicit regression oracle for jumped.
Clock reacquisition ignores negative jumps or treats allowed boundary as fault · case 05
The decoded time state disagrees with the explicit regression oracle for jumped.
Synchronization lock threshold rejects exact count or accepts first sample · case 01
The decoded time state disagrees with the explicit regression oracle for locked.
Synchronization lock threshold rejects exact count or accepts first sample · case 02
The decoded time state disagrees with the explicit regression oracle for locked.
Synchronization lock threshold rejects exact count or accepts first sample · case 03
The decoded time state disagrees with the explicit regression oracle for locked.
Synchronization lock threshold rejects exact count or accepts first sample · case 04
The decoded time state disagrees with the explicit regression oracle for locked.
Synchronization lock threshold rejects exact count or accepts first sample · case 05
The decoded time state disagrees with the explicit regression oracle for locked.
Fresh clock classification loses age boundary or never ages out · case 01
The decoded time state disagrees with the explicit regression oracle for recent.
Fresh clock classification loses age boundary or never ages out · case 02
The decoded time state disagrees with the explicit regression oracle for recent.
Fresh clock classification loses age boundary or never ages out · case 03
The decoded time state disagrees with the explicit regression oracle for recent.
Fresh clock classification loses age boundary or never ages out · case 04
The decoded time state disagrees with the explicit regression oracle for recent.
Fresh clock classification loses age boundary or never ages out · case 05
The decoded time state disagrees with the explicit regression oracle for recent.
Holdover quality survives maximum age or excludes its last admitted tick · case 01
The decoded time state disagrees with the explicit regression oracle for holdover.
Holdover quality survives maximum age or excludes its last admitted tick · case 02
The decoded time state disagrees with the explicit regression oracle for holdover.
Holdover quality survives maximum age or excludes its last admitted tick · case 03
The decoded time state disagrees with the explicit regression oracle for holdover.
Holdover quality survives maximum age or excludes its last admitted tick · case 04
The decoded time state disagrees with the explicit regression oracle for holdover.
Holdover quality survives maximum age or excludes its last admitted tick · case 05
The decoded time state disagrees with the explicit regression oracle for holdover.
Clock lock state overrides oscillator fault or phase-jump reacquisition · case 01
The decoded time state disagrees with the explicit regression oracle for state.
Clock lock state overrides oscillator fault or phase-jump reacquisition · case 02
The decoded time state disagrees with the explicit regression oracle for state.
Clock lock state overrides oscillator fault or phase-jump reacquisition · case 03
The decoded time state disagrees with the explicit regression oracle for state.
Clock lock state overrides oscillator fault or phase-jump reacquisition · case 04
The decoded time state disagrees with the explicit regression oracle for state.
Clock lock state overrides oscillator fault or phase-jump reacquisition · case 05
The decoded time state disagrees with the explicit regression oracle for state.
Holdover uncertainty rounds inward or grows while actively synchronized · case 01
The decoded time state disagrees with the explicit regression oracle for growth.
Holdover uncertainty rounds inward or grows while actively synchronized · case 02
The decoded time state disagrees with the explicit regression oracle for growth.
Holdover uncertainty rounds inward or grows while actively synchronized · case 03
The decoded time state disagrees with the explicit regression oracle for growth.
Holdover uncertainty rounds inward or grows while actively synchronized · case 04
The decoded time state disagrees with the explicit regression oracle for growth.
Holdover uncertainty rounds inward or grows while actively synchronized · case 05
The decoded time state disagrees with the explicit regression oracle for growth.
Clock uncertainty drops base calibration error or holdover drift · case 01
The decoded time state disagrees with the explicit regression oracle for error.
Clock uncertainty drops base calibration error or holdover drift · case 02
The decoded time state disagrees with the explicit regression oracle for error.
Clock uncertainty drops base calibration error or holdover drift · case 03
The decoded time state disagrees with the explicit regression oracle for error.
Clock uncertainty drops base calibration error or holdover drift · case 04
The decoded time state disagrees with the explicit regression oracle for error.
Clock uncertainty drops base calibration error or holdover drift · case 05
The decoded time state disagrees with the explicit regression oracle for error.
Clock usability ignores error budget or rejects bounded holdover · case 01
The decoded time state disagrees with the explicit regression oracle for usable.
Clock usability ignores error budget or rejects bounded holdover · case 02
The decoded time state disagrees with the explicit regression oracle for usable.
Clock usability ignores error budget or rejects bounded holdover · case 03
The decoded time state disagrees with the explicit regression oracle for usable.
Clock usability ignores error budget or rejects bounded holdover · case 04
The decoded time state disagrees with the explicit regression oracle for usable.
Clock usability ignores error budget or rejects bounded holdover · case 05
The decoded time state disagrees with the explicit regression oracle for usable.
Earliest transferred deadline reverses offset or takes late bound · case 01
The decoded time state disagrees with the explicit regression oracle for low.
Earliest transferred deadline reverses offset or takes late bound · case 02
The decoded time state disagrees with the explicit regression oracle for low.
Earliest transferred deadline reverses offset or takes late bound · case 03
The decoded time state disagrees with the explicit regression oracle for low.
Earliest transferred deadline reverses offset or takes late bound · case 04
The decoded time state disagrees with the explicit regression oracle for low.
Earliest transferred deadline reverses offset or takes late bound · case 05
The decoded time state disagrees with the explicit regression oracle for low.
Latest transferred deadline takes earliest uncertainty endpoint · case 01
The decoded time state disagrees with the explicit regression oracle for high.
Latest transferred deadline takes earliest uncertainty endpoint · case 02
The decoded time state disagrees with the explicit regression oracle for high.
Latest transferred deadline takes earliest uncertainty endpoint · case 03
The decoded time state disagrees with the explicit regression oracle for high.
Latest transferred deadline takes earliest uncertainty endpoint · case 04
The decoded time state disagrees with the explicit regression oracle for high.
Latest transferred deadline takes earliest uncertainty endpoint · case 05
The decoded time state disagrees with the explicit regression oracle for high.
Deadline transfer uses opposite guarantee or midpoint estimate · case 01
The decoded time state disagrees with the explicit regression oracle for chosen.
Deadline transfer uses opposite guarantee or midpoint estimate · case 02
The decoded time state disagrees with the explicit regression oracle for chosen.
Deadline transfer uses opposite guarantee or midpoint estimate · case 03
The decoded time state disagrees with the explicit regression oracle for chosen.
Deadline transfer uses opposite guarantee or midpoint estimate · case 04
The decoded time state disagrees with the explicit regression oracle for chosen.
Deadline transfer uses opposite guarantee or midpoint estimate · case 05
The decoded time state disagrees with the explicit regression oracle for chosen.
Transferred wait budget ignores elapsed transport · case 01
The decoded time state disagrees with the explicit regression oracle for arrival.
Transferred wait budget ignores elapsed transport · case 02
The decoded time state disagrees with the explicit regression oracle for arrival.
Transferred wait budget ignores elapsed transport · case 03
The decoded time state disagrees with the explicit regression oracle for arrival.
Transferred wait budget ignores elapsed transport · case 04
The decoded time state disagrees with the explicit regression oracle for arrival.
Transferred wait budget ignores elapsed transport · case 05
The decoded time state disagrees with the explicit regression oracle for arrival.
Elapsed deadline yields negative wait or a fresh positive wait · case 01
The decoded time state disagrees with the explicit regression oracle for remaining.
Elapsed deadline yields negative wait or a fresh positive wait · case 02
The decoded time state disagrees with the explicit regression oracle for remaining.
Elapsed deadline yields negative wait or a fresh positive wait · case 03
The decoded time state disagrees with the explicit regression oracle for remaining.
Elapsed deadline yields negative wait or a fresh positive wait · case 04
The decoded time state disagrees with the explicit regression oracle for remaining.
Elapsed deadline yields negative wait or a fresh positive wait · case 05
The decoded time state disagrees with the explicit regression oracle for remaining.
Platform relative timeout exceeds representable wait cap · case 01
The decoded time state disagrees with the explicit regression oracle for wait.
Platform relative timeout exceeds representable wait cap · case 02
The decoded time state disagrees with the explicit regression oracle for wait.
Platform relative timeout exceeds representable wait cap · case 03
The decoded time state disagrees with the explicit regression oracle for wait.
Platform relative timeout exceeds representable wait cap · case 04
The decoded time state disagrees with the explicit regression oracle for wait.
Platform relative timeout exceeds representable wait cap · case 05
The decoded time state disagrees with the explicit regression oracle for wait.
Long-timeout rearm flag uses exact cap or already-expired condition · case 01
The decoded time state disagrees with the explicit regression oracle for rearm.
Long-timeout rearm flag uses exact cap or already-expired condition · case 02
The decoded time state disagrees with the explicit regression oracle for rearm.
Long-timeout rearm flag uses exact cap or already-expired condition · case 03
The decoded time state disagrees with the explicit regression oracle for rearm.
Long-timeout rearm flag uses exact cap or already-expired condition · case 04
The decoded time state disagrees with the explicit regression oracle for rearm.
Long-timeout rearm flag uses exact cap or already-expired condition · case 05
The decoded time state disagrees with the explicit regression oracle for rearm.
Transferred deadline expiration excludes equality or reverses countdown test · case 01
The decoded time state disagrees with the explicit regression oracle for expired.
Transferred deadline expiration excludes equality or reverses countdown test · case 02
The decoded time state disagrees with the explicit regression oracle for expired.
Transferred deadline expiration excludes equality or reverses countdown test · case 03
The decoded time state disagrees with the explicit regression oracle for expired.
Transferred deadline expiration excludes equality or reverses countdown test · case 04
The decoded time state disagrees with the explicit regression oracle for expired.
Transferred deadline expiration excludes equality or reverses countdown test · case 05
The decoded time state disagrees with the explicit regression oracle for expired.
Actual wake instant ignores transport or capped intermediate rearm · case 01
The decoded time state disagrees with the explicit regression oracle for absolute_wake.
Actual wake instant ignores transport or capped intermediate rearm · case 02
The decoded time state disagrees with the explicit regression oracle for absolute_wake.
Actual wake instant ignores transport or capped intermediate rearm · case 03
The decoded time state disagrees with the explicit regression oracle for absolute_wake.
Actual wake instant ignores transport or capped intermediate rearm · case 04
The decoded time state disagrees with the explicit regression oracle for absolute_wake.
Actual wake instant ignores transport or capped intermediate rearm · case 05
The decoded time state disagrees with the explicit regression oracle for absolute_wake.
Transferred deadline uncertainty uses coordinate sum or selected policy offset · case 01
The decoded time state disagrees with the explicit regression oracle for slack.
Transferred deadline uncertainty uses coordinate sum or selected policy offset · case 02
The decoded time state disagrees with the explicit regression oracle for slack.
Transferred deadline uncertainty uses coordinate sum or selected policy offset · case 03
The decoded time state disagrees with the explicit regression oracle for slack.
Transferred deadline uncertainty uses coordinate sum or selected policy offset · case 04
The decoded time state disagrees with the explicit regression oracle for slack.
Transferred deadline uncertainty uses coordinate sum or selected policy offset · case 05
The decoded time state disagrees with the explicit regression oracle for slack.
Rollback filter measures elapsed in wall domain or hides monotonic regression · case 01
The decoded time state disagrees with the explicit regression oracle for elapsed.
Rollback filter measures elapsed in wall domain or hides monotonic regression · case 02
The decoded time state disagrees with the explicit regression oracle for elapsed.
Rollback filter measures elapsed in wall domain or hides monotonic regression · case 03
The decoded time state disagrees with the explicit regression oracle for elapsed.
Rollback filter measures elapsed in wall domain or hides monotonic regression · case 04
The decoded time state disagrees with the explicit regression oracle for elapsed.
Rollback filter measures elapsed in wall domain or hides monotonic regression · case 05
The decoded time state disagrees with the explicit regression oracle for elapsed.
Presentation clock commits invalid sample or rejects coincident sample · case 01
The decoded time state disagrees with the explicit regression oracle for valid.
Presentation clock commits invalid sample or rejects coincident sample · case 02
The decoded time state disagrees with the explicit regression oracle for valid.
Presentation clock commits invalid sample or rejects coincident sample · case 03
The decoded time state disagrees with the explicit regression oracle for valid.
Presentation clock commits invalid sample or rejects coincident sample · case 04
The decoded time state disagrees with the explicit regression oracle for valid.
Presentation clock commits invalid sample or rejects coincident sample · case 05
The decoded time state disagrees with the explicit regression oracle for valid.
INSPECTABLE BY DESIGN
Every result has a runnable source.
Runnable implementations with recorded outputs, source hashes, and explicit contracts. Related variants share a failure mechanism and belong together in evaluation splits.
Read the methodology ↗