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

Capability-offer negotiation controller: offered / counteroffer · case 01

While offered, event counteroffer produces active/enable instead of countered/validate.

Protocols● Open access↗
FA-18902

Capability-offer negotiation controller: offered / counteroffer · case 02

While offered, event counteroffer produces active/enable instead of countered/validate.

Protocols◈ Members↗
FA-18903

Capability-offer negotiation controller: offered / counteroffer · case 03

While offered, event counteroffer produces active/enable instead of countered/validate.

Protocols◈ Members↗
FA-18904

Capability-offer negotiation controller: offered / counteroffer · case 04

While offered, event counteroffer produces active/enable instead of countered/validate.

Protocols◈ Members↗
FA-18905

Capability-offer negotiation controller: offered / counteroffer · case 05

While offered, event counteroffer produces active/enable instead of countered/validate.

Protocols◈ Members↗
FA-18906

Capability-offer negotiation controller: countered / compatible · case 01

While countered, event compatible produces countered/wait instead of active/confirm.

Protocols● Open access↗
FA-18907

Capability-offer negotiation controller: countered / compatible · case 02

While countered, event compatible produces countered/wait instead of active/confirm.

Protocols◈ Members↗
FA-18908

Capability-offer negotiation controller: countered / compatible · case 03

While countered, event compatible produces countered/wait instead of active/confirm.

Protocols◈ Members↗
FA-18909

Capability-offer negotiation controller: countered / compatible · case 04

While countered, event compatible produces countered/wait instead of active/confirm.

Protocols◈ Members↗
FA-18910

Capability-offer negotiation controller: countered / compatible · case 05

While countered, event compatible produces countered/wait instead of active/confirm.

Protocols◈ Members↗
FA-18911

Capability-offer negotiation controller: countered / incompatible · case 01

While countered, event incompatible produces active/enable instead of failed/reject.

Protocols● Open access↗
FA-18912

Capability-offer negotiation controller: countered / incompatible · case 02

While countered, event incompatible produces active/enable instead of failed/reject.

Protocols◈ Members↗
FA-18913

Capability-offer negotiation controller: countered / incompatible · case 03

While countered, event incompatible produces active/enable instead of failed/reject.

Protocols◈ Members↗
FA-18914

Capability-offer negotiation controller: countered / incompatible · case 04

While countered, event incompatible produces active/enable instead of failed/reject.

Protocols◈ Members↗
FA-18915

Capability-offer negotiation controller: countered / incompatible · case 05

While countered, event incompatible produces active/enable instead of failed/reject.

Protocols◈ Members↗
FA-18916

Capability-offer negotiation controller: offered / mandatory missing · case 01

While offered, event mandatory_missing produces active/enable_subset instead of failed/reject.

Protocols● Open access↗
FA-18917

Capability-offer negotiation controller: offered / mandatory missing · case 02

While offered, event mandatory_missing produces active/enable_subset instead of failed/reject.

Protocols◈ Members↗
FA-18918

Capability-offer negotiation controller: offered / mandatory missing · case 03

While offered, event mandatory_missing produces active/enable_subset instead of failed/reject.

Protocols◈ Members↗
FA-18919

Capability-offer negotiation controller: offered / mandatory missing · case 04

While offered, event mandatory_missing produces active/enable_subset instead of failed/reject.

Protocols◈ Members↗
FA-18920

Capability-offer negotiation controller: offered / mandatory missing · case 05

While offered, event mandatory_missing produces active/enable_subset instead of failed/reject.

Protocols◈ Members↗
FA-18921

Capability-offer negotiation controller: active / renegotiate · case 01

While active, event renegotiate produces active/advertise instead of offered/quiesce.

Protocols● Open access↗
FA-18922

Capability-offer negotiation controller: active / renegotiate · case 02

While active, event renegotiate produces active/advertise instead of offered/quiesce.

Protocols◈ Members↗
FA-18923

Capability-offer negotiation controller: active / renegotiate · case 03

While active, event renegotiate produces active/advertise instead of offered/quiesce.

Protocols◈ Members↗
FA-18924

Capability-offer negotiation controller: active / renegotiate · case 04

While active, event renegotiate produces active/advertise instead of offered/quiesce.

Protocols◈ Members↗
FA-18925

Capability-offer negotiation controller: active / renegotiate · case 05

