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-20101

Acknowledged telemetry publication window controller: collecting / close window · case 01

While collecting, event close_window produces published/send_partial instead of sealed/seal_samples.

Protocols● Open access↗
FA-20102

Acknowledged telemetry publication window controller: collecting / close window · case 02

While collecting, event close_window produces published/send_partial instead of sealed/seal_samples.

Protocols◈ Members↗
FA-20103

Acknowledged telemetry publication window controller: collecting / close window · case 03

While collecting, event close_window produces published/send_partial instead of sealed/seal_samples.

Protocols◈ Members↗
FA-20104

Acknowledged telemetry publication window controller: collecting / close window · case 04

While collecting, event close_window produces published/send_partial instead of sealed/seal_samples.

Protocols◈ Members↗
FA-20105

Acknowledged telemetry publication window controller: collecting / close window · case 05

While collecting, event close_window produces published/send_partial instead of sealed/seal_samples.

Protocols◈ Members↗
FA-20106

Acknowledged telemetry publication window controller: sealed / publish · case 01

While sealed, event publish produces idle/release_window instead of awaiting/send_window.

Protocols● Open access↗
FA-20107

Acknowledged telemetry publication window controller: sealed / publish · case 02

While sealed, event publish produces idle/release_window instead of awaiting/send_window.

Protocols◈ Members↗
FA-20108

Acknowledged telemetry publication window controller: sealed / publish · case 03

While sealed, event publish produces idle/release_window instead of awaiting/send_window.

Protocols◈ Members↗
FA-20109

Acknowledged telemetry publication window controller: sealed / publish · case 04

While sealed, event publish produces idle/release_window instead of awaiting/send_window.

Protocols◈ Members↗
FA-20110

Acknowledged telemetry publication window controller: sealed / publish · case 05

While sealed, event publish produces idle/release_window instead of awaiting/send_window.

Protocols◈ Members↗
FA-20111

Acknowledged telemetry publication window controller: awaiting / window ack · case 01

While awaiting, event window_ack produces idle/delete_immediately instead of published/mark_delivered.

Protocols● Open access↗
FA-20112

Acknowledged telemetry publication window controller: awaiting / window ack · case 02

While awaiting, event window_ack produces idle/delete_immediately instead of published/mark_delivered.

Protocols◈ Members↗
FA-20113

Acknowledged telemetry publication window controller: awaiting / window ack · case 03

While awaiting, event window_ack produces idle/delete_immediately instead of published/mark_delivered.

Protocols◈ Members↗
FA-20114

Acknowledged telemetry publication window controller: awaiting / window ack · case 04

While awaiting, event window_ack produces idle/delete_immediately instead of published/mark_delivered.

Protocols◈ Members↗
FA-20115

Acknowledged telemetry publication window controller: awaiting / window ack · case 05

While awaiting, event window_ack produces idle/delete_immediately instead of published/mark_delivered.

Protocols◈ Members↗
FA-20116

Acknowledged telemetry publication window controller: awaiting / wrong window ack · case 01

While awaiting, event wrong_window_ack produces published/mark_delivered instead of awaiting/ignore_unmatched.

Protocols● Open access↗
FA-20117

Acknowledged telemetry publication window controller: awaiting / wrong window ack · case 02

While awaiting, event wrong_window_ack produces published/mark_delivered instead of awaiting/ignore_unmatched.

Protocols◈ Members↗
FA-20118

Acknowledged telemetry publication window controller: awaiting / wrong window ack · case 03

While awaiting, event wrong_window_ack produces published/mark_delivered instead of awaiting/ignore_unmatched.

Protocols◈ Members↗
FA-20119

Acknowledged telemetry publication window controller: awaiting / wrong window ack · case 04

While awaiting, event wrong_window_ack produces published/mark_delivered instead of awaiting/ignore_unmatched.

Protocols◈ Members↗
FA-20120

Acknowledged telemetry publication window controller: awaiting / wrong window ack · case 05

While awaiting, event wrong_window_ack produces published/mark_delivered instead of awaiting/ignore_unmatched.

