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

Compression dictionary installation controller: offered / cache miss · case 01

While offered, event cache_miss produces active/compress instead of installing/send_dictionary.

Protocols● Open access↗
FA-19302

Compression dictionary installation controller: offered / cache miss · case 02

While offered, event cache_miss produces active/compress instead of installing/send_dictionary.

Protocols◈ Members↗
FA-19303

Compression dictionary installation controller: offered / cache miss · case 03

While offered, event cache_miss produces active/compress instead of installing/send_dictionary.

Protocols◈ Members↗
FA-19304

Compression dictionary installation controller: offered / cache miss · case 04

While offered, event cache_miss produces active/compress instead of installing/send_dictionary.

Protocols◈ Members↗
FA-19305

Compression dictionary installation controller: offered / cache miss · case 05

While offered, event cache_miss produces active/compress instead of installing/send_dictionary.

Protocols◈ Members↗
FA-19306

Compression dictionary installation controller: installing / verified · case 01

While installing, event verified produces active/compress_without_confirm instead of active/confirm_install.

Protocols● Open access↗
FA-19307

Compression dictionary installation controller: installing / verified · case 02

While installing, event verified produces active/compress_without_confirm instead of active/confirm_install.

Protocols◈ Members↗
FA-19308

Compression dictionary installation controller: installing / verified · case 03

While installing, event verified produces active/compress_without_confirm instead of active/confirm_install.

Protocols◈ Members↗
FA-19309

Compression dictionary installation controller: installing / verified · case 04

While installing, event verified produces active/compress_without_confirm instead of active/confirm_install.

Protocols◈ Members↗
FA-19310

Compression dictionary installation controller: installing / verified · case 05

While installing, event verified produces active/compress_without_confirm instead of active/confirm_install.

Protocols◈ Members↗
FA-19311

Compression dictionary installation controller: installing / bad fingerprint · case 01

While installing, event bad_fingerprint produces active/compress instead of empty/reject_dictionary.

Protocols● Open access↗
FA-19312

Compression dictionary installation controller: installing / bad fingerprint · case 02

While installing, event bad_fingerprint produces active/compress instead of empty/reject_dictionary.

Protocols◈ Members↗
FA-19313

Compression dictionary installation controller: installing / bad fingerprint · case 03

While installing, event bad_fingerprint produces active/compress instead of empty/reject_dictionary.

Protocols◈ Members↗
FA-19314

Compression dictionary installation controller: installing / bad fingerprint · case 04

While installing, event bad_fingerprint produces active/compress instead of empty/reject_dictionary.

Protocols◈ Members↗
FA-19315

Compression dictionary installation controller: installing / bad fingerprint · case 05

While installing, event bad_fingerprint produces active/compress instead of empty/reject_dictionary.

Protocols◈ Members↗
FA-19316

Compression dictionary installation controller: active / replacement offer · case 01

While active, event replacement_offer produces active/switch_immediately instead of switching/pause_old_epoch.

Protocols● Open access↗
FA-19317

Compression dictionary installation controller: active / replacement offer · case 02

While active, event replacement_offer produces active/switch_immediately instead of switching/pause_old_epoch.

Protocols◈ Members↗
FA-19318

Compression dictionary installation controller: active / replacement offer · case 03

While active, event replacement_offer produces active/switch_immediately instead of switching/pause_old_epoch.

Protocols◈ Members↗
FA-19319

Compression dictionary installation controller: active / replacement offer · case 04

While active, event replacement_offer produces active/switch_immediately instead of switching/pause_old_epoch.

Protocols◈ Members↗
FA-19320

Compression dictionary installation controller: active / replacement offer · case 05

While active, event replacement_offer produces active/switch_immediately instead of switching/pause_old_epoch.

Protocols◈ Members↗
FA-19321

Compression dictionary installation controller: switching / replacement ready · case 01

While switching, event replacement_ready produces switching/wait instead of active/switch_epoch.

Protocols● Open access↗
FA-19322

Compression dictionary installation controller: switching / replacement ready · case 02

While switching, event replacement_ready produces switching/wait instead of active/switch_epoch.

Protocols◈ Members↗
FA-19323

Compression dictionary installation controller: switching / replacement ready · case 03

While switching, event replacement_ready produces switching/wait instead of active/switch_epoch.

Protocols◈ Members↗
FA-19324

Compression dictionary installation controller: switching / replacement ready · case 04

While switching, event replacement_ready produces switching/wait instead of active/switch_epoch.

Protocols◈ Members↗
FA-19325

Compression dictionary installation controller: switching / replacement ready · case 05

While switching, event replacement_ready produces switching/wait instead of active/switch_epoch.

Protocols◈ Members↗
FA-19326

