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
Split timestamp admits unnormalized fraction endpoint · case 01
The decoded time state disagrees with the explicit regression oracle for fraction_ok.
Split timestamp admits unnormalized fraction endpoint · case 02
The decoded time state disagrees with the explicit regression oracle for fraction_ok.
Split timestamp admits unnormalized fraction endpoint · case 03
The decoded time state disagrees with the explicit regression oracle for fraction_ok.
Split timestamp admits unnormalized fraction endpoint · case 04
The decoded time state disagrees with the explicit regression oracle for fraction_ok.
Split timestamp admits unnormalized fraction endpoint · case 05
The decoded time state disagrees with the explicit regression oracle for fraction_ok.
Already-UTC migration admits redundant offset metadata · case 01
The decoded time state disagrees with the explicit regression oracle for offset_ok.
Already-UTC migration admits redundant offset metadata · case 02
The decoded time state disagrees with the explicit regression oracle for offset_ok.
Already-UTC migration admits redundant offset metadata · case 03
The decoded time state disagrees with the explicit regression oracle for offset_ok.
Already-UTC migration admits redundant offset metadata · case 04
The decoded time state disagrees with the explicit regression oracle for offset_ok.
Already-UTC migration admits redundant offset metadata · case 05
The decoded time state disagrees with the explicit regression oracle for offset_ok.
Migration admits negative uncertainty or rejects an exact timestamp · case 01
The decoded time state disagrees with the explicit regression oracle for valid.
Migration admits negative uncertainty or rejects an exact timestamp · case 02
The decoded time state disagrees with the explicit regression oracle for valid.
Migration admits negative uncertainty or rejects an exact timestamp · case 03
The decoded time state disagrees with the explicit regression oracle for valid.
Migration admits negative uncertainty or rejects an exact timestamp · case 04
The decoded time state disagrees with the explicit regression oracle for valid.
Migration admits negative uncertainty or rejects an exact timestamp · case 05
The decoded time state disagrees with the explicit regression oracle for valid.
Timestamp migration treats legacy milliseconds as seconds or reverses fractional part · case 01
The decoded time state disagrees with the explicit regression oracle for nanoseconds.
Timestamp migration treats legacy milliseconds as seconds or reverses fractional part · case 02
The decoded time state disagrees with the explicit regression oracle for nanoseconds.
Timestamp migration treats legacy milliseconds as seconds or reverses fractional part · case 03
The decoded time state disagrees with the explicit regression oracle for nanoseconds.
Timestamp migration treats legacy milliseconds as seconds or reverses fractional part · case 04
The decoded time state disagrees with the explicit regression oracle for nanoseconds.
Timestamp migration treats legacy milliseconds as seconds or reverses fractional part · case 05
The decoded time state disagrees with the explicit regression oracle for nanoseconds.
Migration converts point coordinate but leaves error in source units · case 01
The decoded time state disagrees with the explicit regression oracle for uncertainty.
Migration converts point coordinate but leaves error in source units · case 02
The decoded time state disagrees with the explicit regression oracle for uncertainty.
Migration converts point coordinate but leaves error in source units · case 03
The decoded time state disagrees with the explicit regression oracle for uncertainty.
Migration converts point coordinate but leaves error in source units · case 04
The decoded time state disagrees with the explicit regression oracle for uncertainty.
Migration converts point coordinate but leaves error in source units · case 05
The decoded time state disagrees with the explicit regression oracle for uncertainty.
Legacy migration lets irrelevant fraction or uncertainty metadata shift epoch second · case 01
The decoded time state disagrees with the explicit regression oracle for seconds.
Legacy migration lets irrelevant fraction or uncertainty metadata shift epoch second · case 02
The decoded time state disagrees with the explicit regression oracle for seconds.
Legacy migration lets irrelevant fraction or uncertainty metadata shift epoch second · case 03
The decoded time state disagrees with the explicit regression oracle for seconds.
Legacy migration lets irrelevant fraction or uncertainty metadata shift epoch second · case 04
The decoded time state disagrees with the explicit regression oracle for seconds.
Legacy migration lets irrelevant fraction or uncertainty metadata shift epoch second · case 05
The decoded time state disagrees with the explicit regression oracle for seconds.
Migrated fraction uses legacy modulus or magnitude residue · case 01
The decoded time state disagrees with the explicit regression oracle for remainder.
Migrated fraction uses legacy modulus or magnitude residue · case 02
The decoded time state disagrees with the explicit regression oracle for remainder.
Migrated fraction uses legacy modulus or magnitude residue · case 03
The decoded time state disagrees with the explicit regression oracle for remainder.
Migrated fraction uses legacy modulus or magnitude residue · case 04
The decoded time state disagrees with the explicit regression oracle for remainder.
Migrated fraction uses legacy modulus or magnitude residue · case 05
The decoded time state disagrees with the explicit regression oracle for remainder.
Migration drops original precision provenance · case 01
The decoded time state disagrees with the explicit regression oracle for precision.
Migration drops original precision provenance · case 02
The decoded time state disagrees with the explicit regression oracle for precision.
Migration drops original precision provenance · case 03
The decoded time state disagrees with the explicit regression oracle for precision.
Migration drops original precision provenance · case 04
The decoded time state disagrees with the explicit regression oracle for precision.
Migration drops original precision provenance · case 05
The decoded time state disagrees with the explicit regression oracle for precision.
Converter reset retains prior fractional epoch or every step discards it · case 01
The decoded time state disagrees with the explicit regression oracle for old_residue.
Converter reset retains prior fractional epoch or every step discards it · case 02
The decoded time state disagrees with the explicit regression oracle for old_residue.
Converter reset retains prior fractional epoch or every step discards it · case 03
The decoded time state disagrees with the explicit regression oracle for old_residue.
Converter reset retains prior fractional epoch or every step discards it · case 04
The decoded time state disagrees with the explicit regression oracle for old_residue.
Converter reset retains prior fractional epoch or every step discards it · case 05
The decoded time state disagrees with the explicit regression oracle for old_residue.
Tick converter uses denominator as scale or assumes one-to-one input rate · case 01
The decoded time state disagrees with the explicit regression oracle for scaled.
Tick converter uses denominator as scale or assumes one-to-one input rate · case 02
The decoded time state disagrees with the explicit regression oracle for scaled.
Tick converter uses denominator as scale or assumes one-to-one input rate · case 03
The decoded time state disagrees with the explicit regression oracle for scaled.
Tick converter uses denominator as scale or assumes one-to-one input rate · case 04
The decoded time state disagrees with the explicit regression oracle for scaled.
Tick converter uses denominator as scale or assumes one-to-one input rate · case 05
The decoded time state disagrees with the explicit regression oracle for scaled.
Tick residue is discarded or rescaled a second time · case 01
The decoded time state disagrees with the explicit regression oracle for accumulated.
Tick residue is discarded or rescaled a second time · case 02
The decoded time state disagrees with the explicit regression oracle for accumulated.
Tick residue is discarded or rescaled a second time · case 03
The decoded time state disagrees with the explicit regression oracle for accumulated.
Tick residue is discarded or rescaled a second time · case 04
The decoded time state disagrees with the explicit regression oracle for accumulated.
Tick residue is discarded or rescaled a second time · case 05
The decoded time state disagrees with the explicit regression oracle for accumulated.
Tick emission rounds up before enough fractional time accumulates · case 01
The decoded time state disagrees with the explicit regression oracle for emitted.
Tick emission rounds up before enough fractional time accumulates · case 02
The decoded time state disagrees with the explicit regression oracle for emitted.
Tick emission rounds up before enough fractional time accumulates · case 03
The decoded time state disagrees with the explicit regression oracle for emitted.
Tick emission rounds up before enough fractional time accumulates · case 04
The decoded time state disagrees with the explicit regression oracle for emitted.
Tick emission rounds up before enough fractional time accumulates · case 05
The decoded time state disagrees with the explicit regression oracle for emitted.
Tick residue is reduced in source scale or lost after emission · case 01
The decoded time state disagrees with the explicit regression oracle for residue.
Tick residue is reduced in source scale or lost after emission · case 02
The decoded time state disagrees with the explicit regression oracle for residue.
Tick residue is reduced in source scale or lost after emission · case 03
The decoded time state disagrees with the explicit regression oracle for residue.
Tick residue is reduced in source scale or lost after emission · case 04
The decoded time state disagrees with the explicit regression oracle for residue.
Tick residue is reduced in source scale or lost after emission · case 05
The decoded time state disagrees with the explicit regression oracle for residue.
Timebase reset retains cumulative target history or clears it every step · case 01
The decoded time state disagrees with the explicit regression oracle for old_target.
Timebase reset retains cumulative target history or clears it every step · case 02
The decoded time state disagrees with the explicit regression oracle for old_target.
Timebase reset retains cumulative target history or clears it every step · case 03
The decoded time state disagrees with the explicit regression oracle for old_target.
Timebase reset retains cumulative target history or clears it every step · case 04
The decoded time state disagrees with the explicit regression oracle for old_target.
Timebase reset retains cumulative target history or clears it every step · case 05
The decoded time state disagrees with the explicit regression oracle for old_target.
Cumulative target uses raw numerator instead of emitted ticks · case 01
The decoded time state disagrees with the explicit regression oracle for target.
Cumulative target uses raw numerator instead of emitted ticks · case 02
The decoded time state disagrees with the explicit regression oracle for target.
Cumulative target uses raw numerator instead of emitted ticks · case 03
The decoded time state disagrees with the explicit regression oracle for target.
Cumulative target uses raw numerator instead of emitted ticks · case 04
The decoded time state disagrees with the explicit regression oracle for target.
Cumulative target uses raw numerator instead of emitted ticks · case 05
The decoded time state disagrees with the explicit regression oracle for target.
Timebase coordinate loses or rescales target-domain origin · case 01
The decoded time state disagrees with the explicit regression oracle for coordinate.
Timebase coordinate loses or rescales target-domain origin · case 02
The decoded time state disagrees with the explicit regression oracle for coordinate.
Timebase coordinate loses or rescales target-domain origin · case 03
The decoded time state disagrees with the explicit regression oracle for coordinate.
Timebase coordinate loses or rescales target-domain origin · case 04
The decoded time state disagrees with the explicit regression oracle for coordinate.
Timebase coordinate loses or rescales target-domain origin · case 05
The decoded time state disagrees with the explicit regression oracle for coordinate.
Unrounded timestamp drops residue or gives it wrong unit denominator · case 01
The decoded time state disagrees with the explicit regression oracle for exact.
Unrounded timestamp drops residue or gives it wrong unit denominator · case 02
The decoded time state disagrees with the explicit regression oracle for exact.
Unrounded timestamp drops residue or gives it wrong unit denominator · case 03
The decoded time state disagrees with the explicit regression oracle for exact.
Unrounded timestamp drops residue or gives it wrong unit denominator · case 04
The decoded time state disagrees with the explicit regression oracle for exact.
Unrounded timestamp drops residue or gives it wrong unit denominator · case 05
The decoded time state disagrees with the explicit regression oracle for exact.
Subtick status is derived from emitted count instead of retained fraction · case 01
The decoded time state disagrees with the explicit regression oracle for needs_tick.
Subtick status is derived from emitted count instead of retained fraction · case 02
The decoded time state disagrees with the explicit regression oracle for needs_tick.
Subtick status is derived from emitted count instead of retained fraction · case 03
The decoded time state disagrees with the explicit regression oracle for needs_tick.
Subtick status is derived from emitted count instead of retained fraction · case 04
The decoded time state disagrees with the explicit regression oracle for needs_tick.
Subtick status is derived from emitted count instead of retained fraction · case 05
The decoded time state disagrees with the explicit regression oracle for needs_tick.
Atomic offset step applies one tick late or before its effective instant · case 01
The decoded time state disagrees with the explicit regression oracle for active_offset.
Atomic offset step applies one tick late or before its effective instant · case 02
The decoded time state disagrees with the explicit regression oracle for active_offset.
Atomic offset step applies one tick late or before its effective instant · case 03
The decoded time state disagrees with the explicit regression oracle for active_offset.
Atomic offset step applies one tick late or before its effective instant · case 04
The decoded time state disagrees with the explicit regression oracle for active_offset.
Atomic offset step applies one tick late or before its effective instant · case 05
The decoded time state disagrees with the explicit regression oracle for active_offset.
Atomic-to-civil conversion reverses declared offset or freezes initial table · case 01
The decoded time state disagrees with the explicit regression oracle for label.
Atomic-to-civil conversion reverses declared offset or freezes initial table · case 02
The decoded time state disagrees with the explicit regression oracle for label.
Atomic-to-civil conversion reverses declared offset or freezes initial table · case 03
The decoded time state disagrees with the explicit regression oracle for label.
Atomic-to-civil conversion reverses declared offset or freezes initial table · case 04
The decoded time state disagrees with the explicit regression oracle for label.
Atomic-to-civil conversion reverses declared offset or freezes initial table · case 05
The decoded time state disagrees with the explicit regression oracle for label.
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 ↗