Protocols◈ Members↗
FA-20121

Acknowledged telemetry publication window controller: published / retention done · case 01

While published, event retention_done produces published/retain instead of idle/release_window.

Protocols● Open access↗
FA-20122

Acknowledged telemetry publication window controller: published / retention done · case 02

While published, event retention_done produces published/retain instead of idle/release_window.

Protocols◈ Members↗
FA-20123

Acknowledged telemetry publication window controller: published / retention done · case 03

While published, event retention_done produces published/retain instead of idle/release_window.

Protocols◈ Members↗
FA-20124

Acknowledged telemetry publication window controller: published / retention done · case 04

While published, event retention_done produces published/retain instead of idle/release_window.

Protocols◈ Members↗
FA-20125

Acknowledged telemetry publication window controller: published / retention done · case 05

While published, event retention_done produces published/retain instead of idle/release_window.

Protocols◈ Members↗
FA-20126

Acknowledged telemetry publication window controller: sealed / sample · case 01

While sealed, event sample produces collecting/append_sample instead of sealed/queue_next_window.

Protocols● Open access↗
FA-20127

Acknowledged telemetry publication window controller: sealed / sample · case 02

While sealed, event sample produces collecting/append_sample instead of sealed/queue_next_window.

Protocols◈ Members↗
FA-20128

Acknowledged telemetry publication window controller: sealed / sample · case 03

While sealed, event sample produces collecting/append_sample instead of sealed/queue_next_window.

Protocols◈ Members↗
FA-20129

Acknowledged telemetry publication window controller: sealed / sample · case 04

While sealed, event sample produces collecting/append_sample instead of sealed/queue_next_window.

Protocols◈ Members↗
FA-20130

Acknowledged telemetry publication window controller: sealed / sample · case 05

While sealed, event sample produces collecting/append_sample instead of sealed/queue_next_window.

Protocols◈ Members↗
FA-20131

Acknowledged telemetry publication window controller: awaiting / receiver backpressure · case 01

While awaiting, event receiver_backpressure produces idle/drop_window instead of paused/retain_window.

Protocols● Open access↗
FA-20132

Acknowledged telemetry publication window controller: awaiting / receiver backpressure · case 02

While awaiting, event receiver_backpressure produces idle/drop_window instead of paused/retain_window.

Protocols◈ Members↗
FA-20133

Acknowledged telemetry publication window controller: awaiting / receiver backpressure · case 03

While awaiting, event receiver_backpressure produces idle/drop_window instead of paused/retain_window.

Protocols◈ Members↗
FA-20134

Acknowledged telemetry publication window controller: awaiting / receiver backpressure · case 04

While awaiting, event receiver_backpressure produces idle/drop_window instead of paused/retain_window.

Protocols◈ Members↗
FA-20135

Acknowledged telemetry publication window controller: awaiting / receiver backpressure · case 05

While awaiting, event receiver_backpressure produces idle/drop_window instead of paused/retain_window.

Protocols◈ Members↗
FA-20136

Acknowledged telemetry publication window controller: paused / receiver ready · case 01

While paused, event receiver_ready produces collecting/rebuild_window instead of awaiting/resume_same_window.

Protocols● Open access↗
FA-20137

Acknowledged telemetry publication window controller: paused / receiver ready · case 02

While paused, event receiver_ready produces collecting/rebuild_window instead of awaiting/resume_same_window.

Protocols◈ Members↗
FA-20138

Acknowledged telemetry publication window controller: paused / receiver ready · case 03

While paused, event receiver_ready produces collecting/rebuild_window instead of awaiting/resume_same_window.

Protocols◈ Members↗
FA-20139

Acknowledged telemetry publication window controller: paused / receiver ready · case 04

While paused, event receiver_ready produces collecting/rebuild_window instead of awaiting/resume_same_window.

Protocols◈ Members↗
FA-20140

Acknowledged telemetry publication window controller: paused / receiver ready · case 05

While paused, event receiver_ready produces collecting/rebuild_window instead of awaiting/resume_same_window.

