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
Calibration age uses device reading or hides future certificate · case 01
The decoded time state disagrees with the explicit regression oracle for age.
Calibration age uses device reading or hides future certificate · case 02
The decoded time state disagrees with the explicit regression oracle for age.
Calibration age uses device reading or hides future certificate · case 03
The decoded time state disagrees with the explicit regression oracle for age.
Calibration age uses device reading or hides future certificate · case 04
The decoded time state disagrees with the explicit regression oracle for age.
Calibration age uses device reading or hides future certificate · case 05
The decoded time state disagrees with the explicit regression oracle for age.
Bridge accepts future calibration or expired endpoint · case 01
The decoded time state disagrees with the explicit regression oracle for fresh.
Bridge accepts future calibration or expired endpoint · case 02
The decoded time state disagrees with the explicit regression oracle for fresh.
Bridge accepts future calibration or expired endpoint · case 03
The decoded time state disagrees with the explicit regression oracle for fresh.
Bridge accepts future calibration or expired endpoint · case 04
The decoded time state disagrees with the explicit regression oracle for fresh.
Bridge accepts future calibration or expired endpoint · case 05
The decoded time state disagrees with the explicit regression oracle for fresh.
Clock bridge omits source anchor or reverses displacement · case 01
The decoded time state disagrees with the explicit regression oracle for delta.
Clock bridge omits source anchor or reverses displacement · case 02
The decoded time state disagrees with the explicit regression oracle for delta.
Clock bridge omits source anchor or reverses displacement · case 03
The decoded time state disagrees with the explicit regression oracle for delta.
Clock bridge omits source anchor or reverses displacement · case 04
The decoded time state disagrees with the explicit regression oracle for delta.
Clock bridge omits source anchor or reverses displacement · case 05
The decoded time state disagrees with the explicit regression oracle for delta.
Bridge extrapolation bound accepts arbitrarily early readings · case 01
The decoded time state disagrees with the explicit regression oracle for supported.
Bridge extrapolation bound accepts arbitrarily early readings · case 02
The decoded time state disagrees with the explicit regression oracle for supported.
Bridge extrapolation bound accepts arbitrarily early readings · case 03
The decoded time state disagrees with the explicit regression oracle for supported.
Bridge extrapolation bound accepts arbitrarily early readings · case 04
The decoded time state disagrees with the explicit regression oracle for supported.
Bridge extrapolation bound accepts arbitrarily early readings · case 05
The decoded time state disagrees with the explicit regression oracle for supported.
Clock bridge inverts rate or scales target-domain origin · case 01
The decoded time state disagrees with the explicit regression oracle for coordinate.
Clock bridge inverts rate or scales target-domain origin · case 02
The decoded time state disagrees with the explicit regression oracle for coordinate.
Clock bridge inverts rate or scales target-domain origin · case 03
The decoded time state disagrees with the explicit regression oracle for coordinate.
Clock bridge inverts rate or scales target-domain origin · case 04
The decoded time state disagrees with the explicit regression oracle for coordinate.
Clock bridge inverts rate or scales target-domain origin · case 05
The decoded time state disagrees with the explicit regression oracle for coordinate.
Bridge uncertainty is reversed or converted despite already being in target units · case 01
The decoded time state disagrees with the explicit regression oracle for low.
Bridge uncertainty is reversed or converted despite already being in target units · case 02
The decoded time state disagrees with the explicit regression oracle for low.
Bridge uncertainty is reversed or converted despite already being in target units · case 03
The decoded time state disagrees with the explicit regression oracle for low.
Bridge uncertainty is reversed or converted despite already being in target units · case 04
The decoded time state disagrees with the explicit regression oracle for low.
Bridge uncertainty is reversed or converted despite already being in target units · case 05
The decoded time state disagrees with the explicit regression oracle for low.
Bridge upper error bound shrinks or double-converts target units · case 01
The decoded time state disagrees with the explicit regression oracle for high.
Bridge upper error bound shrinks or double-converts target units · case 02
The decoded time state disagrees with the explicit regression oracle for high.
Bridge upper error bound shrinks or double-converts target units · case 03
The decoded time state disagrees with the explicit regression oracle for high.
Bridge upper error bound shrinks or double-converts target units · case 04
The decoded time state disagrees with the explicit regression oracle for high.
Bridge upper error bound shrinks or double-converts target units · case 05
The decoded time state disagrees with the explicit regression oracle for high.
Clock bridge accepts negative error certificate or rejects exact calibration · case 01
The decoded time state disagrees with the explicit regression oracle for accepted.
Clock bridge accepts negative error certificate or rejects exact calibration · case 02
The decoded time state disagrees with the explicit regression oracle for accepted.
Clock bridge accepts negative error certificate or rejects exact calibration · case 03
The decoded time state disagrees with the explicit regression oracle for accepted.
Clock bridge accepts negative error certificate or rejects exact calibration · case 04
The decoded time state disagrees with the explicit regression oracle for accepted.
Clock bridge accepts negative error certificate or rejects exact calibration · case 05
The decoded time state disagrees with the explicit regression oracle for accepted.
Awake elapsed time loses origin or crosses clock domains · case 01
The decoded time state disagrees with the explicit regression oracle for awake.
Awake elapsed time loses origin or crosses clock domains · case 02
The decoded time state disagrees with the explicit regression oracle for awake.
Awake elapsed time loses origin or crosses clock domains · case 03
The decoded time state disagrees with the explicit regression oracle for awake.
Awake elapsed time loses origin or crosses clock domains · case 04
The decoded time state disagrees with the explicit regression oracle for awake.
Awake elapsed time loses origin or crosses clock domains · case 05
The decoded time state disagrees with the explicit regression oracle for awake.
Suspend-inclusive elapsed is measured on awake clock · case 01
The decoded time state disagrees with the explicit regression oracle for boot.
Suspend-inclusive elapsed is measured on awake clock · case 02
The decoded time state disagrees with the explicit regression oracle for boot.
Suspend-inclusive elapsed is measured on awake clock · case 03
The decoded time state disagrees with the explicit regression oracle for boot.
Suspend-inclusive elapsed is measured on awake clock · case 04
The decoded time state disagrees with the explicit regression oracle for boot.
Suspend-inclusive elapsed is measured on awake clock · case 05
The decoded time state disagrees with the explicit regression oracle for boot.
Suspend delta reverses paired clocks or includes awake time · case 01
The decoded time state disagrees with the explicit regression oracle for sleep.
Suspend delta reverses paired clocks or includes awake time · case 02
The decoded time state disagrees with the explicit regression oracle for sleep.
Suspend delta reverses paired clocks or includes awake time · case 03
The decoded time state disagrees with the explicit regression oracle for sleep.
Suspend delta reverses paired clocks or includes awake time · case 04
The decoded time state disagrees with the explicit regression oracle for sleep.
Suspend delta reverses paired clocks or includes awake time · case 05
The decoded time state disagrees with the explicit regression oracle for sleep.
Paired clock sample fails to reject impossible negative segment · case 01
The decoded time state disagrees with the explicit regression oracle for valid.
Paired clock sample fails to reject impossible negative segment · case 02
The decoded time state disagrees with the explicit regression oracle for valid.
Paired clock sample fails to reject impossible negative segment · case 03
The decoded time state disagrees with the explicit regression oracle for valid.
Paired clock sample fails to reject impossible negative segment · case 04
The decoded time state disagrees with the explicit regression oracle for valid.
Paired clock sample fails to reject impossible negative segment · case 05
The decoded time state disagrees with the explicit regression oracle for valid.
Timer chooses one clock basis regardless of suspend policy · case 01
The decoded time state disagrees with the explicit regression oracle for selected.
Timer chooses one clock basis regardless of suspend policy · case 02
The decoded time state disagrees with the explicit regression oracle for selected.
Timer chooses one clock basis regardless of suspend policy · case 03
The decoded time state disagrees with the explicit regression oracle for selected.
Timer chooses one clock basis regardless of suspend policy · case 04
The decoded time state disagrees with the explicit regression oracle for selected.
Timer chooses one clock basis regardless of suspend policy · case 05
The decoded time state disagrees with the explicit regression oracle for selected.
Paused interval is ignored or produces negative consumed time · case 01
The decoded time state disagrees with the explicit regression oracle for consumed.
Paused interval is ignored or produces negative consumed time · case 02
The decoded time state disagrees with the explicit regression oracle for consumed.
Paused interval is ignored or produces negative consumed time · case 03
The decoded time state disagrees with the explicit regression oracle for consumed.
Paused interval is ignored or produces negative consumed time · case 04
The decoded time state disagrees with the explicit regression oracle for consumed.
Paused interval is ignored or produces negative consumed time · case 05
The decoded time state disagrees with the explicit regression oracle for consumed.
Countdown exhaustion produces negative budget or never consumes budget · case 01
The decoded time state disagrees with the explicit regression oracle for remaining.
Countdown exhaustion produces negative budget or never consumes budget · case 02
The decoded time state disagrees with the explicit regression oracle for remaining.
Countdown exhaustion produces negative budget or never consumes budget · case 03
The decoded time state disagrees with the explicit regression oracle for remaining.
Countdown exhaustion produces negative budget or never consumes budget · case 04
The decoded time state disagrees with the explicit regression oracle for remaining.
Countdown exhaustion produces negative budget or never consumes budget · case 05
The decoded time state disagrees with the explicit regression oracle for remaining.
Deadline coordinate is emitted in the other timer basis · case 01
The decoded time state disagrees with the explicit regression oracle for clock_now.
Deadline coordinate is emitted in the other timer basis · case 02
The decoded time state disagrees with the explicit regression oracle for clock_now.
Deadline coordinate is emitted in the other timer basis · case 03
The decoded time state disagrees with the explicit regression oracle for clock_now.
Deadline coordinate is emitted in the other timer basis · case 04
The decoded time state disagrees with the explicit regression oracle for clock_now.
Deadline coordinate is emitted in the other timer basis · case 05
The decoded time state disagrees with the explicit regression oracle for clock_now.
Deadline projection subtracts remaining budget or uses stale origin · case 01
The decoded time state disagrees with the explicit regression oracle for deadline.
Deadline projection subtracts remaining budget or uses stale origin · case 02
The decoded time state disagrees with the explicit regression oracle for deadline.
Deadline projection subtracts remaining budget or uses stale origin · case 03
The decoded time state disagrees with the explicit regression oracle for deadline.
Deadline projection subtracts remaining budget or uses stale origin · case 04
The decoded time state disagrees with the explicit regression oracle for deadline.
Deadline projection subtracts remaining budget or uses stale origin · case 05
The decoded time state disagrees with the explicit regression oracle for deadline.
Invalid paired clock sample expires timer or exact exhaustion remains live · case 01
The decoded time state disagrees with the explicit regression oracle for expired.
Invalid paired clock sample expires timer or exact exhaustion remains live · case 02
The decoded time state disagrees with the explicit regression oracle for expired.
Invalid paired clock sample expires timer or exact exhaustion remains live · case 03
The decoded time state disagrees with the explicit regression oracle for expired.
Invalid paired clock sample expires timer or exact exhaustion remains live · case 04
The decoded time state disagrees with the explicit regression oracle for expired.
Invalid paired clock sample expires timer or exact exhaustion remains live · case 05
The decoded time state disagrees with the explicit regression oracle for expired.
Timestamp migration confuses epoch zero with absent value · case 01
The decoded time state disagrees with the explicit regression oracle for present.
Timestamp migration confuses epoch zero with absent value · case 02
The decoded time state disagrees with the explicit regression oracle for present.
Timestamp migration confuses epoch zero with absent value · case 03
The decoded time state disagrees with the explicit regression oracle for present.
Timestamp migration confuses epoch zero with absent value · case 04
The decoded time state disagrees with the explicit regression oracle for present.
Timestamp migration confuses epoch zero with absent value · case 05
The decoded time state disagrees with the explicit regression oracle for present.
Migration admits future schema without known timestamp layout · case 01
The decoded time state disagrees with the explicit regression oracle for version_ok.
Migration admits future schema without known timestamp layout · case 02
The decoded time state disagrees with the explicit regression oracle for version_ok.
Migration admits future schema without known timestamp layout · case 03
The decoded time state disagrees with the explicit regression oracle for version_ok.
Migration admits future schema without known timestamp layout · case 04
The decoded time state disagrees with the explicit regression oracle for version_ok.
Migration admits future schema without known timestamp layout · case 05
The decoded time state disagrees with the explicit regression oracle for version_ok.
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 ↗