While active, event renegotiate produces active/advertise instead of offered/quiesce.

Protocols◈ Members↗
FA-18926

Capability-offer negotiation controller: active / duplicate accept · case 01

While active, event duplicate_accept produces active/reenable instead of active/ack_existing.

Protocols● Open access↗
FA-18927

Capability-offer negotiation controller: active / duplicate accept · case 02

While active, event duplicate_accept produces active/reenable instead of active/ack_existing.

Protocols◈ Members↗
FA-18928

Capability-offer negotiation controller: active / duplicate accept · case 03

While active, event duplicate_accept produces active/reenable instead of active/ack_existing.

Protocols◈ Members↗
FA-18929

Capability-offer negotiation controller: active / duplicate accept · case 04

While active, event duplicate_accept produces active/reenable instead of active/ack_existing.

Protocols◈ Members↗
FA-18930

Capability-offer negotiation controller: active / duplicate accept · case 05

While active, event duplicate_accept produces active/reenable instead of active/ack_existing.

Protocols◈ Members↗
FA-18931

Capability-offer negotiation controller: failed / payload · case 01

While failed, event payload produces active/deliver instead of failed/reject.

Protocols● Open access↗
FA-18932

Capability-offer negotiation controller: failed / payload · case 02

While failed, event payload produces active/deliver instead of failed/reject.

Protocols◈ Members↗
FA-18933

Capability-offer negotiation controller: failed / payload · case 03

While failed, event payload produces active/deliver instead of failed/reject.

Protocols◈ Members↗
FA-18934

Capability-offer negotiation controller: failed / payload · case 04

While failed, event payload produces active/deliver instead of failed/reject.

Protocols◈ Members↗
FA-18935

Capability-offer negotiation controller: failed / payload · case 05

While failed, event payload produces active/deliver instead of failed/reject.

Protocols◈ Members↗
FA-18936

Capability-offer negotiation controller: fresh / payload · case 01

While fresh, event payload produces active/deliver instead of fresh/reject.

Protocols● Open access↗
FA-18937

Capability-offer negotiation controller: fresh / payload · case 02

While fresh, event payload produces active/deliver instead of fresh/reject.

Protocols◈ Members↗
FA-18938

Capability-offer negotiation controller: fresh / payload · case 03

While fresh, event payload produces active/deliver instead of fresh/reject.

Protocols◈ Members↗
FA-18939

Capability-offer negotiation controller: fresh / payload · case 04

While fresh, event payload produces active/deliver instead of fresh/reject.

Protocols◈ Members↗
FA-18940

Capability-offer negotiation controller: fresh / payload · case 05

While fresh, event payload produces active/deliver instead of fresh/reject.

Protocols◈ Members↗
FA-18941

Multiplexed logical-channel admission controller: absent / open local · case 01

While absent, event open_local produces ready/send_data instead of pending/send_open.

Protocols● Open access↗
FA-18942

Multiplexed logical-channel admission controller: absent / open local · case 02

While absent, event open_local produces ready/send_data instead of pending/send_open.

Protocols◈ Members↗
FA-18943

Multiplexed logical-channel admission controller: absent / open local · case 03

While absent, event open_local produces ready/send_data instead of pending/send_open.

Protocols◈ Members↗
FA-18944

Multiplexed logical-channel admission controller: absent / open local · case 04

While absent, event open_local produces ready/send_data instead of pending/send_open.

Protocols◈ Members↗
FA-18945

Multiplexed logical-channel admission controller: absent / open local · case 05

While absent, event open_local produces ready/send_data instead of pending/send_open.

Protocols◈ Members↗
FA-18946

Multiplexed logical-channel admission controller: pending / accepted · case 01

While pending, event accepted produces pending/wait instead of ready/notify_ready.

Protocols● Open access↗
FA-18947

Multiplexed logical-channel admission controller: pending / accepted · case 02

While pending, event accepted produces pending/wait instead of ready/notify_ready.

Protocols◈ Members↗
FA-18948

Multiplexed logical-channel admission controller: pending / accepted · case 03

While pending, event accepted produces pending/wait instead of ready/notify_ready.

Protocols◈ Members↗
FA-18949

Multiplexed logical-channel admission controller: pending / accepted · case 04

While pending, event accepted produces pending/wait instead of ready/notify_ready.

Protocols◈ Members↗
FA-18950

