FAILURE MAP

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 ↗
100840Executable case variants
20168Distinct failure mechanisms
302520Executed implementations
20168Open-access cases

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

Python · Standard library
REFERENCEFAILURE MECHANISMDOMAINACCESS
FA-19101

Intercom call-signaling controller: alerting / answered · case 01

While alerting, event answered produces alerting/notify_remote_ring instead of connected/open_media.

Protocols● Open access↗
FA-19102

Intercom call-signaling controller: alerting / answered · case 02

While alerting, event answered produces alerting/notify_remote_ring instead of connected/open_media.

Protocols◈ Members↗
FA-19103

Intercom call-signaling controller: alerting / answered · case 03

While alerting, event answered produces alerting/notify_remote_ring instead of connected/open_media.

Protocols◈ Members↗
FA-19104

Intercom call-signaling controller: alerting / answered · case 04

While alerting, event answered produces alerting/notify_remote_ring instead of connected/open_media.

Protocols◈ Members↗
FA-19105

Intercom call-signaling controller: alerting / answered · case 05

While alerting, event answered produces alerting/notify_remote_ring instead of connected/open_media.

Protocols◈ Members↗
FA-19106

Intercom call-signaling controller: outgoing / busy · case 01

While outgoing, event busy produces connected/open_media instead of idle/report_busy.

Protocols● Open access↗
FA-19107

Intercom call-signaling controller: outgoing / busy · case 02

While outgoing, event busy produces connected/open_media instead of idle/report_busy.

Protocols◈ Members↗
FA-19108

Intercom call-signaling controller: outgoing / busy · case 03

While outgoing, event busy produces connected/open_media instead of idle/report_busy.

Protocols◈ Members↗
FA-19109

Intercom call-signaling controller: outgoing / busy · case 04

While outgoing, event busy produces connected/open_media instead of idle/report_busy.

Protocols◈ Members↗
FA-19110

Intercom call-signaling controller: outgoing / busy · case 05

While outgoing, event busy produces connected/open_media instead of idle/report_busy.

Protocols◈ Members↗
FA-19111

Intercom call-signaling controller: idle / invitation · case 01

While idle, event invitation produces connected/open_media instead of incoming/ring_local.

Protocols● Open access↗
FA-19112

Intercom call-signaling controller: idle / invitation · case 02

While idle, event invitation produces connected/open_media instead of incoming/ring_local.

Protocols◈ Members↗
FA-19113

Intercom call-signaling controller: idle / invitation · case 03

While idle, event invitation produces connected/open_media instead of incoming/ring_local.

Protocols◈ Members↗
FA-19114

Intercom call-signaling controller: idle / invitation · case 04

While idle, event invitation produces connected/open_media instead of incoming/ring_local.

Protocols◈ Members↗
FA-19115

Intercom call-signaling controller: idle / invitation · case 05

While idle, event invitation produces connected/open_media instead of incoming/ring_local.

Protocols◈ Members↗
FA-19116

Intercom call-signaling controller: incoming / accept · case 01

While incoming, event accept produces connected/open_media instead of connected/answer_open_media.

Protocols● Open access↗
FA-19117

Intercom call-signaling controller: incoming / accept · case 02

While incoming, event accept produces connected/open_media instead of connected/answer_open_media.

Protocols◈ Members↗
FA-19118

Intercom call-signaling controller: incoming / accept · case 03

While incoming, event accept produces connected/open_media instead of connected/answer_open_media.

Protocols◈ Members↗
FA-19119

Intercom call-signaling controller: incoming / accept · case 04

While incoming, event accept produces connected/open_media instead of connected/answer_open_media.

Protocols◈ Members↗
FA-19120

Intercom call-signaling controller: incoming / accept · case 05

While incoming, event accept produces connected/open_media instead of connected/answer_open_media.

Protocols◈ Members↗
FA-19121

Intercom call-signaling controller: incoming / decline · case 01

While incoming, event decline produces connected/open_media instead of idle/send_decline_stop_ring.

Protocols● Open access↗
FA-19122

Intercom call-signaling controller: incoming / decline · case 02

While incoming, event decline produces connected/open_media instead of idle/send_decline_stop_ring.

Protocols◈ Members↗
FA-19123

Intercom call-signaling controller: incoming / decline · case 03

While incoming, event decline produces connected/open_media instead of idle/send_decline_stop_ring.

Protocols◈ Members↗
FA-19124

Intercom call-signaling controller: incoming / decline · case 04

While incoming, event decline produces connected/open_media instead of idle/send_decline_stop_ring.

Protocols◈ Members↗
FA-19125

Intercom call-signaling controller: incoming / decline · case 05

