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

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

While copying, event concurrent_delta produces copying/drop_delta instead of copying/buffer_after_cut.

Protocols● Open access↗
FA-20202

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

While copying, event concurrent_delta produces copying/drop_delta instead of copying/buffer_after_cut.

Protocols◈ Members↗
FA-20203

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

While copying, event concurrent_delta produces copying/drop_delta instead of copying/buffer_after_cut.

Protocols◈ Members↗
FA-20204

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

While copying, event concurrent_delta produces copying/drop_delta instead of copying/buffer_after_cut.

Protocols◈ Members↗
FA-20205

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

While copying, event concurrent_delta produces copying/drop_delta instead of copying/buffer_after_cut.

Protocols◈ Members↗
FA-20206

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

While copying, event baseline_end produces live/publish_shadow instead of replaying/seal_shadow.

Protocols● Open access↗
FA-20207

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

While copying, event baseline_end produces live/publish_shadow instead of replaying/seal_shadow.

Protocols◈ Members↗
FA-20208

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

While copying, event baseline_end produces live/publish_shadow instead of replaying/seal_shadow.

Protocols◈ Members↗
FA-20209

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

While copying, event baseline_end produces live/publish_shadow instead of replaying/seal_shadow.

Protocols◈ Members↗
FA-20210

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

While copying, event baseline_end produces live/publish_shadow instead of replaying/seal_shadow.

Protocols◈ Members↗
FA-20211

Mirror baseline and delta cutover controller: replaying / delta · case 01

While replaying, event delta produces replaying/apply_reverse instead of replaying/apply_buffered_order.

Protocols● Open access↗
FA-20212

Mirror baseline and delta cutover controller: replaying / delta · case 02

While replaying, event delta produces replaying/apply_reverse instead of replaying/apply_buffered_order.

Protocols◈ Members↗
FA-20213

Mirror baseline and delta cutover controller: replaying / delta · case 03

While replaying, event delta produces replaying/apply_reverse instead of replaying/apply_buffered_order.

Protocols◈ Members↗
FA-20214

Mirror baseline and delta cutover controller: replaying / delta · case 04

While replaying, event delta produces replaying/apply_reverse instead of replaying/apply_buffered_order.

Protocols◈ Members↗
FA-20215

Mirror baseline and delta cutover controller: replaying / delta · case 05

While replaying, event delta produces replaying/apply_reverse instead of replaying/apply_buffered_order.

Protocols◈ Members↗
FA-20216

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

While replaying, event buffer_empty produces replaying/wait instead of live/atomic_publish.

Protocols● Open access↗
FA-20217

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

While replaying, event buffer_empty produces replaying/wait instead of live/atomic_publish.

Protocols◈ Members↗
FA-20218

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

While replaying, event buffer_empty produces replaying/wait instead of live/atomic_publish.

Protocols◈ Members↗
FA-20219

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

While replaying, event buffer_empty produces replaying/wait instead of live/atomic_publish.

Protocols◈ Members↗
FA-20220

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

While replaying, event buffer_empty produces replaying/wait instead of live/atomic_publish.

Protocols◈ Members↗
FA-20221

Mirror baseline and delta cutover controller: live / source reset · case 01

While live, event source_reset produces live/continue instead of empty/invalidate_baseline.

Protocols● Open access↗
FA-20222

Mirror baseline and delta cutover controller: live / source reset · case 02

While live, event source_reset produces live/continue instead of empty/invalidate_baseline.

Protocols◈ Members↗
FA-20223

Mirror baseline and delta cutover controller: live / source reset · case 03

While live, event source_reset produces live/continue instead of empty/invalidate_baseline.

Protocols◈ Members↗
FA-20224

Mirror baseline and delta cutover controller: live / source reset · case 04

While live, event source_reset produces live/continue instead of empty/invalidate_baseline.

Protocols◈ Members↗
FA-20225

Mirror baseline and delta cutover controller: live / source reset · case 05

While live, event source_reset produces live/continue instead of empty/invalidate_baseline.

Protocols◈ Members↗
FA-20226

Mirror baseline and delta cutover controller: live / old generation delta · case 01

While live, event old_generation_delta produces live/apply_delta instead of live/reject_stale.

Protocols● Open access↗
FA-20227

Mirror baseline and delta cutover controller: live / old generation delta · case 02

While live, event old_generation_delta produces live/apply_delta instead of live/reject_stale.

Protocols◈ Members↗
FA-20228

