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

Delimited batch command controller: collecting / seal · case 01

While collecting, event seal produces committed/apply instead of sealed/freeze_batch.

Protocols● Open access↗
FA-19702

Delimited batch command controller: collecting / seal · case 02

While collecting, event seal produces committed/apply instead of sealed/freeze_batch.

Protocols◈ Members↗
FA-19703

Delimited batch command controller: collecting / seal · case 03

While collecting, event seal produces committed/apply instead of sealed/freeze_batch.

Protocols◈ Members↗
FA-19704

Delimited batch command controller: collecting / seal · case 04

While collecting, event seal produces committed/apply instead of sealed/freeze_batch.

Protocols◈ Members↗
FA-19705

Delimited batch command controller: collecting / seal · case 05

While collecting, event seal produces committed/apply instead of sealed/freeze_batch.

Protocols◈ Members↗
FA-19706

Delimited batch command controller: sealed / commit · case 01

While sealed, event commit produces sealed/wait instead of committed/apply_once.

Protocols● Open access↗
FA-19707

Delimited batch command controller: sealed / commit · case 02

While sealed, event commit produces sealed/wait instead of committed/apply_once.

Protocols◈ Members↗
FA-19708

Delimited batch command controller: sealed / commit · case 03

While sealed, event commit produces sealed/wait instead of committed/apply_once.

Protocols◈ Members↗
FA-19709

Delimited batch command controller: sealed / commit · case 04

While sealed, event commit produces sealed/wait instead of committed/apply_once.

Protocols◈ Members↗
FA-19710

Delimited batch command controller: sealed / commit · case 05

While sealed, event commit produces sealed/wait instead of committed/apply_once.

Protocols◈ Members↗
FA-19711

Delimited batch command controller: collecting / commit · case 01

While collecting, event commit produces committed/apply instead of collecting/reject_unsealed.

Protocols● Open access↗
FA-19712

Delimited batch command controller: collecting / commit · case 02

While collecting, event commit produces committed/apply instead of collecting/reject_unsealed.

Protocols◈ Members↗
FA-19713

Delimited batch command controller: collecting / commit · case 03

While collecting, event commit produces committed/apply instead of collecting/reject_unsealed.

Protocols◈ Members↗
FA-19714

Delimited batch command controller: collecting / commit · case 04

While collecting, event commit produces committed/apply instead of collecting/reject_unsealed.

Protocols◈ Members↗
FA-19715

Delimited batch command controller: collecting / commit · case 05

While collecting, event commit produces committed/apply instead of collecting/reject_unsealed.

Protocols◈ Members↗
FA-19716

Delimited batch command controller: sealed / operation · case 01

While sealed, event operation produces collecting/stage_operation instead of sealed/reject_sealed.

Protocols● Open access↗
FA-19717

Delimited batch command controller: sealed / operation · case 02

While sealed, event operation produces collecting/stage_operation instead of sealed/reject_sealed.

Protocols◈ Members↗
FA-19718

Delimited batch command controller: sealed / operation · case 03

While sealed, event operation produces collecting/stage_operation instead of sealed/reject_sealed.

Protocols◈ Members↗
FA-19719

Delimited batch command controller: sealed / operation · case 04

While sealed, event operation produces collecting/stage_operation instead of sealed/reject_sealed.

Protocols◈ Members↗
FA-19720

Delimited batch command controller: sealed / operation · case 05

While sealed, event operation produces collecting/stage_operation instead of sealed/reject_sealed.

Protocols◈ Members↗
FA-19721

Delimited batch command controller: collecting / abort · case 01

While collecting, event abort produces committed/apply instead of idle/discard_batch.

Protocols● Open access↗
FA-19722

Delimited batch command controller: collecting / abort · case 02

While collecting, event abort produces committed/apply instead of idle/discard_batch.

Protocols◈ Members↗
FA-19723

Delimited batch command controller: collecting / abort · case 03

While collecting, event abort produces committed/apply instead of idle/discard_batch.

Protocols◈ Members↗
FA-19724

Delimited batch command controller: collecting / abort · case 04

While collecting, event abort produces committed/apply instead of idle/discard_batch.

Protocols◈ Members↗
FA-19725

Delimited batch command controller: collecting / abort · case 05

While collecting, event abort produces committed/apply instead of idle/discard_batch.

Protocols◈ Members↗
FA-19726

Delimited batch command controller: committed / duplicate commit · case 01

While committed, event duplicate_commit produces committed/apply_once instead of committed/repeat_receipt.

Protocols● Open access↗
FA-19727

Delimited batch command controller: committed / duplicate commit · case 02