While incoming, event decline produces connected/open_media instead of idle/send_decline_stop_ring.

Protocols◈ Members↗
FA-19126

Intercom call-signaling controller: connected / hold · case 01

While connected, event hold produces connected/mute_only instead of held/mute_send_hold.

Protocols● Open access↗
FA-19127

Intercom call-signaling controller: connected / hold · case 02

While connected, event hold produces connected/mute_only instead of held/mute_send_hold.

Protocols◈ Members↗
FA-19128

Intercom call-signaling controller: connected / hold · case 03

While connected, event hold produces connected/mute_only instead of held/mute_send_hold.

Protocols◈ Members↗
FA-19129

Intercom call-signaling controller: connected / hold · case 04

While connected, event hold produces connected/mute_only instead of held/mute_send_hold.

Protocols◈ Members↗
FA-19130

Intercom call-signaling controller: connected / hold · case 05

While connected, event hold produces connected/mute_only instead of held/mute_send_hold.

Protocols◈ Members↗
FA-19131

Intercom call-signaling controller: held / resume · case 01

While held, event resume produces connected/unmute_only instead of connected/unmute_send_resume.

Protocols● Open access↗
FA-19132

Intercom call-signaling controller: held / resume · case 02

While held, event resume produces connected/unmute_only instead of connected/unmute_send_resume.

Protocols◈ Members↗
FA-19133

Intercom call-signaling controller: held / resume · case 03

While held, event resume produces connected/unmute_only instead of connected/unmute_send_resume.

Protocols◈ Members↗
FA-19134

Intercom call-signaling controller: held / resume · case 04

While held, event resume produces connected/unmute_only instead of connected/unmute_send_resume.

Protocols◈ Members↗
FA-19135

Intercom call-signaling controller: held / resume · case 05

While held, event resume produces connected/unmute_only instead of connected/unmute_send_resume.

Protocols◈ Members↗
FA-19136

Intercom call-signaling controller: connected / hangup · case 01

While connected, event hangup produces idle/close_media_only instead of idle/close_media_send_bye.

Protocols● Open access↗
FA-19137

Intercom call-signaling controller: connected / hangup · case 02

While connected, event hangup produces idle/close_media_only instead of idle/close_media_send_bye.

Protocols◈ Members↗
FA-19138

Intercom call-signaling controller: connected / hangup · case 03

While connected, event hangup produces idle/close_media_only instead of idle/close_media_send_bye.

Protocols◈ Members↗
FA-19139

Intercom call-signaling controller: connected / hangup · case 04

While connected, event hangup produces idle/close_media_only instead of idle/close_media_send_bye.

Protocols◈ Members↗
FA-19140

Intercom call-signaling controller: connected / hangup · case 05

While connected, event hangup produces idle/close_media_only instead of idle/close_media_send_bye.

Protocols◈ Members↗
FA-19141

Resumable event subscription controller: new / subscribe · case 01

While new, event subscribe produces live/deliver_delta instead of pending/request_snapshot.

Protocols● Open access↗
FA-19142

Resumable event subscription controller: new / subscribe · case 02

While new, event subscribe produces live/deliver_delta instead of pending/request_snapshot.

Protocols◈ Members↗
FA-19143

Resumable event subscription controller: new / subscribe · case 03

While new, event subscribe produces live/deliver_delta instead of pending/request_snapshot.

Protocols◈ Members↗
FA-19144

Resumable event subscription controller: new / subscribe · case 04

While new, event subscribe produces live/deliver_delta instead of pending/request_snapshot.

Protocols◈ Members↗
FA-19145

Resumable event subscription controller: new / subscribe · case 05

While new, event subscribe produces live/deliver_delta instead of pending/request_snapshot.

Protocols◈ Members↗
FA-19146

Resumable event subscription controller: pending / snapshot begin · case 01

While pending, event snapshot_begin produces live/publish instead of snapshot/reset_baseline.

Protocols● Open access↗
FA-19147

Resumable event subscription controller: pending / snapshot begin · case 02

While pending, event snapshot_begin produces live/publish instead of snapshot/reset_baseline.

Protocols◈ Members↗
FA-19148

Resumable event subscription controller: pending / snapshot begin · case 03

While pending, event snapshot_begin produces live/publish instead of snapshot/reset_baseline.

Protocols◈ Members↗
FA-19149

Resumable event subscription controller: pending / snapshot begin · case 04

While pending, event snapshot_begin produces live/publish instead of snapshot/reset_baseline.

Protocols◈ Members↗
FA-19150

Resumable event subscription controller: pending / snapshot begin · case 05

While pending, event snapshot_begin produces live/publish instead of snapshot/reset_baseline.