Multiplexed logical-channel admission controller: pending / accepted · case 05

While pending, event accepted produces pending/wait instead of ready/notify_ready.

Protocols◈ Members↗
FA-18951

Multiplexed logical-channel admission controller: pending / refused · case 01

While pending, event refused produces ready/notify_ready instead of absent/notify_refused.

Protocols● Open access↗
FA-18952

Multiplexed logical-channel admission controller: pending / refused · case 02

While pending, event refused produces ready/notify_ready instead of absent/notify_refused.

Protocols◈ Members↗
FA-18953

Multiplexed logical-channel admission controller: pending / refused · case 03

While pending, event refused produces ready/notify_ready instead of absent/notify_refused.

Protocols◈ Members↗
FA-18954

Multiplexed logical-channel admission controller: pending / refused · case 04

While pending, event refused produces ready/notify_ready instead of absent/notify_refused.

Protocols◈ Members↗
FA-18955

Multiplexed logical-channel admission controller: pending / refused · case 05

While pending, event refused produces ready/notify_ready instead of absent/notify_refused.

Protocols◈ Members↗
FA-18956

Multiplexed logical-channel admission controller: absent / open remote · case 01

While absent, event open_remote produces ready/accept instead of checking/check_policy.

Protocols● Open access↗
FA-18957

Multiplexed logical-channel admission controller: absent / open remote · case 02

While absent, event open_remote produces ready/accept instead of checking/check_policy.

Protocols◈ Members↗
FA-18958

Multiplexed logical-channel admission controller: absent / open remote · case 03

While absent, event open_remote produces ready/accept instead of checking/check_policy.

Protocols◈ Members↗
FA-18959

Multiplexed logical-channel admission controller: absent / open remote · case 04

While absent, event open_remote produces ready/accept instead of checking/check_policy.

Protocols◈ Members↗
FA-18960

Multiplexed logical-channel admission controller: absent / open remote · case 05

While absent, event open_remote produces ready/accept instead of checking/check_policy.

Protocols◈ Members↗
FA-18961

Multiplexed logical-channel admission controller: checking / allowed · case 01

While checking, event allowed produces checking/wait instead of ready/accept.

Protocols● Open access↗
FA-18962

Multiplexed logical-channel admission controller: checking / allowed · case 02

While checking, event allowed produces checking/wait instead of ready/accept.

Protocols◈ Members↗
FA-18963

Multiplexed logical-channel admission controller: checking / allowed · case 03

While checking, event allowed produces checking/wait instead of ready/accept.

Protocols◈ Members↗
FA-18964

Multiplexed logical-channel admission controller: checking / allowed · case 04

While checking, event allowed produces checking/wait instead of ready/accept.

Protocols◈ Members↗
FA-18965

Multiplexed logical-channel admission controller: checking / allowed · case 05

While checking, event allowed produces checking/wait instead of ready/accept.

Protocols◈ Members↗
FA-18966

Multiplexed logical-channel admission controller: checking / denied · case 01

While checking, event denied produces ready/accept instead of absent/refuse.

Protocols● Open access↗
FA-18967

Multiplexed logical-channel admission controller: checking / denied · case 02

While checking, event denied produces ready/accept instead of absent/refuse.

Protocols◈ Members↗
FA-18968

Multiplexed logical-channel admission controller: checking / denied · case 03

While checking, event denied produces ready/accept instead of absent/refuse.

Protocols◈ Members↗
FA-18969

Multiplexed logical-channel admission controller: checking / denied · case 04

While checking, event denied produces ready/accept instead of absent/refuse.

Protocols◈ Members↗
FA-18970

Multiplexed logical-channel admission controller: checking / denied · case 05

While checking, event denied produces ready/accept instead of absent/refuse.

Protocols◈ Members↗
FA-18971

Multiplexed logical-channel admission controller: pending / data · case 01

While pending, event data produces ready/deliver instead of pending/reject.

Protocols● Open access↗
FA-18972

Multiplexed logical-channel admission controller: pending / data · case 02

While pending, event data produces ready/deliver instead of pending/reject.

Protocols◈ Members↗
FA-18973

Multiplexed logical-channel admission controller: pending / data · case 03

While pending, event data produces ready/deliver instead of pending/reject.

Protocols◈ Members↗
FA-18974