Protocols◈ Members↗
FA-20141

Two-peer rendezvous role assignment controller: empty / first arrival · case 01

While empty, event first_arrival produces paired/notify_pair instead of waiting/record_first.

Protocols● Open access↗
FA-20142

Two-peer rendezvous role assignment controller: empty / first arrival · case 02

While empty, event first_arrival produces paired/notify_pair instead of waiting/record_first.

Protocols◈ Members↗
FA-20143

Two-peer rendezvous role assignment controller: empty / first arrival · case 03

While empty, event first_arrival produces paired/notify_pair instead of waiting/record_first.

Protocols◈ Members↗
FA-20144

Two-peer rendezvous role assignment controller: empty / first arrival · case 04

While empty, event first_arrival produces paired/notify_pair instead of waiting/record_first.

Protocols◈ Members↗
FA-20145

Two-peer rendezvous role assignment controller: empty / first arrival · case 05

While empty, event first_arrival produces paired/notify_pair instead of waiting/record_first.

Protocols◈ Members↗
FA-20146

Two-peer rendezvous role assignment controller: waiting / second arrival · case 01

While waiting, event second_arrival produces waiting/replace_first instead of paired/assign_complementary_roles.

Protocols● Open access↗
FA-20147

Two-peer rendezvous role assignment controller: waiting / second arrival · case 02

While waiting, event second_arrival produces waiting/replace_first instead of paired/assign_complementary_roles.

Protocols◈ Members↗
FA-20148

Two-peer rendezvous role assignment controller: waiting / second arrival · case 03

While waiting, event second_arrival produces waiting/replace_first instead of paired/assign_complementary_roles.

Protocols◈ Members↗
FA-20149

Two-peer rendezvous role assignment controller: waiting / second arrival · case 04

While waiting, event second_arrival produces waiting/replace_first instead of paired/assign_complementary_roles.

Protocols◈ Members↗
FA-20150

Two-peer rendezvous role assignment controller: waiting / second arrival · case 05

While waiting, event second_arrival produces waiting/replace_first instead of paired/assign_complementary_roles.

Protocols◈ Members↗
FA-20151

Two-peer rendezvous role assignment controller: paired / first ready · case 01

While paired, event first_ready produces active/start_both instead of one_ready/record_ready.

Protocols● Open access↗
FA-20152

Two-peer rendezvous role assignment controller: paired / first ready · case 02

While paired, event first_ready produces active/start_both instead of one_ready/record_ready.

Protocols◈ Members↗
FA-20153

Two-peer rendezvous role assignment controller: paired / first ready · case 03

While paired, event first_ready produces active/start_both instead of one_ready/record_ready.

Protocols◈ Members↗
FA-20154

Two-peer rendezvous role assignment controller: paired / first ready · case 04

While paired, event first_ready produces active/start_both instead of one_ready/record_ready.

Protocols◈ Members↗
FA-20155

Two-peer rendezvous role assignment controller: paired / first ready · case 05

While paired, event first_ready produces active/start_both instead of one_ready/record_ready.

Protocols◈ Members↗
FA-20156

Two-peer rendezvous role assignment controller: one ready / second ready · case 01

While one_ready, event second_ready produces one_ready/wait instead of active/start_both.

Protocols● Open access↗
FA-20157

Two-peer rendezvous role assignment controller: one ready / second ready · case 02

While one_ready, event second_ready produces one_ready/wait instead of active/start_both.

Protocols◈ Members↗
FA-20158

Two-peer rendezvous role assignment controller: one ready / second ready · case 03

While one_ready, event second_ready produces one_ready/wait instead of active/start_both.

Protocols◈ Members↗
FA-20159

Two-peer rendezvous role assignment controller: one ready / second ready · case 04

While one_ready, event second_ready produces one_ready/wait instead of active/start_both.

Protocols◈ Members↗
FA-20160

Two-peer rendezvous role assignment controller: one ready / second ready · case 05

While one_ready, event second_ready produces one_ready/wait instead of active/start_both.