Mirror baseline and delta cutover controller: live / old generation delta · case 03

While live, event old_generation_delta produces live/apply_delta instead of live/reject_stale.

Protocols◈ Members↗
FA-20229

Mirror baseline and delta cutover controller: live / old generation delta · case 04

While live, event old_generation_delta produces live/apply_delta instead of live/reject_stale.

Protocols◈ Members↗
FA-20230

Mirror baseline and delta cutover controller: live / old generation delta · case 05

While live, event old_generation_delta produces live/apply_delta instead of live/reject_stale.

Protocols◈ Members↗
FA-20231

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

While copying, event copy_cancelled produces live/publish_shadow instead of empty/discard_shadow.

Protocols● Open access↗
FA-20232

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

While copying, event copy_cancelled produces live/publish_shadow instead of empty/discard_shadow.

Protocols◈ Members↗
FA-20233

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

While copying, event copy_cancelled produces live/publish_shadow instead of empty/discard_shadow.

Protocols◈ Members↗
FA-20234

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

While copying, event copy_cancelled produces live/publish_shadow instead of empty/discard_shadow.

Protocols◈ Members↗
FA-20235

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

While copying, event copy_cancelled produces live/publish_shadow instead of empty/discard_shadow.

Protocols◈ Members↗
FA-20236

Mirror baseline and delta cutover controller: live / delta · case 01

While live, event delta produces live/buffer_forever instead of live/apply_notify.

Protocols● Open access↗
FA-20237

Mirror baseline and delta cutover controller: live / delta · case 02

While live, event delta produces live/buffer_forever instead of live/apply_notify.

Protocols◈ Members↗
FA-20238

Mirror baseline and delta cutover controller: live / delta · case 03

While live, event delta produces live/buffer_forever instead of live/apply_notify.

Protocols◈ Members↗
FA-20239

Mirror baseline and delta cutover controller: live / delta · case 04

While live, event delta produces live/buffer_forever instead of live/apply_notify.

Protocols◈ Members↗
FA-20240

Mirror baseline and delta cutover controller: live / delta · case 05

While live, event delta produces live/buffer_forever instead of live/apply_notify.

Protocols◈ Members↗
FA-20241

Serial line command and data mode controller: command / enter data · case 01

While command, event enter_data produces data/send_payload instead of switching/send_mode_request.

Protocols● Open access↗
FA-20242

Serial line command and data mode controller: command / enter data · case 02

While command, event enter_data produces data/send_payload instead of switching/send_mode_request.

Protocols◈ Members↗
FA-20243

Serial line command and data mode controller: command / enter data · case 03

While command, event enter_data produces data/send_payload instead of switching/send_mode_request.

Protocols◈ Members↗
FA-20244

Serial line command and data mode controller: command / enter data · case 04

While command, event enter_data produces data/send_payload instead of switching/send_mode_request.

Protocols◈ Members↗
FA-20245

Serial line command and data mode controller: command / enter data · case 05

While command, event enter_data produces data/send_payload instead of switching/send_mode_request.

Protocols◈ Members↗
FA-20246

Serial line command and data mode controller: switching / mode ack · case 01

While switching, event mode_ack produces command/keep_commands instead of data/enable_payload.

Protocols● Open access↗
FA-20247

Serial line command and data mode controller: switching / mode ack · case 02

While switching, event mode_ack produces command/keep_commands instead of data/enable_payload.

Protocols◈ Members↗
FA-20248

Serial line command and data mode controller: switching / mode ack · case 03

While switching, event mode_ack produces command/keep_commands instead of data/enable_payload.

Protocols◈ Members↗
FA-20249

Serial line command and data mode controller: switching / mode ack · case 04

While switching, event mode_ack produces command/keep_commands instead of data/enable_payload.

Protocols◈ Members↗
FA-20250

Serial line command and data mode controller: switching / mode ack · case 05

While switching, event mode_ack produces command/keep_commands instead of data/enable_payload.

Protocols◈ Members↗
FA-20251

Serial line command and data mode controller: switching / mode nack · case 01

While switching, event mode_nack produces data/enable_payload instead of command/report_refused.

Protocols● Open access↗
FA-20252

Serial line command and data mode controller: switching / mode nack · case 02

While switching, event mode_nack produces data/enable_payload instead of command/report_refused.

Protocols◈ Members↗
FA-20253

Serial line command and data mode controller: switching / mode nack · case 03

While switching, event mode_nack produces data/enable_payload instead of command/report_refused.

