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
Table publication validity uses event time or excludes publication instant · case 01
The decoded time state disagrees with the explicit regression oracle for published.
Table publication validity uses event time or excludes publication instant · case 02
The decoded time state disagrees with the explicit regression oracle for published.
Table publication validity uses event time or excludes publication instant · case 03
The decoded time state disagrees with the explicit regression oracle for published.
Table publication validity uses event time or excludes publication instant · case 04
The decoded time state disagrees with the explicit regression oracle for published.
Table publication validity uses event time or excludes publication instant · case 05
The decoded time state disagrees with the explicit regression oracle for published.
Table expiry follows query timestamp or admits expiration endpoint · case 01
The decoded time state disagrees with the explicit regression oracle for live.
Table expiry follows query timestamp or admits expiration endpoint · case 02
The decoded time state disagrees with the explicit regression oracle for live.
Table expiry follows query timestamp or admits expiration endpoint · case 03
The decoded time state disagrees with the explicit regression oracle for live.
Table expiry follows query timestamp or admits expiration endpoint · case 04
The decoded time state disagrees with the explicit regression oracle for live.
Table expiry follows query timestamp or admits expiration endpoint · case 05
The decoded time state disagrees with the explicit regression oracle for live.
Clock-table coverage assigns effective interval boundaries incorrectly · case 01
The decoded time state disagrees with the explicit regression oracle for covered.
Clock-table coverage assigns effective interval boundaries incorrectly · case 02
The decoded time state disagrees with the explicit regression oracle for covered.
Clock-table coverage assigns effective interval boundaries incorrectly · case 03
The decoded time state disagrees with the explicit regression oracle for covered.
Clock-table coverage assigns effective interval boundaries incorrectly · case 04
The decoded time state disagrees with the explicit regression oracle for covered.
Clock-table coverage assigns effective interval boundaries incorrectly · case 05
The decoded time state disagrees with the explicit regression oracle for covered.
Time conversion bypasses certificate authenticity or freshness gates · case 01
The decoded time state disagrees with the explicit regression oracle for status.
Time conversion bypasses certificate authenticity or freshness gates · case 02
The decoded time state disagrees with the explicit regression oracle for status.
Time conversion bypasses certificate authenticity or freshness gates · case 03
The decoded time state disagrees with the explicit regression oracle for status.
Time conversion bypasses certificate authenticity or freshness gates · case 04
The decoded time state disagrees with the explicit regression oracle for status.
Time conversion bypasses certificate authenticity or freshness gates · case 05
The decoded time state disagrees with the explicit regression oracle for status.
Offset conversion emits untrusted timestamp or reverses declared timescale mapping · case 01
The decoded time state disagrees with the explicit regression oracle for shifted.
Offset conversion emits untrusted timestamp or reverses declared timescale mapping · case 02
The decoded time state disagrees with the explicit regression oracle for shifted.
Offset conversion emits untrusted timestamp or reverses declared timescale mapping · case 03
The decoded time state disagrees with the explicit regression oracle for shifted.
Offset conversion emits untrusted timestamp or reverses declared timescale mapping · case 04
The decoded time state disagrees with the explicit regression oracle for shifted.
Offset conversion emits untrusted timestamp or reverses declared timescale mapping · case 05
The decoded time state disagrees with the explicit regression oracle for shifted.
Certificate lifetime goes negative or is measured at converted event · case 01
The decoded time state disagrees with the explicit regression oracle for remaining.
Certificate lifetime goes negative or is measured at converted event · case 02
The decoded time state disagrees with the explicit regression oracle for remaining.
Certificate lifetime goes negative or is measured at converted event · case 03
The decoded time state disagrees with the explicit regression oracle for remaining.
Certificate lifetime goes negative or is measured at converted event · case 04
The decoded time state disagrees with the explicit regression oracle for remaining.
Certificate lifetime goes negative or is measured at converted event · case 05
The decoded time state disagrees with the explicit regression oracle for remaining.
Coverage margin references publication rather than effective table segment · case 01
The decoded time state disagrees with the explicit regression oracle for left_margin.
Coverage margin references publication rather than effective table segment · case 02
The decoded time state disagrees with the explicit regression oracle for left_margin.
Coverage margin references publication rather than effective table segment · case 03
The decoded time state disagrees with the explicit regression oracle for left_margin.
Coverage margin references publication rather than effective table segment · case 04
The decoded time state disagrees with the explicit regression oracle for left_margin.
Coverage margin references publication rather than effective table segment · case 05
The decoded time state disagrees with the explicit regression oracle for left_margin.
Coverage lookahead references certificate expiry rather than table coverage · case 01
The decoded time state disagrees with the explicit regression oracle for right_margin.
Coverage lookahead references certificate expiry rather than table coverage · case 02
The decoded time state disagrees with the explicit regression oracle for right_margin.
Coverage lookahead references certificate expiry rather than table coverage · case 03
The decoded time state disagrees with the explicit regression oracle for right_margin.
Coverage lookahead references certificate expiry rather than table coverage · case 04
The decoded time state disagrees with the explicit regression oracle for right_margin.
Coverage lookahead references certificate expiry rather than table coverage · case 05
The decoded time state disagrees with the explicit regression oracle for right_margin.
Bidirectional orderly-close controller: open / local eof · case 01
While open, event local_eof produces send_closed/send_two_fins instead of send_closed/send_fin.
Bidirectional orderly-close controller: open / local eof · case 02
While open, event local_eof produces send_closed/send_two_fins instead of send_closed/send_fin.
Bidirectional orderly-close controller: open / local eof · case 03
While open, event local_eof produces send_closed/send_two_fins instead of send_closed/send_fin.
Bidirectional orderly-close controller: open / local eof · case 04
While open, event local_eof produces send_closed/send_two_fins instead of send_closed/send_fin.
Bidirectional orderly-close controller: open / local eof · case 05
While open, event local_eof produces send_closed/send_two_fins instead of send_closed/send_fin.
Bidirectional orderly-close controller: open / remote fin · case 01
While open, event remote_fin produces closed/drop_both instead of receive_closed/ack_fin.
Bidirectional orderly-close controller: open / remote fin · case 02
While open, event remote_fin produces closed/drop_both instead of receive_closed/ack_fin.
Bidirectional orderly-close controller: open / remote fin · case 03
While open, event remote_fin produces closed/drop_both instead of receive_closed/ack_fin.
Bidirectional orderly-close controller: open / remote fin · case 04
While open, event remote_fin produces closed/drop_both instead of receive_closed/ack_fin.
Bidirectional orderly-close controller: open / remote fin · case 05
While open, event remote_fin produces closed/drop_both instead of receive_closed/ack_fin.
Bidirectional orderly-close controller: send closed / fin receipt · case 01
While send_closed, event fin_receipt produces closed/release instead of send_closed/retire_fin.
Bidirectional orderly-close controller: send closed / fin receipt · case 02
While send_closed, event fin_receipt produces closed/release instead of send_closed/retire_fin.
Bidirectional orderly-close controller: send closed / fin receipt · case 03
While send_closed, event fin_receipt produces closed/release instead of send_closed/retire_fin.
Bidirectional orderly-close controller: send closed / fin receipt · case 04
While send_closed, event fin_receipt produces closed/release instead of send_closed/retire_fin.
Bidirectional orderly-close controller: send closed / fin receipt · case 05
While send_closed, event fin_receipt produces closed/release instead of send_closed/retire_fin.
Bidirectional orderly-close controller: receive closed / local data · case 01
While receive_closed, event local_data produces closed/discard instead of receive_closed/send.
Bidirectional orderly-close controller: receive closed / local data · case 02
While receive_closed, event local_data produces closed/discard instead of receive_closed/send.
Bidirectional orderly-close controller: receive closed / local data · case 03
While receive_closed, event local_data produces closed/discard instead of receive_closed/send.
Bidirectional orderly-close controller: receive closed / local data · case 04
While receive_closed, event local_data produces closed/discard instead of receive_closed/send.
Bidirectional orderly-close controller: receive closed / local data · case 05
While receive_closed, event local_data produces closed/discard instead of receive_closed/send.
Bidirectional orderly-close controller: send closed / remote fin · case 01
While send_closed, event remote_fin produces closed/release instead of closing/ack_fin.
Bidirectional orderly-close controller: send closed / remote fin · case 02
While send_closed, event remote_fin produces closed/release instead of closing/ack_fin.
Bidirectional orderly-close controller: send closed / remote fin · case 03
While send_closed, event remote_fin produces closed/release instead of closing/ack_fin.
Bidirectional orderly-close controller: send closed / remote fin · case 04
While send_closed, event remote_fin produces closed/release instead of closing/ack_fin.
Bidirectional orderly-close controller: send closed / remote fin · case 05
While send_closed, event remote_fin produces closed/release instead of closing/ack_fin.
Bidirectional orderly-close controller: receive closed / local eof · case 01
While receive_closed, event local_eof produces closed/release instead of closing/send_fin.
Bidirectional orderly-close controller: receive closed / local eof · case 02
While receive_closed, event local_eof produces closed/release instead of closing/send_fin.
Bidirectional orderly-close controller: receive closed / local eof · case 03
While receive_closed, event local_eof produces closed/release instead of closing/send_fin.
Bidirectional orderly-close controller: receive closed / local eof · case 04
While receive_closed, event local_eof produces closed/release instead of closing/send_fin.
Bidirectional orderly-close controller: receive closed / local eof · case 05
While receive_closed, event local_eof produces closed/release instead of closing/send_fin.
Bidirectional orderly-close controller: closing / fin confirmed · case 01
While closing, event fin_confirmed produces closing/wait instead of closed/release.
Bidirectional orderly-close controller: closing / fin confirmed · case 02
While closing, event fin_confirmed produces closing/wait instead of closed/release.
Bidirectional orderly-close controller: closing / fin confirmed · case 03
While closing, event fin_confirmed produces closing/wait instead of closed/release.
Bidirectional orderly-close controller: closing / fin confirmed · case 04
While closing, event fin_confirmed produces closing/wait instead of closed/release.
Bidirectional orderly-close controller: closing / fin confirmed · case 05
While closing, event fin_confirmed produces closing/wait instead of closed/release.
Bidirectional orderly-close controller: closed / late data · case 01
While closed, event late_data produces open/deliver instead of closed/reject.
Bidirectional orderly-close controller: closed / late data · case 02
While closed, event late_data produces open/deliver instead of closed/reject.
Bidirectional orderly-close controller: closed / late data · case 03
While closed, event late_data produces open/deliver instead of closed/reject.
Bidirectional orderly-close controller: closed / late data · case 04
While closed, event late_data produces open/deliver instead of closed/reject.
Bidirectional orderly-close controller: closed / late data · case 05
While closed, event late_data produces open/deliver instead of closed/reject.
Bidirectional orderly-close controller: send closed / local data · case 01
While send_closed, event local_data produces send_closed/send instead of send_closed/reject.
Bidirectional orderly-close controller: send closed / local data · case 02
While send_closed, event local_data produces send_closed/send instead of send_closed/reject.
Bidirectional orderly-close controller: send closed / local data · case 03
While send_closed, event local_data produces send_closed/send instead of send_closed/reject.
Bidirectional orderly-close controller: send closed / local data · case 04
While send_closed, event local_data produces send_closed/send instead of send_closed/reject.
Bidirectional orderly-close controller: send closed / local data · case 05
While send_closed, event local_data produces send_closed/send instead of send_closed/reject.
Bidirectional orderly-close controller: receive closed / remote data · case 01
While receive_closed, event remote_data produces receive_closed/deliver instead of receive_closed/reject.
Bidirectional orderly-close controller: receive closed / remote data · case 02
While receive_closed, event remote_data produces receive_closed/deliver instead of receive_closed/reject.
Bidirectional orderly-close controller: receive closed / remote data · case 03
While receive_closed, event remote_data produces receive_closed/deliver instead of receive_closed/reject.
Bidirectional orderly-close controller: receive closed / remote data · case 04
While receive_closed, event remote_data produces receive_closed/deliver instead of receive_closed/reject.
Bidirectional orderly-close controller: receive closed / remote data · case 05
While receive_closed, event remote_data produces receive_closed/deliver instead of receive_closed/reject.
Capability-offer negotiation controller: fresh / offer · case 01
While fresh, event offer produces active/enable instead of offered/advertise.
Capability-offer negotiation controller: fresh / offer · case 02
While fresh, event offer produces active/enable instead of offered/advertise.
Capability-offer negotiation controller: fresh / offer · case 03
While fresh, event offer produces active/enable instead of offered/advertise.
Capability-offer negotiation controller: fresh / offer · case 04
While fresh, event offer produces active/enable instead of offered/advertise.
Capability-offer negotiation controller: fresh / offer · case 05
While fresh, event offer produces active/enable instead of offered/advertise.
Capability-offer negotiation controller: offered / subset accept · case 01
While offered, event subset_accept produces active/enable_all instead of active/enable_subset.
Capability-offer negotiation controller: offered / subset accept · case 02
While offered, event subset_accept produces active/enable_all instead of active/enable_subset.
Capability-offer negotiation controller: offered / subset accept · case 03
While offered, event subset_accept produces active/enable_all instead of active/enable_subset.
Capability-offer negotiation controller: offered / subset accept · case 04
While offered, event subset_accept produces active/enable_all instead of active/enable_subset.
Capability-offer negotiation controller: offered / subset accept · case 05
While offered, event subset_accept produces active/enable_all instead of active/enable_subset.
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 ↗