Compression dictionary installation controller: switching / replacement failed · case 01

While switching, event replacement_failed produces empty/discard_old instead of active/resume_old_epoch.

Protocols● Open access↗
FA-19327

Compression dictionary installation controller: switching / replacement failed · case 02

While switching, event replacement_failed produces empty/discard_old instead of active/resume_old_epoch.

Protocols◈ Members↗
FA-19328

Compression dictionary installation controller: switching / replacement failed · case 03

While switching, event replacement_failed produces empty/discard_old instead of active/resume_old_epoch.

Protocols◈ Members↗
FA-19329

Compression dictionary installation controller: switching / replacement failed · case 04

While switching, event replacement_failed produces empty/discard_old instead of active/resume_old_epoch.

Protocols◈ Members↗
FA-19330

Compression dictionary installation controller: switching / replacement failed · case 05

While switching, event replacement_failed produces empty/discard_old instead of active/resume_old_epoch.

Protocols◈ Members↗
FA-19331

Compression dictionary installation controller: empty / compressed payload · case 01

While empty, event compressed_payload produces active/decode_default instead of empty/reject_missing.

Protocols● Open access↗
FA-19332

Compression dictionary installation controller: empty / compressed payload · case 02

While empty, event compressed_payload produces active/decode_default instead of empty/reject_missing.

Protocols◈ Members↗
FA-19333

Compression dictionary installation controller: empty / compressed payload · case 03

While empty, event compressed_payload produces active/decode_default instead of empty/reject_missing.

Protocols◈ Members↗
FA-19334

Compression dictionary installation controller: empty / compressed payload · case 04

While empty, event compressed_payload produces active/decode_default instead of empty/reject_missing.

Protocols◈ Members↗
FA-19335

Compression dictionary installation controller: empty / compressed payload · case 05

While empty, event compressed_payload produces active/decode_default instead of empty/reject_missing.

Protocols◈ Members↗
FA-19336

Compression dictionary installation controller: active / evicted · case 01

While active, event evicted produces active/decode_stale instead of empty/notify_unavailable.

Protocols● Open access↗
FA-19337

Compression dictionary installation controller: active / evicted · case 02

While active, event evicted produces active/decode_stale instead of empty/notify_unavailable.

Protocols◈ Members↗
FA-19338

Compression dictionary installation controller: active / evicted · case 03

While active, event evicted produces active/decode_stale instead of empty/notify_unavailable.

Protocols◈ Members↗
FA-19339

Compression dictionary installation controller: active / evicted · case 04

While active, event evicted produces active/decode_stale instead of empty/notify_unavailable.

Protocols◈ Members↗
FA-19340

Compression dictionary installation controller: active / evicted · case 05

While active, event evicted produces active/decode_stale instead of empty/notify_unavailable.

Protocols◈ Members↗
FA-19341

Checkpoint transfer boundary controller: idle / offer · case 01

While idle, event offer produces receiving/write_chunks instead of manifest/request_manifest.

Protocols● Open access↗
FA-19342

Checkpoint transfer boundary controller: idle / offer · case 02

While idle, event offer produces receiving/write_chunks instead of manifest/request_manifest.

Protocols◈ Members↗
FA-19343

Checkpoint transfer boundary controller: idle / offer · case 03

While idle, event offer produces receiving/write_chunks instead of manifest/request_manifest.

Protocols◈ Members↗
FA-19344

Checkpoint transfer boundary controller: idle / offer · case 04

While idle, event offer produces receiving/write_chunks instead of manifest/request_manifest.

Protocols◈ Members↗
FA-19345

Checkpoint transfer boundary controller: idle / offer · case 05

While idle, event offer produces receiving/write_chunks instead of manifest/request_manifest.

Protocols◈ Members↗
FA-19346

Checkpoint transfer boundary controller: manifest / compatible · case 01

While manifest, event compatible produces installed/activate instead of receiving/allocate_staging.

Protocols● Open access↗
FA-19347

Checkpoint transfer boundary controller: manifest / compatible · case 02

While manifest, event compatible produces installed/activate instead of receiving/allocate_staging.

Protocols◈ Members↗
FA-19348

Checkpoint transfer boundary controller: manifest / compatible · case 03

While manifest, event compatible produces installed/activate instead of receiving/allocate_staging.

Protocols◈ Members↗
FA-19349

Checkpoint transfer boundary controller: manifest / compatible · case 04

While manifest, event compatible produces installed/activate instead of receiving/allocate_staging.

Protocols◈ Members↗
FA-19350

Checkpoint transfer boundary controller: manifest / compatible · case 05

While manifest, event compatible produces installed/activate instead of receiving/allocate_staging.

Protocols◈ Members↗
FA-19351

