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
Two-party resource reservation controller: tentative / decline · case 01
While tentative, event decline produces reserved/commit_hold instead of free/release_hold.
Two-party resource reservation controller: tentative / decline · case 02
While tentative, event decline produces reserved/commit_hold instead of free/release_hold.
Two-party resource reservation controller: tentative / decline · case 03
While tentative, event decline produces reserved/commit_hold instead of free/release_hold.
Two-party resource reservation controller: tentative / decline · case 04
While tentative, event decline produces reserved/commit_hold instead of free/release_hold.
Two-party resource reservation controller: tentative / decline · case 05
While tentative, event decline produces reserved/commit_hold instead of free/release_hold.
Two-party resource reservation controller: tentative / hold expired · case 01
While tentative, event hold_expired produces reserved/confirm instead of free/notify_expired.
Two-party resource reservation controller: tentative / hold expired · case 02
While tentative, event hold_expired produces reserved/confirm instead of free/notify_expired.
Two-party resource reservation controller: tentative / hold expired · case 03
While tentative, event hold_expired produces reserved/confirm instead of free/notify_expired.
Two-party resource reservation controller: tentative / hold expired · case 04
While tentative, event hold_expired produces reserved/confirm instead of free/notify_expired.
Two-party resource reservation controller: tentative / hold expired · case 05
While tentative, event hold_expired produces reserved/confirm instead of free/notify_expired.
Two-party resource reservation controller: reserved / use · case 01
While reserved, event use produces free/release instead of in_use/start_use.
Two-party resource reservation controller: reserved / use · case 02
While reserved, event use produces free/release instead of in_use/start_use.
Two-party resource reservation controller: reserved / use · case 03
While reserved, event use produces free/release instead of in_use/start_use.
Two-party resource reservation controller: reserved / use · case 04
While reserved, event use produces free/release instead of in_use/start_use.
Two-party resource reservation controller: reserved / use · case 05
While reserved, event use produces free/release instead of in_use/start_use.
Two-party resource reservation controller: in use / finish · case 01
While in_use, event finish produces reserved/keep instead of free/release_and_receipt.
Two-party resource reservation controller: in use / finish · case 02
While in_use, event finish produces reserved/keep instead of free/release_and_receipt.
Two-party resource reservation controller: in use / finish · case 03
While in_use, event finish produces reserved/keep instead of free/release_and_receipt.
Two-party resource reservation controller: in use / finish · case 04
While in_use, event finish produces reserved/keep instead of free/release_and_receipt.
Two-party resource reservation controller: in use / finish · case 05
While in_use, event finish produces reserved/keep instead of free/release_and_receipt.
Two-party resource reservation controller: reserved / cancel · case 01
While reserved, event cancel produces reserved/keep instead of free/release_and_cancel_ack.
Two-party resource reservation controller: reserved / cancel · case 02
While reserved, event cancel produces reserved/keep instead of free/release_and_cancel_ack.
Two-party resource reservation controller: reserved / cancel · case 03
While reserved, event cancel produces reserved/keep instead of free/release_and_cancel_ack.
Two-party resource reservation controller: reserved / cancel · case 04
While reserved, event cancel produces reserved/keep instead of free/release_and_cancel_ack.
Two-party resource reservation controller: reserved / cancel · case 05
While reserved, event cancel produces reserved/keep instead of free/release_and_cancel_ack.
Two-party resource reservation controller: free / confirm · case 01
While free, event confirm produces reserved/allocate instead of free/reject_expired.
Two-party resource reservation controller: free / confirm · case 02
While free, event confirm produces reserved/allocate instead of free/reject_expired.
Two-party resource reservation controller: free / confirm · case 03
While free, event confirm produces reserved/allocate instead of free/reject_expired.
Two-party resource reservation controller: free / confirm · case 04
While free, event confirm produces reserved/allocate instead of free/reject_expired.
Two-party resource reservation controller: free / confirm · case 05
While free, event confirm produces reserved/allocate instead of free/reject_expired.
Two-party resource reservation controller: in use / cancel · case 01
While in_use, event cancel produces free/release instead of in_use/reject_busy.
Two-party resource reservation controller: in use / cancel · case 02
While in_use, event cancel produces free/release instead of in_use/reject_busy.
Two-party resource reservation controller: in use / cancel · case 03
While in_use, event cancel produces free/release instead of in_use/reject_busy.
Two-party resource reservation controller: in use / cancel · case 04
While in_use, event cancel produces free/release instead of in_use/reject_busy.
Two-party resource reservation controller: in use / cancel · case 05
While in_use, event cancel produces free/release instead of in_use/reject_busy.
Two-party resource reservation controller: reserved / duplicate confirm · case 01
While reserved, event duplicate_confirm produces reserved/allocate_second instead of reserved/repeat_receipt.
Two-party resource reservation controller: reserved / duplicate confirm · case 02
While reserved, event duplicate_confirm produces reserved/allocate_second instead of reserved/repeat_receipt.
Two-party resource reservation controller: reserved / duplicate confirm · case 03
While reserved, event duplicate_confirm produces reserved/allocate_second instead of reserved/repeat_receipt.
Two-party resource reservation controller: reserved / duplicate confirm · case 04
While reserved, event duplicate_confirm produces reserved/allocate_second instead of reserved/repeat_receipt.
Two-party resource reservation controller: reserved / duplicate confirm · case 05
While reserved, event duplicate_confirm produces reserved/allocate_second instead of reserved/repeat_receipt.
Application liveness challenge controller: quiet / probe due · case 01
While quiet, event probe_due produces healthy/report_alive instead of awaiting/send_challenge.
Application liveness challenge controller: quiet / probe due · case 02
While quiet, event probe_due produces healthy/report_alive instead of awaiting/send_challenge.
Application liveness challenge controller: quiet / probe due · case 03
While quiet, event probe_due produces healthy/report_alive instead of awaiting/send_challenge.
Application liveness challenge controller: quiet / probe due · case 04
While quiet, event probe_due produces healthy/report_alive instead of awaiting/send_challenge.
Application liveness challenge controller: quiet / probe due · case 05
While quiet, event probe_due produces healthy/report_alive instead of awaiting/send_challenge.
Application liveness challenge controller: awaiting / matching response · case 01
While awaiting, event matching_response produces awaiting/wait instead of healthy/record_roundtrip.
Application liveness challenge controller: awaiting / matching response · case 02
While awaiting, event matching_response produces awaiting/wait instead of healthy/record_roundtrip.
Application liveness challenge controller: awaiting / matching response · case 03
While awaiting, event matching_response produces awaiting/wait instead of healthy/record_roundtrip.
Application liveness challenge controller: awaiting / matching response · case 04
While awaiting, event matching_response produces awaiting/wait instead of healthy/record_roundtrip.
Application liveness challenge controller: awaiting / matching response · case 05
While awaiting, event matching_response produces awaiting/wait instead of healthy/record_roundtrip.
Application liveness challenge controller: awaiting / wrong response · case 01
While awaiting, event wrong_response produces healthy/record_roundtrip instead of awaiting/ignore_unmatched.
Application liveness challenge controller: awaiting / wrong response · case 02
While awaiting, event wrong_response produces healthy/record_roundtrip instead of awaiting/ignore_unmatched.
Application liveness challenge controller: awaiting / wrong response · case 03
While awaiting, event wrong_response produces healthy/record_roundtrip instead of awaiting/ignore_unmatched.
Application liveness challenge controller: awaiting / wrong response · case 04
While awaiting, event wrong_response produces healthy/record_roundtrip instead of awaiting/ignore_unmatched.
Application liveness challenge controller: awaiting / wrong response · case 05
While awaiting, event wrong_response produces healthy/record_roundtrip instead of awaiting/ignore_unmatched.
Application liveness challenge controller: awaiting / deadline · case 01
While awaiting, event deadline produces dead/release_peer instead of suspect/report_suspect.
Application liveness challenge controller: awaiting / deadline · case 02
While awaiting, event deadline produces dead/release_peer instead of suspect/report_suspect.
Application liveness challenge controller: awaiting / deadline · case 03
While awaiting, event deadline produces dead/release_peer instead of suspect/report_suspect.
Application liveness challenge controller: awaiting / deadline · case 04
While awaiting, event deadline produces dead/release_peer instead of suspect/report_suspect.
Application liveness challenge controller: awaiting / deadline · case 05
While awaiting, event deadline produces dead/release_peer instead of suspect/report_suspect.
Application liveness challenge controller: suspect / operator confirm dead · case 01
While suspect, event operator_confirm_dead produces healthy/keep_peer instead of dead/release_peer.
Application liveness challenge controller: suspect / operator confirm dead · case 02
While suspect, event operator_confirm_dead produces healthy/keep_peer instead of dead/release_peer.
Application liveness challenge controller: suspect / operator confirm dead · case 03
While suspect, event operator_confirm_dead produces healthy/keep_peer instead of dead/release_peer.
Application liveness challenge controller: suspect / operator confirm dead · case 04
While suspect, event operator_confirm_dead produces healthy/keep_peer instead of dead/release_peer.
Application liveness challenge controller: suspect / operator confirm dead · case 05
While suspect, event operator_confirm_dead produces healthy/keep_peer instead of dead/release_peer.
Application liveness challenge controller: suspect / matching response · case 01
While suspect, event matching_response produces dead/release_peer instead of healthy/clear_suspicion.
Application liveness challenge controller: suspect / matching response · case 02
While suspect, event matching_response produces dead/release_peer instead of healthy/clear_suspicion.
Application liveness challenge controller: suspect / matching response · case 03
While suspect, event matching_response produces dead/release_peer instead of healthy/clear_suspicion.
Application liveness challenge controller: suspect / matching response · case 04
While suspect, event matching_response produces dead/release_peer instead of healthy/clear_suspicion.
Application liveness challenge controller: suspect / matching response · case 05
While suspect, event matching_response produces dead/release_peer instead of healthy/clear_suspicion.
Application liveness challenge controller: healthy / probe due · case 01
While healthy, event probe_due produces healthy/reuse_result instead of awaiting/send_challenge.
Application liveness challenge controller: healthy / probe due · case 02
While healthy, event probe_due produces healthy/reuse_result instead of awaiting/send_challenge.
Application liveness challenge controller: healthy / probe due · case 03
While healthy, event probe_due produces healthy/reuse_result instead of awaiting/send_challenge.
Application liveness challenge controller: healthy / probe due · case 04
While healthy, event probe_due produces healthy/reuse_result instead of awaiting/send_challenge.
Application liveness challenge controller: healthy / probe due · case 05
While healthy, event probe_due produces healthy/reuse_result instead of awaiting/send_challenge.
Application liveness challenge controller: dead / matching response · case 01
While dead, event matching_response produces healthy/record_roundtrip instead of dead/reject_old_session.
Application liveness challenge controller: dead / matching response · case 02
While dead, event matching_response produces healthy/record_roundtrip instead of dead/reject_old_session.
Application liveness challenge controller: dead / matching response · case 03
While dead, event matching_response produces healthy/record_roundtrip instead of dead/reject_old_session.
Application liveness challenge controller: dead / matching response · case 04
While dead, event matching_response produces healthy/record_roundtrip instead of dead/reject_old_session.
Application liveness challenge controller: dead / matching response · case 05
While dead, event matching_response produces healthy/record_roundtrip instead of dead/reject_old_session.
Application liveness challenge controller: quiet / unsolicited response · case 01
While quiet, event unsolicited_response produces healthy/record_roundtrip instead of quiet/ignore_unmatched.
Application liveness challenge controller: quiet / unsolicited response · case 02
While quiet, event unsolicited_response produces healthy/record_roundtrip instead of quiet/ignore_unmatched.
Application liveness challenge controller: quiet / unsolicited response · case 03
While quiet, event unsolicited_response produces healthy/record_roundtrip instead of quiet/ignore_unmatched.
Application liveness challenge controller: quiet / unsolicited response · case 04
While quiet, event unsolicited_response produces healthy/record_roundtrip instead of quiet/ignore_unmatched.
Application liveness challenge controller: quiet / unsolicited response · case 05
While quiet, event unsolicited_response produces healthy/record_roundtrip instead of quiet/ignore_unmatched.
Application liveness challenge controller: healthy / traffic received · case 01
While healthy, event traffic_received produces awaiting/send_challenge instead of healthy/record_activity.
Application liveness challenge controller: healthy / traffic received · case 02
While healthy, event traffic_received produces awaiting/send_challenge instead of healthy/record_activity.
Application liveness challenge controller: healthy / traffic received · case 03
While healthy, event traffic_received produces awaiting/send_challenge instead of healthy/record_activity.
Application liveness challenge controller: healthy / traffic received · case 04
While healthy, event traffic_received produces awaiting/send_challenge instead of healthy/record_activity.
Application liveness challenge controller: healthy / traffic received · case 05
While healthy, event traffic_received produces awaiting/send_challenge instead of healthy/record_activity.
Peer restart-drain coordination controller: running / restart notice · case 01
While running, event restart_notice produces stopped/terminate instead of draining/stop_new_work.
Peer restart-drain coordination controller: running / restart notice · case 02
While running, event restart_notice produces stopped/terminate instead of draining/stop_new_work.
Peer restart-drain coordination controller: running / restart notice · case 03
While running, event restart_notice produces stopped/terminate instead of draining/stop_new_work.
Peer restart-drain coordination controller: running / restart notice · case 04
While running, event restart_notice produces stopped/terminate instead of draining/stop_new_work.
Peer restart-drain coordination controller: running / restart notice · case 05
While running, event restart_notice produces stopped/terminate instead of draining/stop_new_work.
Peer restart-drain coordination controller: draining / work finished · case 01
While draining, event work_finished produces stopped/terminate instead of ready/send_ready.
Peer restart-drain coordination controller: draining / work finished · case 02
While draining, event work_finished produces stopped/terminate instead of ready/send_ready.
Peer restart-drain coordination controller: draining / work finished · case 03
While draining, event work_finished produces stopped/terminate instead of ready/send_ready.
Peer restart-drain coordination controller: draining / work finished · case 04
While draining, event work_finished produces stopped/terminate instead of ready/send_ready.
Peer restart-drain coordination controller: draining / work finished · case 05
While draining, event work_finished produces stopped/terminate instead of ready/send_ready.
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 ↗