Multiplexed logical-channel admission controller: pending / data · case 04

While pending, event data produces ready/deliver instead of pending/reject.

Protocols◈ Members↗
FA-18975

Multiplexed logical-channel admission controller: pending / data · case 05

While pending, event data produces ready/deliver instead of pending/reject.

Protocols◈ Members↗
FA-18976

Multiplexed logical-channel admission controller: ready / reset · case 01

While ready, event reset produces ready/ignore instead of absent/notify_reset.

Protocols● Open access↗
FA-18977

Multiplexed logical-channel admission controller: ready / reset · case 02

While ready, event reset produces ready/ignore instead of absent/notify_reset.

Protocols◈ Members↗
FA-18978

Multiplexed logical-channel admission controller: ready / reset · case 03

While ready, event reset produces ready/ignore instead of absent/notify_reset.

Protocols◈ Members↗
FA-18979

Multiplexed logical-channel admission controller: ready / reset · case 04

While ready, event reset produces ready/ignore instead of absent/notify_reset.

Protocols◈ Members↗
FA-18980

Multiplexed logical-channel admission controller: ready / reset · case 05

While ready, event reset produces ready/ignore instead of absent/notify_reset.

Protocols◈ Members↗
FA-18981

Multiplexed logical-channel admission controller: ready / duplicate open · case 01

While ready, event duplicate_open produces checking/check_policy instead of ready/repeat_accept.

Protocols● Open access↗
FA-18982

Multiplexed logical-channel admission controller: ready / duplicate open · case 02

While ready, event duplicate_open produces checking/check_policy instead of ready/repeat_accept.

Protocols◈ Members↗
FA-18983

Multiplexed logical-channel admission controller: ready / duplicate open · case 03

While ready, event duplicate_open produces checking/check_policy instead of ready/repeat_accept.

Protocols◈ Members↗
FA-18984

Multiplexed logical-channel admission controller: ready / duplicate open · case 04

While ready, event duplicate_open produces checking/check_policy instead of ready/repeat_accept.

Protocols◈ Members↗
FA-18985

Multiplexed logical-channel admission controller: ready / duplicate open · case 05

While ready, event duplicate_open produces checking/check_policy instead of ready/repeat_accept.

Protocols◈ Members↗
FA-18986

Multiplexed logical-channel admission controller: absent / accepted · case 01

While absent, event accepted produces ready/notify_ready instead of absent/reject.

Protocols● Open access↗
FA-18987

Multiplexed logical-channel admission controller: absent / accepted · case 02

While absent, event accepted produces ready/notify_ready instead of absent/reject.

Protocols◈ Members↗
FA-18988

Multiplexed logical-channel admission controller: absent / accepted · case 03

While absent, event accepted produces ready/notify_ready instead of absent/reject.

Protocols◈ Members↗
FA-18989

Multiplexed logical-channel admission controller: absent / accepted · case 04

While absent, event accepted produces ready/notify_ready instead of absent/reject.

Protocols◈ Members↗
FA-18990

Multiplexed logical-channel admission controller: absent / accepted · case 05

While absent, event accepted produces ready/notify_ready instead of absent/reject.

Protocols◈ Members↗
FA-18991

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

While none, event grant produces none/ignore instead of usable/record_grant.

Protocols● Open access↗
FA-18992

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

While none, event grant produces none/ignore instead of usable/record_grant.

Protocols◈ Members↗
FA-18993

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

While none, event grant produces none/ignore instead of usable/record_grant.

Protocols◈ Members↗
FA-18994

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

While none, event grant produces none/ignore instead of usable/record_grant.

Protocols◈ Members↗
FA-18995

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

While none, event grant produces none/ignore instead of usable/record_grant.

Protocols◈ Members↗
FA-18996

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

While usable, event spend_last produces usable/send_one instead of exhausted/send_one.

Protocols● Open access↗
FA-18997

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

While usable, event spend_last produces usable/send_one instead of exhausted/send_one.

Protocols◈ Members↗
FA-18998

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

While usable, event spend_last produces usable/send_one instead of exhausted/send_one.

Protocols◈ Members↗
FA-18999

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

While usable, event spend_last produces usable/send_one instead of exhausted/send_one.

Protocols◈ Members↗
FA-19000

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

While usable, event spend_last produces usable/send_one instead of exhausted/send_one.

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 ↗