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

Receiver-issued transmission-credit lease controller: exhausted / payload · case 01

While exhausted, event payload produces usable/send_one instead of exhausted/backpressure.

Protocols● Open access↗
FA-19002

Receiver-issued transmission-credit lease controller: exhausted / payload · case 02

While exhausted, event payload produces usable/send_one instead of exhausted/backpressure.

Protocols◈ Members↗
FA-19003

Receiver-issued transmission-credit lease controller: exhausted / payload · case 03

While exhausted, event payload produces usable/send_one instead of exhausted/backpressure.

Protocols◈ Members↗
FA-19004

Receiver-issued transmission-credit lease controller: exhausted / payload · case 04

While exhausted, event payload produces usable/send_one instead of exhausted/backpressure.

Protocols◈ Members↗
FA-19005

Receiver-issued transmission-credit lease controller: exhausted / payload · case 05

While exhausted, event payload produces usable/send_one instead of exhausted/backpressure.

Protocols◈ Members↗
FA-19006

Receiver-issued transmission-credit lease controller: usable / revoke · case 01

While usable, event revoke produces usable/continue instead of revoked/stop_new_sends.

Protocols● Open access↗
FA-19007

Receiver-issued transmission-credit lease controller: usable / revoke · case 02

While usable, event revoke produces usable/continue instead of revoked/stop_new_sends.

Protocols◈ Members↗
FA-19008

Receiver-issued transmission-credit lease controller: usable / revoke · case 03

While usable, event revoke produces usable/continue instead of revoked/stop_new_sends.

Protocols◈ Members↗
FA-19009

Receiver-issued transmission-credit lease controller: usable / revoke · case 04

While usable, event revoke produces usable/continue instead of revoked/stop_new_sends.

Protocols◈ Members↗
FA-19010

Receiver-issued transmission-credit lease controller: usable / revoke · case 05

While usable, event revoke produces usable/continue instead of revoked/stop_new_sends.

Protocols◈ Members↗
FA-19011

Receiver-issued transmission-credit lease controller: revoked / inflight ack · case 01

While revoked, event inflight_ack produces usable/grant_credit instead of revoked/retire_inflight.

Protocols● Open access↗
FA-19012

Receiver-issued transmission-credit lease controller: revoked / inflight ack · case 02

While revoked, event inflight_ack produces usable/grant_credit instead of revoked/retire_inflight.

Protocols◈ Members↗
FA-19013

Receiver-issued transmission-credit lease controller: revoked / inflight ack · case 03

While revoked, event inflight_ack produces usable/grant_credit instead of revoked/retire_inflight.

Protocols◈ Members↗
FA-19014

Receiver-issued transmission-credit lease controller: revoked / inflight ack · case 04

While revoked, event inflight_ack produces usable/grant_credit instead of revoked/retire_inflight.

Protocols◈ Members↗
FA-19015

Receiver-issued transmission-credit lease controller: revoked / inflight ack · case 05

While revoked, event inflight_ack produces usable/grant_credit instead of revoked/retire_inflight.

Protocols◈ Members↗
FA-19016

Receiver-issued transmission-credit lease controller: revoked / new grant · case 01

While revoked, event new_grant produces revoked/ignore instead of usable/replace_lease.

Protocols● Open access↗
FA-19017

Receiver-issued transmission-credit lease controller: revoked / new grant · case 02

While revoked, event new_grant produces revoked/ignore instead of usable/replace_lease.

Protocols◈ Members↗
FA-19018

Receiver-issued transmission-credit lease controller: revoked / new grant · case 03

While revoked, event new_grant produces revoked/ignore instead of usable/replace_lease.

Protocols◈ Members↗
FA-19019

Receiver-issued transmission-credit lease controller: revoked / new grant · case 04

While revoked, event new_grant produces revoked/ignore instead of usable/replace_lease.

Protocols◈ Members↗
FA-19020

Receiver-issued transmission-credit lease controller: revoked / new grant · case 05

While revoked, event new_grant produces revoked/ignore instead of usable/replace_lease.

Protocols◈ Members↗
FA-19021

Receiver-issued transmission-credit lease controller: usable / lease expired · case 01

While usable, event lease_expired produces usable/continue instead of expired/stop_new_sends.

Protocols● Open access↗
FA-19022

Receiver-issued transmission-credit lease controller: usable / lease expired · case 02