Checkpoint transfer boundary controller: manifest / incompatible · case 01

While manifest, event incompatible produces receiving/allocate_staging instead of idle/reject_offer.

Protocols● Open access↗
FA-19352

Checkpoint transfer boundary controller: manifest / incompatible · case 02

While manifest, event incompatible produces receiving/allocate_staging instead of idle/reject_offer.

Protocols◈ Members↗
FA-19353

Checkpoint transfer boundary controller: manifest / incompatible · case 03

While manifest, event incompatible produces receiving/allocate_staging instead of idle/reject_offer.

Protocols◈ Members↗
FA-19354

Checkpoint transfer boundary controller: manifest / incompatible · case 04

While manifest, event incompatible produces receiving/allocate_staging instead of idle/reject_offer.

Protocols◈ Members↗
FA-19355

Checkpoint transfer boundary controller: manifest / incompatible · case 05

While manifest, event incompatible produces receiving/allocate_staging instead of idle/reject_offer.

Protocols◈ Members↗
FA-19356

Checkpoint transfer boundary controller: receiving / chunk · case 01

While receiving, event chunk produces installed/activate instead of receiving/write_staging.

Protocols● Open access↗
FA-19357

Checkpoint transfer boundary controller: receiving / chunk · case 02

While receiving, event chunk produces installed/activate instead of receiving/write_staging.

Protocols◈ Members↗
FA-19358

Checkpoint transfer boundary controller: receiving / chunk · case 03

While receiving, event chunk produces installed/activate instead of receiving/write_staging.

Protocols◈ Members↗
FA-19359

Checkpoint transfer boundary controller: receiving / chunk · case 04

While receiving, event chunk produces installed/activate instead of receiving/write_staging.

Protocols◈ Members↗
FA-19360

Checkpoint transfer boundary controller: receiving / chunk · case 05

While receiving, event chunk produces installed/activate instead of receiving/write_staging.

Protocols◈ Members↗
FA-19361

Checkpoint transfer boundary controller: receiving / end · case 01

While receiving, event end produces installed/activate instead of verifying/verify_manifest.

Protocols● Open access↗
FA-19362

Checkpoint transfer boundary controller: receiving / end · case 02

While receiving, event end produces installed/activate instead of verifying/verify_manifest.

Protocols◈ Members↗
FA-19363

Checkpoint transfer boundary controller: receiving / end · case 03

While receiving, event end produces installed/activate instead of verifying/verify_manifest.

Protocols◈ Members↗
FA-19364

Checkpoint transfer boundary controller: receiving / end · case 04

While receiving, event end produces installed/activate instead of verifying/verify_manifest.

Protocols◈ Members↗
FA-19365

Checkpoint transfer boundary controller: receiving / end · case 05

While receiving, event end produces installed/activate instead of verifying/verify_manifest.

Protocols◈ Members↗
FA-19366

Checkpoint transfer boundary controller: verifying / valid · case 01

While verifying, event valid produces installed/copy_partial instead of installed/atomic_activate.

Protocols● Open access↗
FA-19367

Checkpoint transfer boundary controller: verifying / valid · case 02

While verifying, event valid produces installed/copy_partial instead of installed/atomic_activate.

Protocols◈ Members↗
FA-19368

Checkpoint transfer boundary controller: verifying / valid · case 03

While verifying, event valid produces installed/copy_partial instead of installed/atomic_activate.

Protocols◈ Members↗
FA-19369

Checkpoint transfer boundary controller: verifying / valid · case 04

While verifying, event valid produces installed/copy_partial instead of installed/atomic_activate.

Protocols◈ Members↗
FA-19370

Checkpoint transfer boundary controller: verifying / valid · case 05

While verifying, event valid produces installed/copy_partial instead of installed/atomic_activate.

Protocols◈ Members↗
FA-19371

Checkpoint transfer boundary controller: verifying / invalid · case 01

While verifying, event invalid produces installed/activate instead of idle/discard_staging.

Protocols● Open access↗
FA-19372

Checkpoint transfer boundary controller: verifying / invalid · case 02

While verifying, event invalid produces installed/activate instead of idle/discard_staging.

Protocols◈ Members↗
FA-19373

Checkpoint transfer boundary controller: verifying / invalid · case 03

While verifying, event invalid produces installed/activate instead of idle/discard_staging.

Protocols◈ Members↗
FA-19374

Checkpoint transfer boundary controller: verifying / invalid · case 04

While verifying, event invalid produces installed/activate instead of idle/discard_staging.

Protocols◈ Members↗
FA-19375

Checkpoint transfer boundary controller: verifying / invalid · case 05

While verifying, event invalid produces installed/activate instead of idle/discard_staging.

