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
Negative leap smear receives positive correction · case 01
The decoded time state disagrees with the explicit regression oracle for correction.
Negative leap smear receives positive correction · case 02
The decoded time state disagrees with the explicit regression oracle for correction.
Negative leap smear receives positive correction · case 03
The decoded time state disagrees with the explicit regression oracle for correction.
Negative leap smear receives positive correction · case 04
The decoded time state disagrees with the explicit regression oracle for correction.
Negative leap smear receives positive correction · case 05
The decoded time state disagrees with the explicit regression oracle for correction.
Smear coordinate reverses phase correction or quantizes early · case 01
The decoded time state disagrees with the explicit regression oracle for smeared.
Smear coordinate reverses phase correction or quantizes early · case 02
The decoded time state disagrees with the explicit regression oracle for smeared.
Smear coordinate reverses phase correction or quantizes early · case 03
The decoded time state disagrees with the explicit regression oracle for smeared.
Smear coordinate reverses phase correction or quantizes early · case 04
The decoded time state disagrees with the explicit regression oracle for smeared.
Smear coordinate reverses phase correction or quantizes early · case 05
The decoded time state disagrees with the explicit regression oracle for smeared.
Smear slope persists at the completed endpoint · case 01
The decoded time state disagrees with the explicit regression oracle for active.
Smear slope persists at the completed endpoint · case 02
The decoded time state disagrees with the explicit regression oracle for active.
Smear slope persists at the completed endpoint · case 03
The decoded time state disagrees with the explicit regression oracle for active.
Smear slope persists at the completed endpoint · case 04
The decoded time state disagrees with the explicit regression oracle for active.
Smear slope persists at the completed endpoint · case 05
The decoded time state disagrees with the explicit regression oracle for active.
Smear derivative reverses sign or persists outside interval · case 01
The decoded time state disagrees with the explicit regression oracle for slope.
Smear derivative reverses sign or persists outside interval · case 02
The decoded time state disagrees with the explicit regression oracle for slope.
Smear derivative reverses sign or persists outside interval · case 03
The decoded time state disagrees with the explicit regression oracle for slope.
Smear derivative reverses sign or persists outside interval · case 04
The decoded time state disagrees with the explicit regression oracle for slope.
Smear derivative reverses sign or persists outside interval · case 05
The decoded time state disagrees with the explicit regression oracle for slope.
Smear residual loses the signed removed leap amount · case 01
The decoded time state disagrees with the explicit regression oracle for residual.
Smear residual loses the signed removed leap amount · case 02
The decoded time state disagrees with the explicit regression oracle for residual.
Smear residual loses the signed removed leap amount · case 03
The decoded time state disagrees with the explicit regression oracle for residual.
Smear residual loses the signed removed leap amount · case 04
The decoded time state disagrees with the explicit regression oracle for residual.
Smear residual loses the signed removed leap amount · case 05
The decoded time state disagrees with the explicit regression oracle for residual.
Smear starts with full correction or rebases absolute origin · case 01
The decoded time state disagrees with the explicit regression oracle for start_coordinate.
Smear starts with full correction or rebases absolute origin · case 02
The decoded time state disagrees with the explicit regression oracle for start_coordinate.
Smear starts with full correction or rebases absolute origin · case 03
The decoded time state disagrees with the explicit regression oracle for start_coordinate.
Smear starts with full correction or rebases absolute origin · case 04
The decoded time state disagrees with the explicit regression oracle for start_coordinate.
Smear starts with full correction or rebases absolute origin · case 05
The decoded time state disagrees with the explicit regression oracle for start_coordinate.
Smear endpoint omits or reverses completed leap removal · case 01
The decoded time state disagrees with the explicit regression oracle for end_coordinate.
Smear endpoint omits or reverses completed leap removal · case 02
The decoded time state disagrees with the explicit regression oracle for end_coordinate.
Smear endpoint omits or reverses completed leap removal · case 03
The decoded time state disagrees with the explicit regression oracle for end_coordinate.
Smear endpoint omits or reverses completed leap removal · case 04
The decoded time state disagrees with the explicit regression oracle for end_coordinate.
Smear endpoint omits or reverses completed leap removal · case 05
The decoded time state disagrees with the explicit regression oracle for end_coordinate.
Remaining smear debt records applied correction or loses negative leap sign · case 01
The decoded time state disagrees with the explicit regression oracle for remaining.
Remaining smear debt records applied correction or loses negative leap sign · case 02
The decoded time state disagrees with the explicit regression oracle for remaining.
Remaining smear debt records applied correction or loses negative leap sign · case 03
The decoded time state disagrees with the explicit regression oracle for remaining.
Remaining smear debt records applied correction or loses negative leap sign · case 04
The decoded time state disagrees with the explicit regression oracle for remaining.
Remaining smear debt records applied correction or loses negative leap sign · case 05
The decoded time state disagrees with the explicit regression oracle for remaining.
Decimal instant sign accepts embedded minus or treats plus as negative · case 01
The decoded time state disagrees with the explicit regression oracle for negative.
Decimal instant sign accepts embedded minus or treats plus as negative · case 02
The decoded time state disagrees with the explicit regression oracle for negative.
Decimal instant sign accepts embedded minus or treats plus as negative · case 03
The decoded time state disagrees with the explicit regression oracle for negative.
Decimal instant sign accepts embedded minus or treats plus as negative · case 04
The decoded time state disagrees with the explicit regression oracle for negative.
Decimal instant sign accepts embedded minus or treats plus as negative · case 05
The decoded time state disagrees with the explicit regression oracle for negative.
Sign removal accepts repeated signs or silently trims timestamp whitespace · case 01
The decoded time state disagrees with the explicit regression oracle for payload.
Sign removal accepts repeated signs or silently trims timestamp whitespace · case 02
The decoded time state disagrees with the explicit regression oracle for payload.
Sign removal accepts repeated signs or silently trims timestamp whitespace · case 03
The decoded time state disagrees with the explicit regression oracle for payload.
Sign removal accepts repeated signs or silently trims timestamp whitespace · case 04
The decoded time state disagrees with the explicit regression oracle for payload.
Sign removal accepts repeated signs or silently trims timestamp whitespace · case 05
The decoded time state disagrees with the explicit regression oracle for payload.
Timestamp delimiter normalization admits unsupported decimal separator · case 01
The decoded time state disagrees with the explicit regression oracle for parts.
Timestamp delimiter normalization admits unsupported decimal separator · case 02
The decoded time state disagrees with the explicit regression oracle for parts.
Timestamp delimiter normalization admits unsupported decimal separator · case 03
The decoded time state disagrees with the explicit regression oracle for parts.
Timestamp delimiter normalization admits unsupported decimal separator · case 04
The decoded time state disagrees with the explicit regression oracle for parts.
Timestamp delimiter normalization admits unsupported decimal separator · case 05
The decoded time state disagrees with the explicit regression oracle for parts.
Epoch parser synthesizes missing whole digits or accepts plus prefix · case 01
The decoded time state disagrees with the explicit regression oracle for whole.
Epoch parser synthesizes missing whole digits or accepts plus prefix · case 02
The decoded time state disagrees with the explicit regression oracle for whole.
Epoch parser synthesizes missing whole digits or accepts plus prefix · case 03
The decoded time state disagrees with the explicit regression oracle for whole.
Epoch parser synthesizes missing whole digits or accepts plus prefix · case 04
The decoded time state disagrees with the explicit regression oracle for whole.
Epoch parser synthesizes missing whole digits or accepts plus prefix · case 05
The decoded time state disagrees with the explicit regression oracle for whole.
Timestamp precision validation runs after destructive fraction normalization · case 01
The decoded time state disagrees with the explicit regression oracle for fraction.
Timestamp precision validation runs after destructive fraction normalization · case 02
The decoded time state disagrees with the explicit regression oracle for fraction.
Timestamp precision validation runs after destructive fraction normalization · case 03
The decoded time state disagrees with the explicit regression oracle for fraction.
Timestamp precision validation runs after destructive fraction normalization · case 04
The decoded time state disagrees with the explicit regression oracle for fraction.
Timestamp precision validation runs after destructive fraction normalization · case 05
The decoded time state disagrees with the explicit regression oracle for fraction.
Whole timestamp accepts Unicode digit forms or embedded spaces · case 01
The decoded time state disagrees with the explicit regression oracle for whole_valid.
Whole timestamp accepts Unicode digit forms or embedded spaces · case 02
The decoded time state disagrees with the explicit regression oracle for whole_valid.
Whole timestamp accepts Unicode digit forms or embedded spaces · case 03
The decoded time state disagrees with the explicit regression oracle for whole_valid.
Whole timestamp accepts Unicode digit forms or embedded spaces · case 04
The decoded time state disagrees with the explicit regression oracle for whole_valid.
Whole timestamp accepts Unicode digit forms or embedded spaces · case 05
The decoded time state disagrees with the explicit regression oracle for whole_valid.
Fraction accepts an empty suffix or Unicode numeric characters · case 01
The decoded time state disagrees with the explicit regression oracle for fraction_valid.
Fraction accepts an empty suffix or Unicode numeric characters · case 02
The decoded time state disagrees with the explicit regression oracle for fraction_valid.
Fraction accepts an empty suffix or Unicode numeric characters · case 03
The decoded time state disagrees with the explicit regression oracle for fraction_valid.
Fraction accepts an empty suffix or Unicode numeric characters · case 04
The decoded time state disagrees with the explicit regression oracle for fraction_valid.
Fraction accepts an empty suffix or Unicode numeric characters · case 05
The decoded time state disagrees with the explicit regression oracle for fraction_valid.
Timestamp admission supports only one precision form · case 01
The decoded time state disagrees with the explicit regression oracle for valid.
Timestamp admission supports only one precision form · case 02
The decoded time state disagrees with the explicit regression oracle for valid.
Timestamp admission supports only one precision form · case 03
The decoded time state disagrees with the explicit regression oracle for valid.
Timestamp admission supports only one precision form · case 04
The decoded time state disagrees with the explicit regression oracle for valid.
Timestamp admission supports only one precision form · case 05
The decoded time state disagrees with the explicit regression oracle for valid.
Fractional timestamp digits are aligned as integers instead of decimal places · case 01
The decoded time state disagrees with the explicit regression oracle for magnitude.
Fractional timestamp digits are aligned as integers instead of decimal places · case 02
The decoded time state disagrees with the explicit regression oracle for magnitude.
Fractional timestamp digits are aligned as integers instead of decimal places · case 03
The decoded time state disagrees with the explicit regression oracle for magnitude.
Fractional timestamp digits are aligned as integers instead of decimal places · case 04
The decoded time state disagrees with the explicit regression oracle for magnitude.
Fractional timestamp digits are aligned as integers instead of decimal places · case 05
The decoded time state disagrees with the explicit regression oracle for magnitude.
Negative timestamp sign applies only to whole component · case 01
The decoded time state disagrees with the explicit regression oracle for milliseconds.
Negative timestamp sign applies only to whole component · case 02
The decoded time state disagrees with the explicit regression oracle for milliseconds.
Negative timestamp sign applies only to whole component · case 03
The decoded time state disagrees with the explicit regression oracle for milliseconds.
Negative timestamp sign applies only to whole component · case 04
The decoded time state disagrees with the explicit regression oracle for milliseconds.
Negative timestamp sign applies only to whole component · case 05
The decoded time state disagrees with the explicit regression oracle for milliseconds.
RTC hour read reuses a preceding latch generation · case 01
The decoded time state disagrees with the explicit regression oracle for hour.
RTC hour read reuses a preceding latch generation · case 02
The decoded time state disagrees with the explicit regression oracle for hour.
RTC hour read reuses a preceding latch generation · case 03
The decoded time state disagrees with the explicit regression oracle for hour.
RTC hour read reuses a preceding latch generation · case 04
The decoded time state disagrees with the explicit regression oracle for hour.
RTC hour read reuses a preceding latch generation · case 05
The decoded time state disagrees with the explicit regression oracle for hour.
RTC minute tens nibble is reversed or dropped · case 01
The decoded time state disagrees with the explicit regression oracle for minute.
RTC minute tens nibble is reversed or dropped · case 02
The decoded time state disagrees with the explicit regression oracle for minute.
RTC minute tens nibble is reversed or dropped · case 03
The decoded time state disagrees with the explicit regression oracle for minute.
RTC minute tens nibble is reversed or dropped · case 04
The decoded time state disagrees with the explicit regression oracle for minute.
RTC minute tens nibble is reversed or dropped · case 05
The decoded time state disagrees with the explicit regression oracle for minute.
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 ↗