Protocols◈ Members↗
FA-19151

Resumable event subscription controller: snapshot / snapshot end · case 01

While snapshot, event snapshot_end produces live/deliver_delta instead of catchup/seal_baseline.

Protocols● Open access↗
FA-19152

Resumable event subscription controller: snapshot / snapshot end · case 02

While snapshot, event snapshot_end produces live/deliver_delta instead of catchup/seal_baseline.

Protocols◈ Members↗
FA-19153

Resumable event subscription controller: snapshot / snapshot end · case 03

While snapshot, event snapshot_end produces live/deliver_delta instead of catchup/seal_baseline.

Protocols◈ Members↗
FA-19154

Resumable event subscription controller: snapshot / snapshot end · case 04

While snapshot, event snapshot_end produces live/deliver_delta instead of catchup/seal_baseline.

Protocols◈ Members↗
FA-19155

Resumable event subscription controller: snapshot / snapshot end · case 05

While snapshot, event snapshot_end produces live/deliver_delta instead of catchup/seal_baseline.

Protocols◈ Members↗
FA-19156

Resumable event subscription controller: catchup / caught up · case 01

While catchup, event caught_up produces catchup/wait instead of live/publish_ready.

Protocols● Open access↗
FA-19157

Resumable event subscription controller: catchup / caught up · case 02

While catchup, event caught_up produces catchup/wait instead of live/publish_ready.

Protocols◈ Members↗
FA-19158

Resumable event subscription controller: catchup / caught up · case 03

While catchup, event caught_up produces catchup/wait instead of live/publish_ready.

Protocols◈ Members↗
FA-19159

Resumable event subscription controller: catchup / caught up · case 04

While catchup, event caught_up produces catchup/wait instead of live/publish_ready.

Protocols◈ Members↗
FA-19160

Resumable event subscription controller: catchup / caught up · case 05

While catchup, event caught_up produces catchup/wait instead of live/publish_ready.

Protocols◈ Members↗
FA-19161

Resumable event subscription controller: live / gap · case 01

While live, event gap produces live/deliver_delta instead of resync/request_baseline.

Protocols● Open access↗
FA-19162

Resumable event subscription controller: live / gap · case 02

While live, event gap produces live/deliver_delta instead of resync/request_baseline.

Protocols◈ Members↗
FA-19163

Resumable event subscription controller: live / gap · case 03

While live, event gap produces live/deliver_delta instead of resync/request_baseline.

Protocols◈ Members↗
FA-19164

Resumable event subscription controller: live / gap · case 04

While live, event gap produces live/deliver_delta instead of resync/request_baseline.

Protocols◈ Members↗
FA-19165

Resumable event subscription controller: live / gap · case 05

While live, event gap produces live/deliver_delta instead of resync/request_baseline.

Protocols◈ Members↗
FA-19166

Resumable event subscription controller: resync / snapshot begin · case 01

While resync, event snapshot_begin produces live/publish instead of snapshot/replace_baseline.

Protocols● Open access↗
FA-19167

Resumable event subscription controller: resync / snapshot begin · case 02

While resync, event snapshot_begin produces live/publish instead of snapshot/replace_baseline.

Protocols◈ Members↗
FA-19168

Resumable event subscription controller: resync / snapshot begin · case 03

While resync, event snapshot_begin produces live/publish instead of snapshot/replace_baseline.

Protocols◈ Members↗
FA-19169

Resumable event subscription controller: resync / snapshot begin · case 04

While resync, event snapshot_begin produces live/publish instead of snapshot/replace_baseline.

Protocols◈ Members↗
FA-19170

Resumable event subscription controller: resync / snapshot begin · case 05

While resync, event snapshot_begin produces live/publish instead of snapshot/replace_baseline.

Protocols◈ Members↗
FA-19171

Resumable event subscription controller: live / disconnect · case 01

While live, event disconnect produces new/forget_cursor instead of paused/save_cursor.

Protocols● Open access↗
FA-19172

Resumable event subscription controller: live / disconnect · case 02

While live, event disconnect produces new/forget_cursor instead of paused/save_cursor.

Protocols◈ Members↗
FA-19173

Resumable event subscription controller: live / disconnect · case 03

While live, event disconnect produces new/forget_cursor instead of paused/save_cursor.

Protocols◈ Members↗
FA-19174

Resumable event subscription controller: live / disconnect · case 04

While live, event disconnect produces new/forget_cursor instead of paused/save_cursor.

Protocols◈ Members↗
FA-19175

Resumable event subscription controller: live / disconnect · case 05

While live, event disconnect produces new/forget_cursor instead of paused/save_cursor.

Protocols◈ Members↗
FA-19176