While usable, event lease_expired produces usable/continue instead of expired/stop_new_sends.

Protocols◈ Members↗
FA-19023

Receiver-issued transmission-credit lease controller: usable / lease expired · case 03

While usable, event lease_expired produces usable/continue instead of expired/stop_new_sends.

Protocols◈ Members↗
FA-19024

Receiver-issued transmission-credit lease controller: usable / lease expired · case 04

While usable, event lease_expired produces usable/continue instead of expired/stop_new_sends.

Protocols◈ Members↗
FA-19025

Receiver-issued transmission-credit lease controller: usable / lease expired · case 05

While usable, event lease_expired produces usable/continue instead of expired/stop_new_sends.

Protocols◈ Members↗
FA-19026

Receiver-issued transmission-credit lease controller: expired / old grant · case 01

While expired, event old_grant produces usable/record_grant instead of expired/reject_stale.

Protocols● Open access↗
FA-19027

Receiver-issued transmission-credit lease controller: expired / old grant · case 02

While expired, event old_grant produces usable/record_grant instead of expired/reject_stale.

Protocols◈ Members↗
FA-19028

Receiver-issued transmission-credit lease controller: expired / old grant · case 03

While expired, event old_grant produces usable/record_grant instead of expired/reject_stale.

Protocols◈ Members↗
FA-19029

Receiver-issued transmission-credit lease controller: expired / old grant · case 04

While expired, event old_grant produces usable/record_grant instead of expired/reject_stale.

Protocols◈ Members↗
FA-19030

Receiver-issued transmission-credit lease controller: expired / old grant · case 05

While expired, event old_grant produces usable/record_grant instead of expired/reject_stale.

Protocols◈ Members↗
FA-19031

Receiver-issued transmission-credit lease controller: exhausted / refresh · case 01

While exhausted, event refresh produces exhausted/wait instead of usable/record_grant.

Protocols● Open access↗
FA-19032

Receiver-issued transmission-credit lease controller: exhausted / refresh · case 02

While exhausted, event refresh produces exhausted/wait instead of usable/record_grant.

Protocols◈ Members↗
FA-19033

Receiver-issued transmission-credit lease controller: exhausted / refresh · case 03

While exhausted, event refresh produces exhausted/wait instead of usable/record_grant.

Protocols◈ Members↗
FA-19034

Receiver-issued transmission-credit lease controller: exhausted / refresh · case 04

While exhausted, event refresh produces exhausted/wait instead of usable/record_grant.

Protocols◈ Members↗
FA-19035

Receiver-issued transmission-credit lease controller: exhausted / refresh · case 05

While exhausted, event refresh produces exhausted/wait instead of usable/record_grant.

Protocols◈ Members↗
FA-19036

Receiver-issued transmission-credit lease controller: none / ack · case 01

While none, event ack produces usable/grant_credit instead of none/reject_unsolicited.

Protocols● Open access↗
FA-19037

Receiver-issued transmission-credit lease controller: none / ack · case 02

While none, event ack produces usable/grant_credit instead of none/reject_unsolicited.

Protocols◈ Members↗
FA-19038

Receiver-issued transmission-credit lease controller: none / ack · case 03

While none, event ack produces usable/grant_credit instead of none/reject_unsolicited.

Protocols◈ Members↗
FA-19039

Receiver-issued transmission-credit lease controller: none / ack · case 04

While none, event ack produces usable/grant_credit instead of none/reject_unsolicited.

Protocols◈ Members↗
FA-19040

Receiver-issued transmission-credit lease controller: none / ack · case 05

While none, event ack produces usable/grant_credit instead of none/reject_unsolicited.

Protocols◈ Members↗
FA-19041

Segmented message assembly controller: idle / begin · case 01

While idle, event begin produces complete/publish instead of collecting/start_message.

Protocols● Open access↗
FA-19042

Segmented message assembly controller: idle / begin · case 02

While idle, event begin produces complete/publish instead of collecting/start_message.

Protocols◈ Members↗
FA-19043

Segmented message assembly controller: idle / begin · case 03

While idle, event begin produces complete/publish instead of collecting/start_message.

Protocols◈ Members↗
FA-19044

Segmented message assembly controller: idle / begin · case 04

While idle, event begin produces complete/publish instead of collecting/start_message.

