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
Offset grammar loses sign or required colon position · case 01
The decoded time state disagrees with the explicit regression oracle for shape.
Offset grammar loses sign or required colon position · case 02
The decoded time state disagrees with the explicit regression oracle for shape.
Offset grammar loses sign or required colon position · case 03
The decoded time state disagrees with the explicit regression oracle for shape.
Offset grammar loses sign or required colon position · case 04
The decoded time state disagrees with the explicit regression oracle for shape.
Offset grammar loses sign or required colon position · case 05
The decoded time state disagrees with the explicit regression oracle for shape.
Offset parser admits non-ASCII decimal glyphs · case 01
The decoded time state disagrees with the explicit regression oracle for digits.
Offset parser admits non-ASCII decimal glyphs · case 02
The decoded time state disagrees with the explicit regression oracle for digits.
Offset parser admits non-ASCII decimal glyphs · case 03
The decoded time state disagrees with the explicit regression oracle for digits.
Offset parser admits non-ASCII decimal glyphs · case 04
The decoded time state disagrees with the explicit regression oracle for digits.
Offset parser admits non-ASCII decimal glyphs · case 05
The decoded time state disagrees with the explicit regression oracle for digits.
Offset hour field reads minutes or only tens digit · case 01
The decoded time state disagrees with the explicit regression oracle for hour.
Offset hour field reads minutes or only tens digit · case 02
The decoded time state disagrees with the explicit regression oracle for hour.
Offset hour field reads minutes or only tens digit · case 03
The decoded time state disagrees with the explicit regression oracle for hour.
Offset hour field reads minutes or only tens digit · case 04
The decoded time state disagrees with the explicit regression oracle for hour.
Offset hour field reads minutes or only tens digit · case 05
The decoded time state disagrees with the explicit regression oracle for hour.
Offset minute field loses units position · case 01
The decoded time state disagrees with the explicit regression oracle for minute.
Offset minute field loses units position · case 02
The decoded time state disagrees with the explicit regression oracle for minute.
Offset minute field loses units position · case 03
The decoded time state disagrees with the explicit regression oracle for minute.
Offset minute field loses units position · case 04
The decoded time state disagrees with the explicit regression oracle for minute.
Offset minute field loses units position · case 05
The decoded time state disagrees with the explicit regression oracle for minute.
Maximum offset policy loses the fourteen-hour zero-minute exception · case 01
The decoded time state disagrees with the explicit regression oracle for range_ok.
Maximum offset policy loses the fourteen-hour zero-minute exception · case 02
The decoded time state disagrees with the explicit regression oracle for range_ok.
Maximum offset policy loses the fourteen-hour zero-minute exception · case 03
The decoded time state disagrees with the explicit regression oracle for range_ok.
Maximum offset policy loses the fourteen-hour zero-minute exception · case 04
The decoded time state disagrees with the explicit regression oracle for range_ok.
Maximum offset policy loses the fourteen-hour zero-minute exception · case 05
The decoded time state disagrees with the explicit regression oracle for range_ok.
Offset admission omits range gate or rejects Z representation · case 01
The decoded time state disagrees with the explicit regression oracle for valid.
Offset admission omits range gate or rejects Z representation · case 02
The decoded time state disagrees with the explicit regression oracle for valid.
Offset admission omits range gate or rejects Z representation · case 03
The decoded time state disagrees with the explicit regression oracle for valid.
Offset admission omits range gate or rejects Z representation · case 04
The decoded time state disagrees with the explicit regression oracle for valid.
Offset admission omits range gate or rejects Z representation · case 05
The decoded time state disagrees with the explicit regression oracle for valid.
Unknown negative-zero offset collapses into known UTC or absorbs positive zero · case 01
The decoded time state disagrees with the explicit regression oracle for unknown.
Unknown negative-zero offset collapses into known UTC or absorbs positive zero · case 02
The decoded time state disagrees with the explicit regression oracle for unknown.
Unknown negative-zero offset collapses into known UTC or absorbs positive zero · case 03
The decoded time state disagrees with the explicit regression oracle for unknown.
Unknown negative-zero offset collapses into known UTC or absorbs positive zero · case 04
The decoded time state disagrees with the explicit regression oracle for unknown.
Unknown negative-zero offset collapses into known UTC or absorbs positive zero · case 05
The decoded time state disagrees with the explicit regression oracle for unknown.
Negative UTC offset loses sign on its minute component · case 01
The decoded time state disagrees with the explicit regression oracle for offset.
Negative UTC offset loses sign on its minute component · case 02
The decoded time state disagrees with the explicit regression oracle for offset.
Negative UTC offset loses sign on its minute component · case 03
The decoded time state disagrees with the explicit regression oracle for offset.
Negative UTC offset loses sign on its minute component · case 04
The decoded time state disagrees with the explicit regression oracle for offset.
Negative UTC offset loses sign on its minute component · case 05
The decoded time state disagrees with the explicit regression oracle for offset.
Rate switch continuity anchor omits monotonic origin · case 01
The decoded time state disagrees with the explicit regression oracle for first_span.
Rate switch continuity anchor omits monotonic origin · case 02
The decoded time state disagrees with the explicit regression oracle for first_span.
Rate switch continuity anchor omits monotonic origin · case 03
The decoded time state disagrees with the explicit regression oracle for first_span.
Rate switch continuity anchor omits monotonic origin · case 04
The decoded time state disagrees with the explicit regression oracle for first_span.
Rate switch continuity anchor omits monotonic origin · case 05
The decoded time state disagrees with the explicit regression oracle for first_span.
Initial virtual clock rate is inverted or integer-truncated · case 01
The decoded time state disagrees with the explicit regression oracle for first_rate.
Initial virtual clock rate is inverted or integer-truncated · case 02
The decoded time state disagrees with the explicit regression oracle for first_rate.
Initial virtual clock rate is inverted or integer-truncated · case 03
The decoded time state disagrees with the explicit regression oracle for first_rate.
Initial virtual clock rate is inverted or integer-truncated · case 04
The decoded time state disagrees with the explicit regression oracle for first_rate.
Initial virtual clock rate is inverted or integer-truncated · case 05
The decoded time state disagrees with the explicit regression oracle for first_rate.
Rate switch retains old slope or inverts replacement slope · case 01
The decoded time state disagrees with the explicit regression oracle for second_rate.
Rate switch retains old slope or inverts replacement slope · case 02
The decoded time state disagrees with the explicit regression oracle for second_rate.
Rate switch retains old slope or inverts replacement slope · case 03
The decoded time state disagrees with the explicit regression oracle for second_rate.
Rate switch retains old slope or inverts replacement slope · case 04
The decoded time state disagrees with the explicit regression oracle for second_rate.
Rate switch retains old slope or inverts replacement slope · case 05
The decoded time state disagrees with the explicit regression oracle for second_rate.
Rate change retrospectively applies new rate to old elapsed interval · case 01
The decoded time state disagrees with the explicit regression oracle for join.
Rate change retrospectively applies new rate to old elapsed interval · case 02
The decoded time state disagrees with the explicit regression oracle for join.
Rate change retrospectively applies new rate to old elapsed interval · case 03
The decoded time state disagrees with the explicit regression oracle for join.
Rate change retrospectively applies new rate to old elapsed interval · case 04
The decoded time state disagrees with the explicit regression oracle for join.
Rate change retrospectively applies new rate to old elapsed interval · case 05
The decoded time state disagrees with the explicit regression oracle for join.
Rate switch endpoint retains previous slope or applies new slope early · case 01
The decoded time state disagrees with the explicit regression oracle for second.
Rate switch endpoint retains previous slope or applies new slope early · case 02
The decoded time state disagrees with the explicit regression oracle for second.
Rate switch endpoint retains previous slope or applies new slope early · case 03
The decoded time state disagrees with the explicit regression oracle for second.
Rate switch endpoint retains previous slope or applies new slope early · case 04
The decoded time state disagrees with the explicit regression oracle for second.
Rate switch endpoint retains previous slope or applies new slope early · case 05
The decoded time state disagrees with the explicit regression oracle for second.
Post-switch displacement is measured from original anchor · case 01
The decoded time state disagrees with the explicit regression oracle for delta.
Post-switch displacement is measured from original anchor · case 02
The decoded time state disagrees with the explicit regression oracle for delta.
Post-switch displacement is measured from original anchor · case 03
The decoded time state disagrees with the explicit regression oracle for delta.
Post-switch displacement is measured from original anchor · case 04
The decoded time state disagrees with the explicit regression oracle for delta.
Post-switch displacement is measured from original anchor · case 05
The decoded time state disagrees with the explicit regression oracle for delta.
Virtual reading uses one rate on both sides of switch · case 01
The decoded time state disagrees with the explicit regression oracle for active.
Virtual reading uses one rate on both sides of switch · case 02
The decoded time state disagrees with the explicit regression oracle for active.
Virtual reading uses one rate on both sides of switch · case 03
The decoded time state disagrees with the explicit regression oracle for active.
Virtual reading uses one rate on both sides of switch · case 04
The decoded time state disagrees with the explicit regression oracle for active.
Virtual reading uses one rate on both sides of switch · case 05
The decoded time state disagrees with the explicit regression oracle for active.
Piecewise clock discards continuity anchor or active rate · case 01
The decoded time state disagrees with the explicit regression oracle for coordinate.
Piecewise clock discards continuity anchor or active rate · case 02
The decoded time state disagrees with the explicit regression oracle for coordinate.
Piecewise clock discards continuity anchor or active rate · case 03
The decoded time state disagrees with the explicit regression oracle for coordinate.
Piecewise clock discards continuity anchor or active rate · case 04
The decoded time state disagrees with the explicit regression oracle for coordinate.
Piecewise clock discards continuity anchor or active rate · case 05
The decoded time state disagrees with the explicit regression oracle for coordinate.
Target displacement loses signed future-versus-past meaning · case 01
The decoded time state disagrees with the explicit regression oracle for until.
Target displacement loses signed future-versus-past meaning · case 02
The decoded time state disagrees with the explicit regression oracle for until.
Target displacement loses signed future-versus-past meaning · case 03
The decoded time state disagrees with the explicit regression oracle for until.
Target displacement loses signed future-versus-past meaning · case 04
The decoded time state disagrees with the explicit regression oracle for until.
Target displacement loses signed future-versus-past meaning · case 05
The decoded time state disagrees with the explicit regression oracle for until.
Inverse switched clock uses old origin or multiplies instead of divides rate · case 01
The decoded time state disagrees with the explicit regression oracle for inverse.
Inverse switched clock uses old origin or multiplies instead of divides rate · case 02
The decoded time state disagrees with the explicit regression oracle for inverse.
Inverse switched clock uses old origin or multiplies instead of divides rate · case 03
The decoded time state disagrees with the explicit regression oracle for inverse.
Inverse switched clock uses old origin or multiplies instead of divides rate · case 04
The decoded time state disagrees with the explicit regression oracle for inverse.
Inverse switched clock uses old origin or multiplies instead of divides rate · case 05
The decoded time state disagrees with the explicit regression oracle for inverse.
Clock quality accepts future synchronization or ages from global origin · case 01
The decoded time state disagrees with the explicit regression oracle for age.
Clock quality accepts future synchronization or ages from global origin · case 02
The decoded time state disagrees with the explicit regression oracle for age.
Clock quality accepts future synchronization or ages from global origin · case 03
The decoded time state disagrees with the explicit regression oracle for age.
Clock quality accepts future synchronization or ages from global origin · case 04
The decoded time state disagrees with the explicit regression oracle for age.
Clock quality accepts future synchronization or ages from global origin · case 05
The decoded time state disagrees with the explicit regression oracle for age.
Holdover admission fabricates missing history or admits future sync · case 01
The decoded time state disagrees with the explicit regression oracle for history.
Holdover admission fabricates missing history or admits future sync · case 02
The decoded time state disagrees with the explicit regression oracle for history.
Holdover admission fabricates missing history or admits future sync · case 03
The decoded time state disagrees with the explicit regression oracle for history.
Holdover admission fabricates missing history or admits future sync · case 04
The decoded time state disagrees with the explicit regression oracle for history.
Holdover admission fabricates missing history or admits future sync · case 05
The decoded time state disagrees with the explicit regression oracle for history.
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 ↗