Protocols◈ Members↗
FA-20161

Two-peer rendezvous role assignment controller: waiting / first withdraws · case 01

While waiting, event first_withdraws produces waiting/keep_first instead of empty/remove_first.

Protocols● Open access↗
FA-20162

Two-peer rendezvous role assignment controller: waiting / first withdraws · case 02

While waiting, event first_withdraws produces waiting/keep_first instead of empty/remove_first.

Protocols◈ Members↗
FA-20163

Two-peer rendezvous role assignment controller: waiting / first withdraws · case 03

While waiting, event first_withdraws produces waiting/keep_first instead of empty/remove_first.

Protocols◈ Members↗
FA-20164

Two-peer rendezvous role assignment controller: waiting / first withdraws · case 04

While waiting, event first_withdraws produces waiting/keep_first instead of empty/remove_first.

Protocols◈ Members↗
FA-20165

Two-peer rendezvous role assignment controller: waiting / first withdraws · case 05

While waiting, event first_withdraws produces waiting/keep_first instead of empty/remove_first.

Protocols◈ Members↗
FA-20166

Two-peer rendezvous role assignment controller: paired / partner withdraws · case 01

While paired, event partner_withdraws produces active/start_both instead of waiting/notify_requeue_survivor.

Protocols● Open access↗
FA-20167

Two-peer rendezvous role assignment controller: paired / partner withdraws · case 02

While paired, event partner_withdraws produces active/start_both instead of waiting/notify_requeue_survivor.

Protocols◈ Members↗
FA-20168

Two-peer rendezvous role assignment controller: paired / partner withdraws · case 03

While paired, event partner_withdraws produces active/start_both instead of waiting/notify_requeue_survivor.

Protocols◈ Members↗
FA-20169

Two-peer rendezvous role assignment controller: paired / partner withdraws · case 04

While paired, event partner_withdraws produces active/start_both instead of waiting/notify_requeue_survivor.

Protocols◈ Members↗
FA-20170

Two-peer rendezvous role assignment controller: paired / partner withdraws · case 05

While paired, event partner_withdraws produces active/start_both instead of waiting/notify_requeue_survivor.

Protocols◈ Members↗
FA-20171

Two-peer rendezvous role assignment controller: active / third arrival · case 01

While active, event third_arrival produces paired/replace_partner instead of active/reject_full.

Protocols● Open access↗
FA-20172

Two-peer rendezvous role assignment controller: active / third arrival · case 02

While active, event third_arrival produces paired/replace_partner instead of active/reject_full.

Protocols◈ Members↗
FA-20173

Two-peer rendezvous role assignment controller: active / third arrival · case 03

While active, event third_arrival produces paired/replace_partner instead of active/reject_full.

Protocols◈ Members↗
FA-20174

Two-peer rendezvous role assignment controller: active / third arrival · case 04

While active, event third_arrival produces paired/replace_partner instead of active/reject_full.

Protocols◈ Members↗
FA-20175

Two-peer rendezvous role assignment controller: active / third arrival · case 05

While active, event third_arrival produces paired/replace_partner instead of active/reject_full.

Protocols◈ Members↗
FA-20176

Two-peer rendezvous role assignment controller: one ready / duplicate ready · case 01

While one_ready, event duplicate_ready produces active/start_both instead of one_ready/ack_existing.

Protocols● Open access↗
FA-20177

Two-peer rendezvous role assignment controller: one ready / duplicate ready · case 02

While one_ready, event duplicate_ready produces active/start_both instead of one_ready/ack_existing.

Protocols◈ Members↗
FA-20178

Two-peer rendezvous role assignment controller: one ready / duplicate ready · case 03

While one_ready, event duplicate_ready produces active/start_both instead of one_ready/ack_existing.

Protocols◈ Members↗
FA-20179

Two-peer rendezvous role assignment controller: one ready / duplicate ready · case 04

While one_ready, event duplicate_ready produces active/start_both instead of one_ready/ack_existing.

Protocols◈ Members↗
FA-20180