Protocols◈ Members↗
FA-20254

Serial line command and data mode controller: switching / mode nack · case 04

While switching, event mode_nack produces data/enable_payload instead of command/report_refused.

Protocols◈ Members↗
FA-20255

Serial line command and data mode controller: switching / mode nack · case 05

While switching, event mode_nack produces data/enable_payload instead of command/report_refused.

Protocols◈ Members↗
FA-20256

Serial line command and data mode controller: data / escape guard start · case 01

While data, event escape_guard_start produces command/parse_command instead of guarding/hold_escape_candidate.

Protocols● Open access↗
FA-20257

Serial line command and data mode controller: data / escape guard start · case 02

While data, event escape_guard_start produces command/parse_command instead of guarding/hold_escape_candidate.

Protocols◈ Members↗
FA-20258

Serial line command and data mode controller: data / escape guard start · case 03

While data, event escape_guard_start produces command/parse_command instead of guarding/hold_escape_candidate.

Protocols◈ Members↗
FA-20259

Serial line command and data mode controller: data / escape guard start · case 04

While data, event escape_guard_start produces command/parse_command instead of guarding/hold_escape_candidate.

Protocols◈ Members↗
FA-20260

Serial line command and data mode controller: data / escape guard start · case 05

While data, event escape_guard_start produces command/parse_command instead of guarding/hold_escape_candidate.

Protocols◈ Members↗
FA-20261

Serial line command and data mode controller: guarding / guard satisfied · case 01

While guarding, event guard_satisfied produces data/deliver_escape instead of command/consume_escape.

Protocols● Open access↗
FA-20262

Serial line command and data mode controller: guarding / guard satisfied · case 02

While guarding, event guard_satisfied produces data/deliver_escape instead of command/consume_escape.

Protocols◈ Members↗
FA-20263

Serial line command and data mode controller: guarding / guard satisfied · case 03

While guarding, event guard_satisfied produces data/deliver_escape instead of command/consume_escape.

Protocols◈ Members↗
FA-20264

Serial line command and data mode controller: guarding / guard satisfied · case 04

While guarding, event guard_satisfied produces data/deliver_escape instead of command/consume_escape.

Protocols◈ Members↗
FA-20265

Serial line command and data mode controller: guarding / guard satisfied · case 05

While guarding, event guard_satisfied produces data/deliver_escape instead of command/consume_escape.

Protocols◈ Members↗
FA-20266

Serial line command and data mode controller: guarding / guard broken · case 01

While guarding, event guard_broken produces command/parse_command instead of data/deliver_candidate_and_data.

Protocols● Open access↗
FA-20267

Serial line command and data mode controller: guarding / guard broken · case 02

While guarding, event guard_broken produces command/parse_command instead of data/deliver_candidate_and_data.

Protocols◈ Members↗
FA-20268

Serial line command and data mode controller: guarding / guard broken · case 03

While guarding, event guard_broken produces command/parse_command instead of data/deliver_candidate_and_data.

Protocols◈ Members↗
FA-20269

Serial line command and data mode controller: guarding / guard broken · case 04

While guarding, event guard_broken produces command/parse_command instead of data/deliver_candidate_and_data.

Protocols◈ Members↗
FA-20270

Serial line command and data mode controller: guarding / guard broken · case 05

While guarding, event guard_broken produces command/parse_command instead of data/deliver_candidate_and_data.

Protocols◈ Members↗
FA-20271

Serial line command and data mode controller: command / payload · case 01

While command, event payload produces data/deliver instead of command/reject_data.

Protocols● Open access↗
FA-20272

Serial line command and data mode controller: command / payload · case 02

While command, event payload produces data/deliver instead of command/reject_data.

Protocols◈ Members↗
FA-20273

Serial line command and data mode controller: command / payload · case 03

While command, event payload produces data/deliver instead of command/reject_data.

Protocols◈ Members↗
FA-20274

Serial line command and data mode controller: command / payload · case 04

While command, event payload produces data/deliver instead of command/reject_data.

Protocols◈ Members↗
FA-20275

Serial line command and data mode controller: command / payload · case 05

While command, event payload produces data/deliver instead of command/reject_data.

Protocols◈ Members↗
FA-20276

Serial line command and data mode controller: data / command like payload · case 01

While data, event command_like_payload produces command/execute_command instead of data/deliver_verbatim.

Protocols● Open access↗
FA-20277

Serial line command and data mode controller: data / command like payload · case 02