While committed, event duplicate_commit produces committed/apply_once instead of committed/repeat_receipt.

Protocols◈ Members↗
FA-19728

Delimited batch command controller: committed / duplicate commit · case 03

While committed, event duplicate_commit produces committed/apply_once instead of committed/repeat_receipt.

Protocols◈ Members↗
FA-19729

Delimited batch command controller: committed / duplicate commit · case 04

While committed, event duplicate_commit produces committed/apply_once instead of committed/repeat_receipt.

Protocols◈ Members↗
FA-19730

Delimited batch command controller: committed / duplicate commit · case 05

While committed, event duplicate_commit produces committed/apply_once instead of committed/repeat_receipt.

Protocols◈ Members↗
FA-19731

Delimited batch command controller: sealed / validation failed · case 01

While sealed, event validation_failed produces committed/apply instead of idle/reject_discard.

Protocols● Open access↗
FA-19732

Delimited batch command controller: sealed / validation failed · case 02

While sealed, event validation_failed produces committed/apply instead of idle/reject_discard.

Protocols◈ Members↗
FA-19733

Delimited batch command controller: sealed / validation failed · case 03

While sealed, event validation_failed produces committed/apply instead of idle/reject_discard.

Protocols◈ Members↗
FA-19734

Delimited batch command controller: sealed / validation failed · case 04

While sealed, event validation_failed produces committed/apply instead of idle/reject_discard.

Protocols◈ Members↗
FA-19735

Delimited batch command controller: sealed / validation failed · case 05

While sealed, event validation_failed produces committed/apply instead of idle/reject_discard.

Protocols◈ Members↗
FA-19736

Delimited batch command controller: committed / receipt consumed · case 01

While committed, event receipt_consumed produces committed/retain instead of idle/release_receipt.

Protocols● Open access↗
FA-19737

Delimited batch command controller: committed / receipt consumed · case 02

While committed, event receipt_consumed produces committed/retain instead of idle/release_receipt.

Protocols◈ Members↗
FA-19738

Delimited batch command controller: committed / receipt consumed · case 03

While committed, event receipt_consumed produces committed/retain instead of idle/release_receipt.

Protocols◈ Members↗
FA-19739

Delimited batch command controller: committed / receipt consumed · case 04

While committed, event receipt_consumed produces committed/retain instead of idle/release_receipt.

Protocols◈ Members↗
FA-19740

Delimited batch command controller: committed / receipt consumed · case 05

While committed, event receipt_consumed produces committed/retain instead of idle/release_receipt.

Protocols◈ Members↗
FA-19741

Exclusive owner handoff controller: owned / handoff request · case 01

While owned, event handoff_request produces released/drop_owner instead of offering/send_offer.

Protocols● Open access↗
FA-19742

Exclusive owner handoff controller: owned / handoff request · case 02

While owned, event handoff_request produces released/drop_owner instead of offering/send_offer.

Protocols◈ Members↗
FA-19743

Exclusive owner handoff controller: owned / handoff request · case 03

While owned, event handoff_request produces released/drop_owner instead of offering/send_offer.

Protocols◈ Members↗
FA-19744

Exclusive owner handoff controller: owned / handoff request · case 04

While owned, event handoff_request produces released/drop_owner instead of offering/send_offer.

Protocols◈ Members↗
FA-19745

Exclusive owner handoff controller: owned / handoff request · case 05

While owned, event handoff_request produces released/drop_owner instead of offering/send_offer.

Protocols◈ Members↗
FA-19746

Exclusive owner handoff controller: offering / peer ready · case 01

While offering, event peer_ready produces owned/continue_local instead of fenced/fence_local.

Protocols● Open access↗
FA-19747

Exclusive owner handoff controller: offering / peer ready · case 02

While offering, event peer_ready produces owned/continue_local instead of fenced/fence_local.

Protocols◈ Members↗
FA-19748

Exclusive owner handoff controller: offering / peer ready · case 03

While offering, event peer_ready produces owned/continue_local instead of fenced/fence_local.

Protocols◈ Members↗
FA-19749

Exclusive owner handoff controller: offering / peer ready · case 04

While offering, event peer_ready produces owned/continue_local instead of fenced/fence_local.

Protocols◈ Members↗
FA-19750

Exclusive owner handoff controller: offering / peer ready · case 05

While offering, event peer_ready produces owned/continue_local instead of fenced/fence_local.

Protocols◈ Members↗
FA-19751

Exclusive owner handoff controller: fenced / fence confirmed · case 01

While fenced, event fence_confirmed produces released/drop_record instead of transferring/send_grant.

Protocols● Open access↗
FA-19752