Two-peer rendezvous role assignment controller: one ready / duplicate ready · case 05

While one_ready, event duplicate_ready produces active/start_both instead of one_ready/ack_existing.

Protocols◈ Members↗
FA-20181

Two-peer rendezvous role assignment controller: empty / ready · case 01

While empty, event ready produces one_ready/record_ready instead of empty/reject_unpaired.

Protocols● Open access↗
FA-20182

Two-peer rendezvous role assignment controller: empty / ready · case 02

While empty, event ready produces one_ready/record_ready instead of empty/reject_unpaired.

Protocols◈ Members↗
FA-20183

Two-peer rendezvous role assignment controller: empty / ready · case 03

While empty, event ready produces one_ready/record_ready instead of empty/reject_unpaired.

Protocols◈ Members↗
FA-20184

Two-peer rendezvous role assignment controller: empty / ready · case 04

While empty, event ready produces one_ready/record_ready instead of empty/reject_unpaired.

Protocols◈ Members↗
FA-20185

Two-peer rendezvous role assignment controller: empty / ready · case 05

While empty, event ready produces one_ready/record_ready instead of empty/reject_unpaired.

Protocols◈ Members↗
FA-20186

Two-peer rendezvous role assignment controller: active / both done · case 01

While active, event both_done produces active/retain instead of empty/release_pair.

Protocols● Open access↗
FA-20187

Two-peer rendezvous role assignment controller: active / both done · case 02

While active, event both_done produces active/retain instead of empty/release_pair.

Protocols◈ Members↗
FA-20188

Two-peer rendezvous role assignment controller: active / both done · case 03

While active, event both_done produces active/retain instead of empty/release_pair.

Protocols◈ Members↗
FA-20189

Two-peer rendezvous role assignment controller: active / both done · case 04

While active, event both_done produces active/retain instead of empty/release_pair.

Protocols◈ Members↗
FA-20190

Two-peer rendezvous role assignment controller: active / both done · case 05

While active, event both_done produces active/retain instead of empty/release_pair.

Protocols◈ Members↗
FA-20191

Mirror baseline and delta cutover controller: empty / baseline offer · case 01

While empty, event baseline_offer produces live/accept_deltas instead of copying/create_shadow.

Protocols● Open access↗
FA-20192

Mirror baseline and delta cutover controller: empty / baseline offer · case 02

While empty, event baseline_offer produces live/accept_deltas instead of copying/create_shadow.

Protocols◈ Members↗
FA-20193

Mirror baseline and delta cutover controller: empty / baseline offer · case 03

While empty, event baseline_offer produces live/accept_deltas instead of copying/create_shadow.

Protocols◈ Members↗
FA-20194

Mirror baseline and delta cutover controller: empty / baseline offer · case 04

While empty, event baseline_offer produces live/accept_deltas instead of copying/create_shadow.

Protocols◈ Members↗
FA-20195

Mirror baseline and delta cutover controller: empty / baseline offer · case 05

While empty, event baseline_offer produces live/accept_deltas instead of copying/create_shadow.

Protocols◈ Members↗
FA-20196

Mirror baseline and delta cutover controller: copying / baseline item · case 01

While copying, event baseline_item produces live/write_live instead of copying/write_shadow.

Protocols● Open access↗
FA-20197

Mirror baseline and delta cutover controller: copying / baseline item · case 02

While copying, event baseline_item produces live/write_live instead of copying/write_shadow.

Protocols◈ Members↗
FA-20198

Mirror baseline and delta cutover controller: copying / baseline item · case 03

While copying, event baseline_item produces live/write_live instead of copying/write_shadow.

Protocols◈ Members↗
FA-20199

Mirror baseline and delta cutover controller: copying / baseline item · case 04

While copying, event baseline_item produces live/write_live instead of copying/write_shadow.

Protocols◈ Members↗
FA-20200

Mirror baseline and delta cutover controller: copying / baseline item · case 05

While copying, event baseline_item produces live/write_live instead of copying/write_shadow.

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 ↗