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
Slew direction reverses signed phase debt · case 01
The decoded time state disagrees with the explicit regression oracle for direction.
Slew direction reverses signed phase debt · case 02
The decoded time state disagrees with the explicit regression oracle for direction.
Slew direction reverses signed phase debt · case 03
The decoded time state disagrees with the explicit regression oracle for direction.
Slew direction reverses signed phase debt · case 04
The decoded time state disagrees with the explicit regression oracle for direction.
Slew direction reverses signed phase debt · case 05
The decoded time state disagrees with the explicit regression oracle for direction.
Slew step exceeds correction cap or loses debt direction · case 01
The decoded time state disagrees with the explicit regression oracle for applied.
Slew step exceeds correction cap or loses debt direction · case 02
The decoded time state disagrees with the explicit regression oracle for applied.
Slew step exceeds correction cap or loses debt direction · case 03
The decoded time state disagrees with the explicit regression oracle for applied.
Slew step exceeds correction cap or loses debt direction · case 04
The decoded time state disagrees with the explicit regression oracle for applied.
Slew step exceeds correction cap or loses debt direction · case 05
The decoded time state disagrees with the explicit regression oracle for applied.
Remaining negative correction is clipped as if it were a countdown · case 01
The decoded time state disagrees with the explicit regression oracle for remaining.
Remaining negative correction is clipped as if it were a countdown · case 02
The decoded time state disagrees with the explicit regression oracle for remaining.
Remaining negative correction is clipped as if it were a countdown · case 03
The decoded time state disagrees with the explicit regression oracle for remaining.
Remaining negative correction is clipped as if it were a countdown · case 04
The decoded time state disagrees with the explicit regression oracle for remaining.
Remaining negative correction is clipped as if it were a countdown · case 05
The decoded time state disagrees with the explicit regression oracle for remaining.
Wall advancement omits ordinary monotonic elapsed time · case 01
The decoded time state disagrees with the explicit regression oracle for advance.
Wall advancement omits ordinary monotonic elapsed time · case 02
The decoded time state disagrees with the explicit regression oracle for advance.
Wall advancement omits ordinary monotonic elapsed time · case 03
The decoded time state disagrees with the explicit regression oracle for advance.
Wall advancement omits ordinary monotonic elapsed time · case 04
The decoded time state disagrees with the explicit regression oracle for advance.
Wall advancement omits ordinary monotonic elapsed time · case 05
The decoded time state disagrees with the explicit regression oracle for advance.
Clock slewing discards phase correction or original wall origin · case 01
The decoded time state disagrees with the explicit regression oracle for wall.
Clock slewing discards phase correction or original wall origin · case 02
The decoded time state disagrees with the explicit regression oracle for wall.
Clock slewing discards phase correction or original wall origin · case 03
The decoded time state disagrees with the explicit regression oracle for wall.
Clock slewing discards phase correction or original wall origin · case 04
The decoded time state disagrees with the explicit regression oracle for wall.
Clock slewing discards phase correction or original wall origin · case 05
The decoded time state disagrees with the explicit regression oracle for wall.
Negative unfinished debt is marked synchronized · case 01
The decoded time state disagrees with the explicit regression oracle for complete.
Negative unfinished debt is marked synchronized · case 02
The decoded time state disagrees with the explicit regression oracle for complete.
Negative unfinished debt is marked synchronized · case 03
The decoded time state disagrees with the explicit regression oracle for complete.
Negative unfinished debt is marked synchronized · case 04
The decoded time state disagrees with the explicit regression oracle for complete.
Negative unfinished debt is marked synchronized · case 05
The decoded time state disagrees with the explicit regression oracle for complete.
Negative correction creates extra reported slew capacity · case 01
The decoded time state disagrees with the explicit regression oracle for unused.
Negative correction creates extra reported slew capacity · case 02
The decoded time state disagrees with the explicit regression oracle for unused.
Negative correction creates extra reported slew capacity · case 03
The decoded time state disagrees with the explicit regression oracle for unused.
Negative correction creates extra reported slew capacity · case 04
The decoded time state disagrees with the explicit regression oracle for unused.
Negative correction creates extra reported slew capacity · case 05
The decoded time state disagrees with the explicit regression oracle for unused.
Cumulative wall correction resets or loses signed history · case 01
The decoded time state disagrees with the explicit regression oracle for cumulative.
Cumulative wall correction resets or loses signed history · case 02
The decoded time state disagrees with the explicit regression oracle for cumulative.
Cumulative wall correction resets or loses signed history · case 03
The decoded time state disagrees with the explicit regression oracle for cumulative.
Cumulative wall correction resets or loses signed history · case 04
The decoded time state disagrees with the explicit regression oracle for cumulative.
Cumulative wall correction resets or loses signed history · case 05
The decoded time state disagrees with the explicit regression oracle for cumulative.
Old civil branch applies new or reversed UTC offset · case 01
The decoded time state disagrees with the explicit regression oracle for old_candidate.
Old civil branch applies new or reversed UTC offset · case 02
The decoded time state disagrees with the explicit regression oracle for old_candidate.
Old civil branch applies new or reversed UTC offset · case 03
The decoded time state disagrees with the explicit regression oracle for old_candidate.
Old civil branch applies new or reversed UTC offset · case 04
The decoded time state disagrees with the explicit regression oracle for old_candidate.
Old civil branch applies new or reversed UTC offset · case 05
The decoded time state disagrees with the explicit regression oracle for old_candidate.
New civil branch retains the pre-transition offset · case 01
The decoded time state disagrees with the explicit regression oracle for new_candidate.
New civil branch retains the pre-transition offset · case 02
The decoded time state disagrees with the explicit regression oracle for new_candidate.
New civil branch retains the pre-transition offset · case 03
The decoded time state disagrees with the explicit regression oracle for new_candidate.
New civil branch retains the pre-transition offset · case 04
The decoded time state disagrees with the explicit regression oracle for new_candidate.
New civil branch retains the pre-transition offset · case 05
The decoded time state disagrees with the explicit regression oracle for new_candidate.
Old branch owns transition instant or compares local coordinate to UTC · case 01
The decoded time state disagrees with the explicit regression oracle for old_valid.
Old branch owns transition instant or compares local coordinate to UTC · case 02
The decoded time state disagrees with the explicit regression oracle for old_valid.
Old branch owns transition instant or compares local coordinate to UTC · case 03
The decoded time state disagrees with the explicit regression oracle for old_valid.
Old branch owns transition instant or compares local coordinate to UTC · case 04
The decoded time state disagrees with the explicit regression oracle for old_valid.
Old branch owns transition instant or compares local coordinate to UTC · case 05
The decoded time state disagrees with the explicit regression oracle for old_valid.
New branch excludes its first instant · case 01
The decoded time state disagrees with the explicit regression oracle for new_valid.
New branch excludes its first instant · case 02
The decoded time state disagrees with the explicit regression oracle for new_valid.
New branch excludes its first instant · case 03
The decoded time state disagrees with the explicit regression oracle for new_valid.
New branch excludes its first instant · case 04
The decoded time state disagrees with the explicit regression oracle for new_valid.
New branch excludes its first instant · case 05
The decoded time state disagrees with the explicit regression oracle for new_valid.
Fold enumeration discards the second branch or keeps invalid branches · case 01
The decoded time state disagrees with the explicit regression oracle for candidates.
Fold enumeration discards the second branch or keeps invalid branches · case 02
The decoded time state disagrees with the explicit regression oracle for candidates.
Fold enumeration discards the second branch or keeps invalid branches · case 03
The decoded time state disagrees with the explicit regression oracle for candidates.
Fold enumeration discards the second branch or keeps invalid branches · case 04
The decoded time state disagrees with the explicit regression oracle for candidates.
Fold enumeration discards the second branch or keeps invalid branches · case 05
The decoded time state disagrees with the explicit regression oracle for candidates.
Civil multiplicity collapses two valid instants · case 01
The decoded time state disagrees with the explicit regression oracle for count.
Civil multiplicity collapses two valid instants · case 02
The decoded time state disagrees with the explicit regression oracle for count.
Civil multiplicity collapses two valid instants · case 03
The decoded time state disagrees with the explicit regression oracle for count.
Civil multiplicity collapses two valid instants · case 04
The decoded time state disagrees with the explicit regression oracle for count.
Civil multiplicity collapses two valid instants · case 05
The decoded time state disagrees with the explicit regression oracle for count.
A unique civil instant is labeled ambiguous · case 01
The decoded time state disagrees with the explicit regression oracle for ambiguous.
A unique civil instant is labeled ambiguous · case 02
The decoded time state disagrees with the explicit regression oracle for ambiguous.
A unique civil instant is labeled ambiguous · case 03
The decoded time state disagrees with the explicit regression oracle for ambiguous.
A unique civil instant is labeled ambiguous · case 04
The decoded time state disagrees with the explicit regression oracle for ambiguous.
A unique civil instant is labeled ambiguous · case 05
The decoded time state disagrees with the explicit regression oracle for ambiguous.
Fold resolver ignores later or reject selection policy · case 01
The decoded time state disagrees with the explicit regression oracle for chosen.
Fold resolver ignores later or reject selection policy · case 02
The decoded time state disagrees with the explicit regression oracle for chosen.
Fold resolver ignores later or reject selection policy · case 03
The decoded time state disagrees with the explicit regression oracle for chosen.
Fold resolver ignores later or reject selection policy · case 04
The decoded time state disagrees with the explicit regression oracle for chosen.
Fold resolver ignores later or reject selection policy · case 05
The decoded time state disagrees with the explicit regression oracle for chosen.
Resolved instant uses an offset from the other fold branch · case 01
The decoded time state disagrees with the explicit regression oracle for offset.
Resolved instant uses an offset from the other fold branch · case 02
The decoded time state disagrees with the explicit regression oracle for offset.
Resolved instant uses an offset from the other fold branch · case 03
The decoded time state disagrees with the explicit regression oracle for offset.
Resolved instant uses an offset from the other fold branch · case 04
The decoded time state disagrees with the explicit regression oracle for offset.
Resolved instant uses an offset from the other fold branch · case 05
The decoded time state disagrees with the explicit regression oracle for offset.
Civil roundtrip subtracts the selected zone offset · case 01
The decoded time state disagrees with the explicit regression oracle for roundtrip.
Civil roundtrip subtracts the selected zone offset · case 02
The decoded time state disagrees with the explicit regression oracle for roundtrip.
Civil roundtrip subtracts the selected zone offset · case 03
The decoded time state disagrees with the explicit regression oracle for roundtrip.
Civil roundtrip subtracts the selected zone offset · case 04
The decoded time state disagrees with the explicit regression oracle for roundtrip.
Civil roundtrip subtracts the selected zone offset · case 05
The decoded time state disagrees with the explicit regression oracle for roundtrip.
Civil gap starts on the wrong offset branch · case 01
The decoded time state disagrees with the explicit regression oracle for start.
Civil gap starts on the wrong offset branch · case 02
The decoded time state disagrees with the explicit regression oracle for start.
Civil gap starts on the wrong offset branch · case 03
The decoded time state disagrees with the explicit regression oracle for start.
Civil gap starts on the wrong offset branch · case 04
The decoded time state disagrees with the explicit regression oracle for start.
Civil gap starts on the wrong offset branch · case 05
The decoded time state disagrees with the explicit regression oracle for start.
Civil gap end is interpreted in UTC instead of new local coordinates · case 01
The decoded time state disagrees with the explicit regression oracle for end.
Civil gap end is interpreted in UTC instead of new local coordinates · case 02
The decoded time state disagrees with the explicit regression oracle for end.
Civil gap end is interpreted in UTC instead of new local coordinates · case 03
The decoded time state disagrees with the explicit regression oracle for end.
Civil gap end is interpreted in UTC instead of new local coordinates · case 04
The decoded time state disagrees with the explicit regression oracle for end.
Civil gap end is interpreted in UTC instead of new local coordinates · case 05
The decoded time state disagrees with the explicit regression oracle for end.
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 ↗