Exclusive owner handoff controller: fenced / fence confirmed · case 02

While fenced, event fence_confirmed produces released/drop_record instead of transferring/send_grant.

Protocols◈ Members↗
FA-19753

Exclusive owner handoff controller: fenced / fence confirmed · case 03

While fenced, event fence_confirmed produces released/drop_record instead of transferring/send_grant.

Protocols◈ Members↗
FA-19754

Exclusive owner handoff controller: fenced / fence confirmed · case 04

While fenced, event fence_confirmed produces released/drop_record instead of transferring/send_grant.

Protocols◈ Members↗
FA-19755

Exclusive owner handoff controller: fenced / fence confirmed · case 05

While fenced, event fence_confirmed produces released/drop_record instead of transferring/send_grant.

Protocols◈ Members↗
FA-19756

Exclusive owner handoff controller: transferring / grant ack · case 01

While transferring, event grant_ack produces owned/resume_local instead of released/forget_local_owner.

Protocols● Open access↗
FA-19757

Exclusive owner handoff controller: transferring / grant ack · case 02

While transferring, event grant_ack produces owned/resume_local instead of released/forget_local_owner.

Protocols◈ Members↗
FA-19758

Exclusive owner handoff controller: transferring / grant ack · case 03

While transferring, event grant_ack produces owned/resume_local instead of released/forget_local_owner.

Protocols◈ Members↗
FA-19759

Exclusive owner handoff controller: transferring / grant ack · case 04

While transferring, event grant_ack produces owned/resume_local instead of released/forget_local_owner.

Protocols◈ Members↗
FA-19760

Exclusive owner handoff controller: transferring / grant ack · case 05

While transferring, event grant_ack produces owned/resume_local instead of released/forget_local_owner.

Protocols◈ Members↗
FA-19761

Exclusive owner handoff controller: offering / peer refuses · case 01

While offering, event peer_refuses produces released/drop_owner instead of owned/withdraw_offer.

Protocols● Open access↗
FA-19762

Exclusive owner handoff controller: offering / peer refuses · case 02

While offering, event peer_refuses produces released/drop_owner instead of owned/withdraw_offer.

Protocols◈ Members↗
FA-19763

Exclusive owner handoff controller: offering / peer refuses · case 03

While offering, event peer_refuses produces released/drop_owner instead of owned/withdraw_offer.

Protocols◈ Members↗
FA-19764

Exclusive owner handoff controller: offering / peer refuses · case 04

While offering, event peer_refuses produces released/drop_owner instead of owned/withdraw_offer.

Protocols◈ Members↗
FA-19765

Exclusive owner handoff controller: offering / peer refuses · case 05

While offering, event peer_refuses produces released/drop_owner instead of owned/withdraw_offer.

Protocols◈ Members↗
FA-19766

Exclusive owner handoff controller: offering / local write · case 01

While offering, event local_write produces released/reject instead of offering/write_local.

Protocols● Open access↗
FA-19767

Exclusive owner handoff controller: offering / local write · case 02

While offering, event local_write produces released/reject instead of offering/write_local.

Protocols◈ Members↗
FA-19768

Exclusive owner handoff controller: offering / local write · case 03

While offering, event local_write produces released/reject instead of offering/write_local.

Protocols◈ Members↗
FA-19769

Exclusive owner handoff controller: offering / local write · case 04

While offering, event local_write produces released/reject instead of offering/write_local.

Protocols◈ Members↗
FA-19770

Exclusive owner handoff controller: offering / local write · case 05

While offering, event local_write produces released/reject instead of offering/write_local.

Protocols◈ Members↗
FA-19771

Exclusive owner handoff controller: fenced / local write · case 01

While fenced, event local_write produces owned/write_local instead of fenced/reject_fenced.

Protocols● Open access↗
FA-19772

Exclusive owner handoff controller: fenced / local write · case 02

While fenced, event local_write produces owned/write_local instead of fenced/reject_fenced.

Protocols◈ Members↗
FA-19773

Exclusive owner handoff controller: fenced / local write · case 03

While fenced, event local_write produces owned/write_local instead of fenced/reject_fenced.

Protocols◈ Members↗
FA-19774

Exclusive owner handoff controller: fenced / local write · case 04

While fenced, event local_write produces owned/write_local instead of fenced/reject_fenced.

Protocols◈ Members↗
FA-19775

Exclusive owner handoff controller: fenced / local write · case 05

While fenced, event local_write produces owned/write_local instead of fenced/reject_fenced.

Protocols◈ Members↗
FA-19776

Exclusive owner handoff controller: released / local write · case 01