Resumable event subscription controller: paused / resume accepted · case 01

While paused, event resume_accepted produces live/deliver_delta instead of catchup/request_after_cursor.

Protocols● Open access↗
FA-19177

Resumable event subscription controller: paused / resume accepted · case 02

While paused, event resume_accepted produces live/deliver_delta instead of catchup/request_after_cursor.

Protocols◈ Members↗
FA-19178

Resumable event subscription controller: paused / resume accepted · case 03

While paused, event resume_accepted produces live/deliver_delta instead of catchup/request_after_cursor.

Protocols◈ Members↗
FA-19179

Resumable event subscription controller: paused / resume accepted · case 04

While paused, event resume_accepted produces live/deliver_delta instead of catchup/request_after_cursor.

Protocols◈ Members↗
FA-19180

Resumable event subscription controller: paused / resume accepted · case 05

While paused, event resume_accepted produces live/deliver_delta instead of catchup/request_after_cursor.

Protocols◈ Members↗
FA-19181

Resumable event subscription controller: paused / cursor expired · case 01

While paused, event cursor_expired produces live/deliver_delta instead of pending/request_snapshot.

Protocols● Open access↗
FA-19182

Resumable event subscription controller: paused / cursor expired · case 02

While paused, event cursor_expired produces live/deliver_delta instead of pending/request_snapshot.

Protocols◈ Members↗
FA-19183

Resumable event subscription controller: paused / cursor expired · case 03

While paused, event cursor_expired produces live/deliver_delta instead of pending/request_snapshot.

Protocols◈ Members↗
FA-19184

Resumable event subscription controller: paused / cursor expired · case 04

While paused, event cursor_expired produces live/deliver_delta instead of pending/request_snapshot.

Protocols◈ Members↗
FA-19185

Resumable event subscription controller: paused / cursor expired · case 05

While paused, event cursor_expired produces live/deliver_delta instead of pending/request_snapshot.

Protocols◈ Members↗
FA-19186

Resumable event subscription controller: live / unsubscribe · case 01

While live, event unsubscribe produces paused/save_cursor instead of closed/release_subscription.

Protocols● Open access↗
FA-19187

Resumable event subscription controller: live / unsubscribe · case 02

While live, event unsubscribe produces paused/save_cursor instead of closed/release_subscription.

Protocols◈ Members↗
FA-19188

Resumable event subscription controller: live / unsubscribe · case 03

While live, event unsubscribe produces paused/save_cursor instead of closed/release_subscription.

Protocols◈ Members↗
FA-19189

Resumable event subscription controller: live / unsubscribe · case 04

While live, event unsubscribe produces paused/save_cursor instead of closed/release_subscription.

Protocols◈ Members↗
FA-19190

Resumable event subscription controller: live / unsubscribe · case 05

While live, event unsubscribe produces paused/save_cursor instead of closed/release_subscription.

Protocols◈ Members↗
FA-19191

Route advertisement lifecycle controller: unknown / announce · case 01

While unknown, event announce produces usable/install instead of candidate/check_path.

Protocols● Open access↗
FA-19192

Route advertisement lifecycle controller: unknown / announce · case 02

While unknown, event announce produces usable/install instead of candidate/check_path.

Protocols◈ Members↗
FA-19193

Route advertisement lifecycle controller: unknown / announce · case 03

While unknown, event announce produces usable/install instead of candidate/check_path.

Protocols◈ Members↗
FA-19194

Route advertisement lifecycle controller: unknown / announce · case 04

While unknown, event announce produces usable/install instead of candidate/check_path.

Protocols◈ Members↗
FA-19195

Route advertisement lifecycle controller: unknown / announce · case 05

While unknown, event announce produces usable/install instead of candidate/check_path.

Protocols◈ Members↗
FA-19196

Route advertisement lifecycle controller: candidate / loop free · case 01

While candidate, event loop_free produces candidate/wait instead of usable/install.

Protocols● Open access↗
FA-19197

Route advertisement lifecycle controller: candidate / loop free · case 02

While candidate, event loop_free produces candidate/wait instead of usable/install.

Protocols◈ Members↗
FA-19198

Route advertisement lifecycle controller: candidate / loop free · case 03

While candidate, event loop_free produces candidate/wait instead of usable/install.

Protocols◈ Members↗
FA-19199

Route advertisement lifecycle controller: candidate / loop free · case 04

While candidate, event loop_free produces candidate/wait instead of usable/install.

Protocols◈ Members↗
FA-19200

Route advertisement lifecycle controller: candidate / loop free · case 05

While candidate, event loop_free produces candidate/wait instead of usable/install.

Protocols◈ Members↗

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 ↗