While data, event command_like_payload produces command/execute_command instead of data/deliver_verbatim.

Protocols◈ Members↗
FA-20278

Serial line command and data mode controller: data / command like payload · case 03

While data, event command_like_payload produces command/execute_command instead of data/deliver_verbatim.

Protocols◈ Members↗
FA-20279

Serial line command and data mode controller: data / command like payload · case 04

While data, event command_like_payload produces command/execute_command instead of data/deliver_verbatim.

Protocols◈ Members↗
FA-20280

Serial line command and data mode controller: data / command like payload · case 05

While data, event command_like_payload produces command/execute_command instead of data/deliver_verbatim.

Protocols◈ Members↗
FA-20281

Serial line command and data mode controller: data / hangup · case 01

While data, event hangup produces data/continue instead of command/flush_close_report.

Protocols● Open access↗
FA-20282

Serial line command and data mode controller: data / hangup · case 02

While data, event hangup produces data/continue instead of command/flush_close_report.

Protocols◈ Members↗
FA-20283

Serial line command and data mode controller: data / hangup · case 03

While data, event hangup produces data/continue instead of command/flush_close_report.

Protocols◈ Members↗
FA-20284

Serial line command and data mode controller: data / hangup · case 04

While data, event hangup produces data/continue instead of command/flush_close_report.

Protocols◈ Members↗
FA-20285

Serial line command and data mode controller: data / hangup · case 05

While data, event hangup produces data/continue instead of command/flush_close_report.

Protocols◈ Members↗
FA-20286

Serial line command and data mode controller: command / line reset · case 01

While command, event line_reset produces data/enable_payload instead of command/reset_parser_report.

Protocols● Open access↗
FA-20287

Serial line command and data mode controller: command / line reset · case 02

While command, event line_reset produces data/enable_payload instead of command/reset_parser_report.

Protocols◈ Members↗
FA-20288

Serial line command and data mode controller: command / line reset · case 03

While command, event line_reset produces data/enable_payload instead of command/reset_parser_report.

Protocols◈ Members↗
FA-20289

Serial line command and data mode controller: command / line reset · case 04

While command, event line_reset produces data/enable_payload instead of command/reset_parser_report.

Protocols◈ Members↗
FA-20290

Serial line command and data mode controller: command / line reset · case 05

While command, event line_reset produces data/enable_payload instead of command/reset_parser_report.

Protocols◈ Members↗
FA-20291

Record-stream checkpoint fence controller: streaming / fence request · case 01

While streaming, event fence_request produces fenced/ack_fence instead of draining/freeze_cut.

Protocols● Open access↗
FA-20292

Record-stream checkpoint fence controller: streaming / fence request · case 02

While streaming, event fence_request produces fenced/ack_fence instead of draining/freeze_cut.

Protocols◈ Members↗
FA-20293

Record-stream checkpoint fence controller: streaming / fence request · case 03

While streaming, event fence_request produces fenced/ack_fence instead of draining/freeze_cut.

Protocols◈ Members↗
FA-20294

Record-stream checkpoint fence controller: streaming / fence request · case 04

While streaming, event fence_request produces fenced/ack_fence instead of draining/freeze_cut.

Protocols◈ Members↗
FA-20295

Record-stream checkpoint fence controller: streaming / fence request · case 05

While streaming, event fence_request produces fenced/ack_fence instead of draining/freeze_cut.

Protocols◈ Members↗
FA-20296

Record-stream checkpoint fence controller: draining / record before cut · case 01

While draining, event record_before_cut produces draining/buffer_post_cut instead of draining/deliver_pre_cut.

Protocols● Open access↗
FA-20297

Record-stream checkpoint fence controller: draining / record before cut · case 02

While draining, event record_before_cut produces draining/buffer_post_cut instead of draining/deliver_pre_cut.

Protocols◈ Members↗
FA-20298

Record-stream checkpoint fence controller: draining / record before cut · case 03

While draining, event record_before_cut produces draining/buffer_post_cut instead of draining/deliver_pre_cut.

Protocols◈ Members↗
FA-20299

Record-stream checkpoint fence controller: draining / record before cut · case 04

While draining, event record_before_cut produces draining/buffer_post_cut instead of draining/deliver_pre_cut.

Protocols◈ Members↗
FA-20300

Record-stream checkpoint fence controller: draining / record before cut · case 05

While draining, event record_before_cut produces draining/buffer_post_cut instead of draining/deliver_pre_cut.

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 ↗