Protocols◈ Members↗
FA-19045

Segmented message assembly controller: idle / begin · case 05

While idle, event begin produces complete/publish instead of collecting/start_message.

Protocols◈ Members↗
FA-19046

Segmented message assembly controller: collecting / middle · case 01

While collecting, event middle produces complete/publish instead of collecting/append.

Protocols● Open access↗
FA-19047

Segmented message assembly controller: collecting / middle · case 02

While collecting, event middle produces complete/publish instead of collecting/append.

Protocols◈ Members↗
FA-19048

Segmented message assembly controller: collecting / middle · case 03

While collecting, event middle produces complete/publish instead of collecting/append.

Protocols◈ Members↗
FA-19049

Segmented message assembly controller: collecting / middle · case 04

While collecting, event middle produces complete/publish instead of collecting/append.

Protocols◈ Members↗
FA-19050

Segmented message assembly controller: collecting / middle · case 05

While collecting, event middle produces complete/publish instead of collecting/append.

Protocols◈ Members↗
FA-19051

Segmented message assembly controller: collecting / end · case 01

While collecting, event end produces idle/discard instead of complete/append_publish.

Protocols● Open access↗
FA-19052

Segmented message assembly controller: collecting / end · case 02

While collecting, event end produces idle/discard instead of complete/append_publish.

Protocols◈ Members↗
FA-19053

Segmented message assembly controller: collecting / end · case 03

While collecting, event end produces idle/discard instead of complete/append_publish.

Protocols◈ Members↗
FA-19054

Segmented message assembly controller: collecting / end · case 04

While collecting, event end produces idle/discard instead of complete/append_publish.

Protocols◈ Members↗
FA-19055

Segmented message assembly controller: collecting / end · case 05

While collecting, event end produces idle/discard instead of complete/append_publish.

Protocols◈ Members↗
FA-19056

Segmented message assembly controller: idle / middle · case 01

While idle, event middle produces collecting/append instead of idle/reject_orphan.

Protocols● Open access↗
FA-19057

Segmented message assembly controller: idle / middle · case 02

While idle, event middle produces collecting/append instead of idle/reject_orphan.

Protocols◈ Members↗
FA-19058

Segmented message assembly controller: idle / middle · case 03

While idle, event middle produces collecting/append instead of idle/reject_orphan.

Protocols◈ Members↗
FA-19059

Segmented message assembly controller: idle / middle · case 04

While idle, event middle produces collecting/append instead of idle/reject_orphan.

Protocols◈ Members↗
FA-19060

Segmented message assembly controller: idle / middle · case 05

While idle, event middle produces collecting/append instead of idle/reject_orphan.

Protocols◈ Members↗
FA-19061

Segmented message assembly controller: idle / end · case 01

While idle, event end produces complete/publish instead of idle/reject_orphan.

Protocols● Open access↗
FA-19062

Segmented message assembly controller: idle / end · case 02

While idle, event end produces complete/publish instead of idle/reject_orphan.

Protocols◈ Members↗
FA-19063

Segmented message assembly controller: idle / end · case 03

While idle, event end produces complete/publish instead of idle/reject_orphan.

Protocols◈ Members↗
FA-19064

Segmented message assembly controller: idle / end · case 04

While idle, event end produces complete/publish instead of idle/reject_orphan.

Protocols◈ Members↗
FA-19065

Segmented message assembly controller: idle / end · case 05

While idle, event end produces complete/publish instead of idle/reject_orphan.

Protocols◈ Members↗
FA-19066

Segmented message assembly controller: collecting / begin · case 01

While collecting, event begin produces collecting/restart instead of collecting/reject_nested.

Protocols● Open access↗
FA-19067

Segmented message assembly controller: collecting / begin · case 02

While collecting, event begin produces collecting/restart instead of collecting/reject_nested.

Protocols◈ Members↗
FA-19068

Segmented message assembly controller: collecting / begin · case 03

While collecting, event begin produces collecting/restart instead of collecting/reject_nested.

Protocols◈ Members↗
FA-19069

Segmented message assembly controller: collecting / begin · case 04

While collecting, event begin produces collecting/restart instead of collecting/reject_nested.

Protocols◈ Members↗
FA-19070

Segmented message assembly controller: collecting / begin · case 05

While collecting, event begin produces collecting/restart instead of collecting/reject_nested.

