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
Exchange delay normalization hides physically impossible negative propagation · case 01
The decoded time state disagrees with the explicit regression oracle for round_trip.
Exchange delay normalization hides physically impossible negative propagation · case 02
The decoded time state disagrees with the explicit regression oracle for round_trip.
Exchange delay normalization hides physically impossible negative propagation · case 03
The decoded time state disagrees with the explicit regression oracle for round_trip.
Exchange delay normalization hides physically impossible negative propagation · case 04
The decoded time state disagrees with the explicit regression oracle for round_trip.
Exchange delay normalization hides physically impossible negative propagation · case 05
The decoded time state disagrees with the explicit regression oracle for round_trip.
Earliest offset bound uses receive rather than server-send causality · case 01
The decoded time state disagrees with the explicit regression oracle for offset_low.
Earliest offset bound uses receive rather than server-send causality · case 02
The decoded time state disagrees with the explicit regression oracle for offset_low.
Earliest offset bound uses receive rather than server-send causality · case 03
The decoded time state disagrees with the explicit regression oracle for offset_low.
Earliest offset bound uses receive rather than server-send causality · case 04
The decoded time state disagrees with the explicit regression oracle for offset_low.
Earliest offset bound uses receive rather than server-send causality · case 05
The decoded time state disagrees with the explicit regression oracle for offset_low.
Latest offset bound uses send rather than server-receive causality · case 01
The decoded time state disagrees with the explicit regression oracle for offset_high.
Latest offset bound uses send rather than server-receive causality · case 02
The decoded time state disagrees with the explicit regression oracle for offset_high.
Latest offset bound uses send rather than server-receive causality · case 03
The decoded time state disagrees with the explicit regression oracle for offset_high.
Latest offset bound uses send rather than server-receive causality · case 04
The decoded time state disagrees with the explicit regression oracle for offset_high.
Latest offset bound uses send rather than server-receive causality · case 05
The decoded time state disagrees with the explicit regression oracle for offset_high.
Clock offset estimator uses interval radius or discards half tick · case 01
The decoded time state disagrees with the explicit regression oracle for offset.
Clock offset estimator uses interval radius or discards half tick · case 02
The decoded time state disagrees with the explicit regression oracle for offset.
Clock offset estimator uses interval radius or discards half tick · case 03
The decoded time state disagrees with the explicit regression oracle for offset.
Clock offset estimator uses interval radius or discards half tick · case 04
The decoded time state disagrees with the explicit regression oracle for offset.
Clock offset estimator uses interval radius or discards half tick · case 05
The decoded time state disagrees with the explicit regression oracle for offset.
Server-time projection uses reversed offset or stale exchange instant · case 01
The decoded time state disagrees with the explicit regression oracle for projected.
Server-time projection uses reversed offset or stale exchange instant · case 02
The decoded time state disagrees with the explicit regression oracle for projected.
Server-time projection uses reversed offset or stale exchange instant · case 03
The decoded time state disagrees with the explicit regression oracle for projected.
Server-time projection uses reversed offset or stale exchange instant · case 04
The decoded time state disagrees with the explicit regression oracle for projected.
Server-time projection uses reversed offset or stale exchange instant · case 05
The decoded time state disagrees with the explicit regression oracle for projected.
One-way propagation estimate includes service delay or truncates odd tick · case 01
The decoded time state disagrees with the explicit regression oracle for one_way.
One-way propagation estimate includes service delay or truncates odd tick · case 02
The decoded time state disagrees with the explicit regression oracle for one_way.
One-way propagation estimate includes service delay or truncates odd tick · case 03
The decoded time state disagrees with the explicit regression oracle for one_way.
One-way propagation estimate includes service delay or truncates odd tick · case 04
The decoded time state disagrees with the explicit regression oracle for one_way.
One-way propagation estimate includes service delay or truncates odd tick · case 05
The decoded time state disagrees with the explicit regression oracle for one_way.
Exchange validity admits impossible negative propagation or rejects zero delay · case 01
The decoded time state disagrees with the explicit regression oracle for valid.
Exchange validity admits impossible negative propagation or rejects zero delay · case 02
The decoded time state disagrees with the explicit regression oracle for valid.
Exchange validity admits impossible negative propagation or rejects zero delay · case 03
The decoded time state disagrees with the explicit regression oracle for valid.
Exchange validity admits impossible negative propagation or rejects zero delay · case 04
The decoded time state disagrees with the explicit regression oracle for valid.
Exchange validity admits impossible negative propagation or rejects zero delay · case 05
The decoded time state disagrees with the explicit regression oracle for valid.
Clock error radius is confused with offset center or full round trip · case 01
The decoded time state disagrees with the explicit regression oracle for uncertainty.
Clock error radius is confused with offset center or full round trip · case 02
The decoded time state disagrees with the explicit regression oracle for uncertainty.
Clock error radius is confused with offset center or full round trip · case 03
The decoded time state disagrees with the explicit regression oracle for uncertainty.
Clock error radius is confused with offset center or full round trip · case 04
The decoded time state disagrees with the explicit regression oracle for uncertainty.
Clock error radius is confused with offset center or full round trip · case 05
The decoded time state disagrees with the explicit regression oracle for uncertainty.
Hybrid receive drops remote or local physical history · case 01
The decoded time state disagrees with the explicit regression oracle for physical.
Hybrid receive drops remote or local physical history · case 02
The decoded time state disagrees with the explicit regression oracle for physical.
Hybrid receive drops remote or local physical history · case 03
The decoded time state disagrees with the explicit regression oracle for physical.
Hybrid receive drops remote or local physical history · case 04
The decoded time state disagrees with the explicit regression oracle for physical.
Hybrid receive drops remote or local physical history · case 05
The decoded time state disagrees with the explicit regression oracle for physical.
Logical ownership treats older local physical state as current · case 01
The decoded time state disagrees with the explicit regression oracle for local_owns.
Logical ownership treats older local physical state as current · case 02
The decoded time state disagrees with the explicit regression oracle for local_owns.
Logical ownership treats older local physical state as current · case 03
The decoded time state disagrees with the explicit regression oracle for local_owns.
Logical ownership treats older local physical state as current · case 04
The decoded time state disagrees with the explicit regression oracle for local_owns.
Logical ownership treats older local physical state as current · case 05
The decoded time state disagrees with the explicit regression oracle for local_owns.
Remote logical ownership ignores exact physical equality · case 01
The decoded time state disagrees with the explicit regression oracle for remote_owns.
Remote logical ownership ignores exact physical equality · case 02
The decoded time state disagrees with the explicit regression oracle for remote_owns.
Remote logical ownership ignores exact physical equality · case 03
The decoded time state disagrees with the explicit regression oracle for remote_owns.
Remote logical ownership ignores exact physical equality · case 04
The decoded time state disagrees with the explicit regression oracle for remote_owns.
Remote logical ownership ignores exact physical equality · case 05
The decoded time state disagrees with the explicit regression oracle for remote_owns.
Hybrid receive increments logical counter when wall alone advanced · case 01
The decoded time state disagrees with the explicit regression oracle for logical.
Hybrid receive increments logical counter when wall alone advanced · case 02
The decoded time state disagrees with the explicit regression oracle for logical.
Hybrid receive increments logical counter when wall alone advanced · case 03
The decoded time state disagrees with the explicit regression oracle for logical.
Hybrid receive increments logical counter when wall alone advanced · case 04
The decoded time state disagrees with the explicit regression oracle for logical.
Hybrid receive increments logical counter when wall alone advanced · case 05
The decoded time state disagrees with the explicit regression oracle for logical.
Hybrid logical carry uses the largest label rather than counter capacity · case 01
The decoded time state disagrees with the explicit regression oracle for carry.
Hybrid logical carry uses the largest label rather than counter capacity · case 02
The decoded time state disagrees with the explicit regression oracle for carry.
Hybrid logical carry uses the largest label rather than counter capacity · case 03
The decoded time state disagrees with the explicit regression oracle for carry.
Hybrid logical carry uses the largest label rather than counter capacity · case 04
The decoded time state disagrees with the explicit regression oracle for carry.
Hybrid logical carry uses the largest label rather than counter capacity · case 05
The decoded time state disagrees with the explicit regression oracle for carry.
Hybrid counter carry is dropped or adds all logical ticks to physical time · case 01
The decoded time state disagrees with the explicit regression oracle for normalized_p.
Hybrid counter carry is dropped or adds all logical ticks to physical time · case 02
The decoded time state disagrees with the explicit regression oracle for normalized_p.
Hybrid counter carry is dropped or adds all logical ticks to physical time · case 03
The decoded time state disagrees with the explicit regression oracle for normalized_p.
Hybrid counter carry is dropped or adds all logical ticks to physical time · case 04
The decoded time state disagrees with the explicit regression oracle for normalized_p.
Hybrid counter carry is dropped or adds all logical ticks to physical time · case 05
The decoded time state disagrees with the explicit regression oracle for normalized_p.
Hybrid logical component overflows or saturates instead of carrying · case 01
The decoded time state disagrees with the explicit regression oracle for normalized_l.
Hybrid logical component overflows or saturates instead of carrying · case 02
The decoded time state disagrees with the explicit regression oracle for normalized_l.
Hybrid logical component overflows or saturates instead of carrying · case 03
The decoded time state disagrees with the explicit regression oracle for normalized_l.
Hybrid logical component overflows or saturates instead of carrying · case 04
The decoded time state disagrees with the explicit regression oracle for normalized_l.
Hybrid logical component overflows or saturates instead of carrying · case 05
The decoded time state disagrees with the explicit regression oracle for normalized_l.
Clock-source provenance collapses source bits or omits wall source · case 01
The decoded time state disagrees with the explicit regression oracle for mask.
Clock-source provenance collapses source bits or omits wall source · case 02
The decoded time state disagrees with the explicit regression oracle for mask.
Clock-source provenance collapses source bits or omits wall source · case 03
The decoded time state disagrees with the explicit regression oracle for mask.
Clock-source provenance collapses source bits or omits wall source · case 04
The decoded time state disagrees with the explicit regression oracle for mask.
Clock-source provenance collapses source bits or omits wall source · case 05
The decoded time state disagrees with the explicit regression oracle for mask.
Local hybrid ordering compares only one timestamp component · case 01
The decoded time state disagrees with the explicit regression oracle for after_local.
Local hybrid ordering compares only one timestamp component · case 02
The decoded time state disagrees with the explicit regression oracle for after_local.
Local hybrid ordering compares only one timestamp component · case 03
The decoded time state disagrees with the explicit regression oracle for after_local.
Local hybrid ordering compares only one timestamp component · case 04
The decoded time state disagrees with the explicit regression oracle for after_local.
Local hybrid ordering compares only one timestamp component · case 05
The decoded time state disagrees with the explicit regression oracle for after_local.
Remote hybrid ordering discards lexicographic physical precedence · case 01
The decoded time state disagrees with the explicit regression oracle for after_remote.
Remote hybrid ordering discards lexicographic physical precedence · case 02
The decoded time state disagrees with the explicit regression oracle for after_remote.
Remote hybrid ordering discards lexicographic physical precedence · case 03
The decoded time state disagrees with the explicit regression oracle for after_remote.
Remote hybrid ordering discards lexicographic physical precedence · case 04
The decoded time state disagrees with the explicit regression oracle for after_remote.
Remote hybrid ordering discards lexicographic physical precedence · case 05
The decoded time state disagrees with the explicit regression oracle for after_remote.
Clock bridge reuses calibration from a different boot · case 01
The decoded time state disagrees with the explicit regression oracle for boot_ok.
Clock bridge reuses calibration from a different boot · case 02
The decoded time state disagrees with the explicit regression oracle for boot_ok.
Clock bridge reuses calibration from a different boot · case 03
The decoded time state disagrees with the explicit regression oracle for boot_ok.
Clock bridge reuses calibration from a different boot · case 04
The decoded time state disagrees with the explicit regression oracle for boot_ok.
Clock bridge reuses calibration from a different boot · case 05
The decoded time state disagrees with the explicit regression oracle for boot_ok.
Clock bridge applies calibration from another rate generation · case 01
The decoded time state disagrees with the explicit regression oracle for generation_ok.
Clock bridge applies calibration from another rate generation · case 02
The decoded time state disagrees with the explicit regression oracle for generation_ok.
Clock bridge applies calibration from another rate generation · case 03
The decoded time state disagrees with the explicit regression oracle for generation_ok.
Clock bridge applies calibration from another rate generation · case 04
The decoded time state disagrees with the explicit regression oracle for generation_ok.
Clock bridge applies calibration from another rate generation · case 05
The decoded time state disagrees with the explicit regression oracle for generation_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 ↗