Protocols◈ Members↗
FA-19376

Checkpoint transfer boundary controller: receiving / cancel · case 01

While receiving, event cancel produces receiving/pause instead of idle/remove_staging.

Protocols● Open access↗
FA-19377

Checkpoint transfer boundary controller: receiving / cancel · case 02

While receiving, event cancel produces receiving/pause instead of idle/remove_staging.

Protocols◈ Members↗
FA-19378

Checkpoint transfer boundary controller: receiving / cancel · case 03

While receiving, event cancel produces receiving/pause instead of idle/remove_staging.

Protocols◈ Members↗
FA-19379

Checkpoint transfer boundary controller: receiving / cancel · case 04

While receiving, event cancel produces receiving/pause instead of idle/remove_staging.

Protocols◈ Members↗
FA-19380

Checkpoint transfer boundary controller: receiving / cancel · case 05

While receiving, event cancel produces receiving/pause instead of idle/remove_staging.

Protocols◈ Members↗
FA-19381

Checkpoint transfer boundary controller: installed / duplicate end · case 01

While installed, event duplicate_end produces verifying/verify_manifest instead of installed/ack_installed.

Protocols● Open access↗
FA-19382

Checkpoint transfer boundary controller: installed / duplicate end · case 02

While installed, event duplicate_end produces verifying/verify_manifest instead of installed/ack_installed.

Protocols◈ Members↗
FA-19383

Checkpoint transfer boundary controller: installed / duplicate end · case 03

While installed, event duplicate_end produces verifying/verify_manifest instead of installed/ack_installed.

Protocols◈ Members↗
FA-19384

Checkpoint transfer boundary controller: installed / duplicate end · case 04

While installed, event duplicate_end produces verifying/verify_manifest instead of installed/ack_installed.

Protocols◈ Members↗
FA-19385

Checkpoint transfer boundary controller: installed / duplicate end · case 05

While installed, event duplicate_end produces verifying/verify_manifest instead of installed/ack_installed.

Protocols◈ Members↗
FA-19386

Checkpoint transfer boundary controller: idle / chunk · case 01

While idle, event chunk produces receiving/write_staging instead of idle/reject_unoffered.

Protocols● Open access↗
FA-19387

Checkpoint transfer boundary controller: idle / chunk · case 02

While idle, event chunk produces receiving/write_staging instead of idle/reject_unoffered.

Protocols◈ Members↗
FA-19388

Checkpoint transfer boundary controller: idle / chunk · case 03

While idle, event chunk produces receiving/write_staging instead of idle/reject_unoffered.

Protocols◈ Members↗
FA-19389

Checkpoint transfer boundary controller: idle / chunk · case 04

While idle, event chunk produces receiving/write_staging instead of idle/reject_unoffered.

Protocols◈ Members↗
FA-19390

Checkpoint transfer boundary controller: idle / chunk · case 05

While idle, event chunk produces receiving/write_staging instead of idle/reject_unoffered.

Protocols◈ Members↗
FA-19391

Print-spool job transfer controller: idle / declare job · case 01

While idle, event declare_job produces printing/start_engine instead of declared/reserve_spool.

Protocols● Open access↗
FA-19392

Print-spool job transfer controller: idle / declare job · case 02

While idle, event declare_job produces printing/start_engine instead of declared/reserve_spool.

Protocols◈ Members↗
FA-19393

Print-spool job transfer controller: idle / declare job · case 03

While idle, event declare_job produces printing/start_engine instead of declared/reserve_spool.

Protocols◈ Members↗
FA-19394

Print-spool job transfer controller: idle / declare job · case 04

While idle, event declare_job produces printing/start_engine instead of declared/reserve_spool.

Protocols◈ Members↗
FA-19395

Print-spool job transfer controller: idle / declare job · case 05

While idle, event declare_job produces printing/start_engine instead of declared/reserve_spool.

Protocols◈ Members↗
FA-19396

Print-spool job transfer controller: declared / page begin · case 01

While declared, event page_begin produces declared/ignore instead of page/create_page.

Protocols● Open access↗
FA-19397

Print-spool job transfer controller: declared / page begin · case 02

While declared, event page_begin produces declared/ignore instead of page/create_page.

Protocols◈ Members↗
FA-19398

Print-spool job transfer controller: declared / page begin · case 03

While declared, event page_begin produces declared/ignore instead of page/create_page.

Protocols◈ Members↗
FA-19399

Print-spool job transfer controller: declared / page begin · case 04

While declared, event page_begin produces declared/ignore instead of page/create_page.

Protocols◈ Members↗
FA-19400

Print-spool job transfer controller: declared / page begin · case 05

While declared, event page_begin produces declared/ignore instead of page/create_page.

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 ↗