Protocols◈ Members↗
FA-19071

Segmented message assembly controller: collecting / abort · case 01

While collecting, event abort produces complete/publish instead of idle/discard_partial.

Protocols● Open access↗
FA-19072

Segmented message assembly controller: collecting / abort · case 02

While collecting, event abort produces complete/publish instead of idle/discard_partial.

Protocols◈ Members↗
FA-19073

Segmented message assembly controller: collecting / abort · case 03

While collecting, event abort produces complete/publish instead of idle/discard_partial.

Protocols◈ Members↗
FA-19074

Segmented message assembly controller: collecting / abort · case 04

While collecting, event abort produces complete/publish instead of idle/discard_partial.

Protocols◈ Members↗
FA-19075

Segmented message assembly controller: collecting / abort · case 05

While collecting, event abort produces complete/publish instead of idle/discard_partial.

Protocols◈ Members↗
FA-19076

Segmented message assembly controller: complete / consume · case 01

While complete, event consume produces complete/retain instead of idle/release_message.

Protocols● Open access↗
FA-19077

Segmented message assembly controller: complete / consume · case 02

While complete, event consume produces complete/retain instead of idle/release_message.

Protocols◈ Members↗
FA-19078

Segmented message assembly controller: complete / consume · case 03

While complete, event consume produces complete/retain instead of idle/release_message.

Protocols◈ Members↗
FA-19079

Segmented message assembly controller: complete / consume · case 04

While complete, event consume produces complete/retain instead of idle/release_message.

Protocols◈ Members↗
FA-19080

Segmented message assembly controller: complete / consume · case 05

While complete, event consume produces complete/retain instead of idle/release_message.

Protocols◈ Members↗
FA-19081

Segmented message assembly controller: complete / middle · case 01

While complete, event middle produces collecting/append instead of complete/reject_sealed.

Protocols● Open access↗
FA-19082

Segmented message assembly controller: complete / middle · case 02

While complete, event middle produces collecting/append instead of complete/reject_sealed.

Protocols◈ Members↗
FA-19083

Segmented message assembly controller: complete / middle · case 03

While complete, event middle produces collecting/append instead of complete/reject_sealed.

Protocols◈ Members↗
FA-19084

Segmented message assembly controller: complete / middle · case 04

While complete, event middle produces collecting/append instead of complete/reject_sealed.

Protocols◈ Members↗
FA-19085

Segmented message assembly controller: complete / middle · case 05

While complete, event middle produces collecting/append instead of complete/reject_sealed.

Protocols◈ Members↗
FA-19086

Segmented message assembly controller: collecting / oversize · case 01

While collecting, event oversize produces collecting/truncate instead of idle/reject_discard.

Protocols● Open access↗
FA-19087

Segmented message assembly controller: collecting / oversize · case 02

While collecting, event oversize produces collecting/truncate instead of idle/reject_discard.

Protocols◈ Members↗
FA-19088

Segmented message assembly controller: collecting / oversize · case 03

While collecting, event oversize produces collecting/truncate instead of idle/reject_discard.

Protocols◈ Members↗
FA-19089

Segmented message assembly controller: collecting / oversize · case 04

While collecting, event oversize produces collecting/truncate instead of idle/reject_discard.

Protocols◈ Members↗
FA-19090

Segmented message assembly controller: collecting / oversize · case 05

While collecting, event oversize produces collecting/truncate instead of idle/reject_discard.

Protocols◈ Members↗
FA-19091

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

While idle, event dial produces connected/open_media instead of outgoing/send_invitation.

Protocols● Open access↗
FA-19092

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

While idle, event dial produces connected/open_media instead of outgoing/send_invitation.

Protocols◈ Members↗
FA-19093

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

While idle, event dial produces connected/open_media instead of outgoing/send_invitation.

Protocols◈ Members↗
FA-19094

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

While idle, event dial produces connected/open_media instead of outgoing/send_invitation.

Protocols◈ Members↗
FA-19095

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

While idle, event dial produces connected/open_media instead of outgoing/send_invitation.

Protocols◈ Members↗
FA-19096

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

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

Protocols● Open access↗
FA-19097

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

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

Protocols◈ Members↗
FA-19098

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

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

Protocols◈ Members↗
FA-19099

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

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

Protocols◈ Members↗
FA-19100

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

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

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 ↗