While released, event local_write produces owned/write_local instead of released/reject_not_owner.

Protocols● Open access↗
FA-19777

Exclusive owner handoff controller: released / local write · case 02

While released, event local_write produces owned/write_local instead of released/reject_not_owner.

Protocols◈ Members↗
FA-19778

Exclusive owner handoff controller: released / local write · case 03

While released, event local_write produces owned/write_local instead of released/reject_not_owner.

Protocols◈ Members↗
FA-19779

Exclusive owner handoff controller: released / local write · case 04

While released, event local_write produces owned/write_local instead of released/reject_not_owner.

Protocols◈ Members↗
FA-19780

Exclusive owner handoff controller: released / local write · case 05

While released, event local_write produces owned/write_local instead of released/reject_not_owner.

Protocols◈ Members↗
FA-19781

Exclusive owner handoff controller: transferring / duplicate ready · case 01

While transferring, event duplicate_ready produces offering/send_offer instead of transferring/repeat_grant.

Protocols● Open access↗
FA-19782

Exclusive owner handoff controller: transferring / duplicate ready · case 02

While transferring, event duplicate_ready produces offering/send_offer instead of transferring/repeat_grant.

Protocols◈ Members↗
FA-19783

Exclusive owner handoff controller: transferring / duplicate ready · case 03

While transferring, event duplicate_ready produces offering/send_offer instead of transferring/repeat_grant.

Protocols◈ Members↗
FA-19784

Exclusive owner handoff controller: transferring / duplicate ready · case 04

While transferring, event duplicate_ready produces offering/send_offer instead of transferring/repeat_grant.

Protocols◈ Members↗
FA-19785

Exclusive owner handoff controller: transferring / duplicate ready · case 05

While transferring, event duplicate_ready produces offering/send_offer instead of transferring/repeat_grant.

Protocols◈ Members↗
FA-19786

Exclusive owner handoff controller: owned / unsolicited ack · case 01

While owned, event unsolicited_ack produces released/forget_local_owner instead of owned/reject_unoffered.

Protocols● Open access↗
FA-19787

Exclusive owner handoff controller: owned / unsolicited ack · case 02

While owned, event unsolicited_ack produces released/forget_local_owner instead of owned/reject_unoffered.

Protocols◈ Members↗
FA-19788

Exclusive owner handoff controller: owned / unsolicited ack · case 03

While owned, event unsolicited_ack produces released/forget_local_owner instead of owned/reject_unoffered.

Protocols◈ Members↗
FA-19789

Exclusive owner handoff controller: owned / unsolicited ack · case 04

While owned, event unsolicited_ack produces released/forget_local_owner instead of owned/reject_unoffered.

Protocols◈ Members↗
FA-19790

Exclusive owner handoff controller: owned / unsolicited ack · case 05

While owned, event unsolicited_ack produces released/forget_local_owner instead of owned/reject_unoffered.

Protocols◈ Members↗
FA-19791

Peer configuration epoch activation controller: active / propose · case 01

While active, event propose produces active/activate_config instead of pending/stage_config.

Protocols● Open access↗
FA-19792

Peer configuration epoch activation controller: active / propose · case 02

While active, event propose produces active/activate_config instead of pending/stage_config.

Protocols◈ Members↗
FA-19793

Peer configuration epoch activation controller: active / propose · case 03

While active, event propose produces active/activate_config instead of pending/stage_config.

Protocols◈ Members↗
FA-19794

Peer configuration epoch activation controller: active / propose · case 04

While active, event propose produces active/activate_config instead of pending/stage_config.

Protocols◈ Members↗
FA-19795

Peer configuration epoch activation controller: active / propose · case 05

While active, event propose produces active/activate_config instead of pending/stage_config.

Protocols◈ Members↗
FA-19796

Peer configuration epoch activation controller: pending / validated · case 01

While pending, event validated produces active/activate_config instead of prepared/send_prepared.

Protocols● Open access↗
FA-19797

Peer configuration epoch activation controller: pending / validated · case 02

While pending, event validated produces active/activate_config instead of prepared/send_prepared.

Protocols◈ Members↗
FA-19798

Peer configuration epoch activation controller: pending / validated · case 03

While pending, event validated produces active/activate_config instead of prepared/send_prepared.

Protocols◈ Members↗
FA-19799

Peer configuration epoch activation controller: pending / validated · case 04

While pending, event validated produces active/activate_config instead of prepared/send_prepared.

Protocols◈ Members↗
FA-19800

Peer configuration epoch activation controller: pending / validated · case 05

While pending, event validated produces active/activate_config instead of prepared/send_prepared.

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 ↗