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

Scoped address assignment controller: offered / select · case 01

While offered, event select produces bound/use_address instead of requesting/request_selected.

Protocols● Open access↗
FA-19902

Scoped address assignment controller: offered / select · case 02

While offered, event select produces bound/use_address instead of requesting/request_selected.

Protocols◈ Members↗
FA-19903

Scoped address assignment controller: offered / select · case 03

While offered, event select produces bound/use_address instead of requesting/request_selected.

Protocols◈ Members↗
FA-19904

Scoped address assignment controller: offered / select · case 04

While offered, event select produces bound/use_address instead of requesting/request_selected.

Protocols◈ Members↗
FA-19905

Scoped address assignment controller: offered / select · case 05

While offered, event select produces bound/use_address instead of requesting/request_selected.

Protocols◈ Members↗
FA-19906

Scoped address assignment controller: requesting / ack · case 01

While requesting, event ack produces requesting/wait instead of bound/install_lease.

Protocols● Open access↗
FA-19907

Scoped address assignment controller: requesting / ack · case 02

While requesting, event ack produces requesting/wait instead of bound/install_lease.

Protocols◈ Members↗
FA-19908

Scoped address assignment controller: requesting / ack · case 03

While requesting, event ack produces requesting/wait instead of bound/install_lease.

Protocols◈ Members↗
FA-19909

Scoped address assignment controller: requesting / ack · case 04

While requesting, event ack produces requesting/wait instead of bound/install_lease.

Protocols◈ Members↗
FA-19910

Scoped address assignment controller: requesting / ack · case 05

While requesting, event ack produces requesting/wait instead of bound/install_lease.

Protocols◈ Members↗
FA-19911

Scoped address assignment controller: requesting / nack · case 01

While requesting, event nack produces bound/use_address instead of unassigned/discard_offer.

Protocols● Open access↗
FA-19912

Scoped address assignment controller: requesting / nack · case 02

While requesting, event nack produces bound/use_address instead of unassigned/discard_offer.

Protocols◈ Members↗
FA-19913

Scoped address assignment controller: requesting / nack · case 03

While requesting, event nack produces bound/use_address instead of unassigned/discard_offer.

Protocols◈ Members↗
FA-19914

Scoped address assignment controller: requesting / nack · case 04

While requesting, event nack produces bound/use_address instead of unassigned/discard_offer.

Protocols◈ Members↗
FA-19915

Scoped address assignment controller: requesting / nack · case 05

While requesting, event nack produces bound/use_address instead of unassigned/discard_offer.

Protocols◈ Members↗
FA-19916

Scoped address assignment controller: bound / renew due · case 01

While bound, event renew_due produces unassigned/clear_address instead of renewing/request_renewal.

Protocols● Open access↗
FA-19917

Scoped address assignment controller: bound / renew due · case 02

While bound, event renew_due produces unassigned/clear_address instead of renewing/request_renewal.

Protocols◈ Members↗
FA-19918

Scoped address assignment controller: bound / renew due · case 03

While bound, event renew_due produces unassigned/clear_address instead of renewing/request_renewal.

Protocols◈ Members↗
FA-19919

Scoped address assignment controller: bound / renew due · case 04

While bound, event renew_due produces unassigned/clear_address instead of renewing/request_renewal.

Protocols◈ Members↗
FA-19920

Scoped address assignment controller: bound / renew due · case 05

While bound, event renew_due produces unassigned/clear_address instead of renewing/request_renewal.

Protocols◈ Members↗
FA-19921

Scoped address assignment controller: renewing / renew ack · case 01

While renewing, event renew_ack produces renewing/wait instead of bound/replace_expiry.

Protocols● Open access↗
FA-19922

Scoped address assignment controller: renewing / renew ack · case 02

While renewing, event renew_ack produces renewing/wait instead of bound/replace_expiry.

Protocols◈ Members↗
FA-19923

Scoped address assignment controller: renewing / renew ack · case 03

While renewing, event renew_ack produces renewing/wait instead of bound/replace_expiry.

Protocols◈ Members↗
FA-19924

Scoped address assignment controller: renewing / renew ack · case 04

While renewing, event renew_ack produces renewing/wait instead of bound/replace_expiry.

Protocols◈ Members↗
FA-19925

Scoped address assignment controller: renewing / renew ack · case 05

While renewing, event renew_ack produces renewing/wait instead of bound/replace_expiry.

Protocols◈ Members↗
FA-19926

Scoped address assignment controller: renewing / expired · case 01

While renewing, event expired produces bound/use_address instead of unassigned/clear_address.

Protocols● Open access↗
FA-19927

Scoped address assignment controller: renewing / expired · case 02

While renewing, event expired produces bound/use_address instead of unassigned/clear_address.

Protocols◈ Members↗
FA-19928

Scoped address assignment controller: renewing / expired · case 03

While renewing, event expired produces bound/use_address instead of unassigned/clear_address.

Protocols◈ Members↗
FA-19929

Scoped address assignment controller: renewing / expired · case 04

While renewing, event expired produces bound/use_address instead of unassigned/clear_address.

Protocols◈ Members↗
FA-19930

Scoped address assignment controller: renewing / expired · case 05

While renewing, event expired produces bound/use_address instead of unassigned/clear_address.

Protocols◈ Members↗
FA-19931

Scoped address assignment controller: bound / conflict detected · case 01

While bound, event conflict_detected produces bound/ignore_conflict instead of unassigned/decline_clear.

Protocols● Open access↗
FA-19932

Scoped address assignment controller: bound / conflict detected · case 02

While bound, event conflict_detected produces bound/ignore_conflict instead of unassigned/decline_clear.

Protocols◈ Members↗
FA-19933

Scoped address assignment controller: bound / conflict detected · case 03

While bound, event conflict_detected produces bound/ignore_conflict instead of unassigned/decline_clear.

Protocols◈ Members↗
FA-19934

Scoped address assignment controller: bound / conflict detected · case 04

While bound, event conflict_detected produces bound/ignore_conflict instead of unassigned/decline_clear.

Protocols◈ Members↗
FA-19935

Scoped address assignment controller: bound / conflict detected · case 05

While bound, event conflict_detected produces bound/ignore_conflict instead of unassigned/decline_clear.

Protocols◈ Members↗
FA-19936

Scoped address assignment controller: bound / release · case 01

While bound, event release produces bound/retain instead of unassigned/release_clear.

Protocols● Open access↗
FA-19937

Scoped address assignment controller: bound / release · case 02

While bound, event release produces bound/retain instead of unassigned/release_clear.

Protocols◈ Members↗
FA-19938

Scoped address assignment controller: bound / release · case 03

While bound, event release produces bound/retain instead of unassigned/release_clear.

Protocols◈ Members↗
FA-19939

Scoped address assignment controller: bound / release · case 04

While bound, event release produces bound/retain instead of unassigned/release_clear.

Protocols◈ Members↗
FA-19940

Scoped address assignment controller: bound / release · case 05

While bound, event release produces bound/retain instead of unassigned/release_clear.

Protocols◈ Members↗
FA-19941

Four-event clock measurement exchange controller: idle / sync received · case 01

While idle, event sync_received produces complete/publish_offset instead of have_sync/record_receive_time.

Protocols● Open access↗
FA-19942

Four-event clock measurement exchange controller: idle / sync received · case 02

While idle, event sync_received produces complete/publish_offset instead of have_sync/record_receive_time.

Protocols◈ Members↗
FA-19943

Four-event clock measurement exchange controller: idle / sync received · case 03

While idle, event sync_received produces complete/publish_offset instead of have_sync/record_receive_time.

Protocols◈ Members↗
FA-19944

Four-event clock measurement exchange controller: idle / sync received · case 04

While idle, event sync_received produces complete/publish_offset instead of have_sync/record_receive_time.

Protocols◈ Members↗
FA-19945

Four-event clock measurement exchange controller: idle / sync received · case 05

While idle, event sync_received produces complete/publish_offset instead of have_sync/record_receive_time.

Protocols◈ Members↗
FA-19946

Four-event clock measurement exchange controller: have sync / followup received · case 01

While have_sync, event followup_received produces complete/publish_offset instead of have_origin/record_origin_time.

Protocols● Open access↗
FA-19947

Four-event clock measurement exchange controller: have sync / followup received · case 02

While have_sync, event followup_received produces complete/publish_offset instead of have_origin/record_origin_time.

Protocols◈ Members↗
FA-19948

Four-event clock measurement exchange controller: have sync / followup received · case 03

While have_sync, event followup_received produces complete/publish_offset instead of have_origin/record_origin_time.

Protocols◈ Members↗
FA-19949

Four-event clock measurement exchange controller: have sync / followup received · case 04

While have_sync, event followup_received produces complete/publish_offset instead of have_origin/record_origin_time.

Protocols◈ Members↗
FA-19950

Four-event clock measurement exchange controller: have sync / followup received · case 05

While have_sync, event followup_received produces complete/publish_offset instead of have_origin/record_origin_time.

Protocols◈ Members↗
FA-19951

Four-event clock measurement exchange controller: have origin / delay sent · case 01

While have_origin, event delay_sent produces complete/publish_offset instead of awaiting_delay/record_departure_time.

Protocols● Open access↗
FA-19952

Four-event clock measurement exchange controller: have origin / delay sent · case 02

While have_origin, event delay_sent produces complete/publish_offset instead of awaiting_delay/record_departure_time.

Protocols◈ Members↗
FA-19953

Four-event clock measurement exchange controller: have origin / delay sent · case 03

While have_origin, event delay_sent produces complete/publish_offset instead of awaiting_delay/record_departure_time.

Protocols◈ Members↗
FA-19954

Four-event clock measurement exchange controller: have origin / delay sent · case 04

While have_origin, event delay_sent produces complete/publish_offset instead of awaiting_delay/record_departure_time.

Protocols◈ Members↗
FA-19955

Four-event clock measurement exchange controller: have origin / delay sent · case 05

While have_origin, event delay_sent produces complete/publish_offset instead of awaiting_delay/record_departure_time.

Protocols◈ Members↗
FA-19956

Four-event clock measurement exchange controller: awaiting delay / delay response · case 01

While awaiting_delay, event delay_response produces awaiting_delay/wait instead of complete/compute_exchange.

Protocols● Open access↗
FA-19957

Four-event clock measurement exchange controller: awaiting delay / delay response · case 02

While awaiting_delay, event delay_response produces awaiting_delay/wait instead of complete/compute_exchange.

Protocols◈ Members↗
FA-19958

Four-event clock measurement exchange controller: awaiting delay / delay response · case 03

While awaiting_delay, event delay_response produces awaiting_delay/wait instead of complete/compute_exchange.

Protocols◈ Members↗
FA-19959

Four-event clock measurement exchange controller: awaiting delay / delay response · case 04

While awaiting_delay, event delay_response produces awaiting_delay/wait instead of complete/compute_exchange.

Protocols◈ Members↗
FA-19960

Four-event clock measurement exchange controller: awaiting delay / delay response · case 05

While awaiting_delay, event delay_response produces awaiting_delay/wait instead of complete/compute_exchange.

Protocols◈ Members↗
FA-19961

Four-event clock measurement exchange controller: have sync / wrong followup · case 01

While have_sync, event wrong_followup produces have_origin/record_origin_time instead of have_sync/reject_sequence.

Protocols● Open access↗
FA-19962

Four-event clock measurement exchange controller: have sync / wrong followup · case 02

While have_sync, event wrong_followup produces have_origin/record_origin_time instead of have_sync/reject_sequence.

Protocols◈ Members↗
FA-19963

Four-event clock measurement exchange controller: have sync / wrong followup · case 03

While have_sync, event wrong_followup produces have_origin/record_origin_time instead of have_sync/reject_sequence.

Protocols◈ Members↗
FA-19964

Four-event clock measurement exchange controller: have sync / wrong followup · case 04

While have_sync, event wrong_followup produces have_origin/record_origin_time instead of have_sync/reject_sequence.

Protocols◈ Members↗
FA-19965

Four-event clock measurement exchange controller: have sync / wrong followup · case 05

While have_sync, event wrong_followup produces have_origin/record_origin_time instead of have_sync/reject_sequence.

Protocols◈ Members↗
FA-19966

Four-event clock measurement exchange controller: awaiting delay / wrong response · case 01

While awaiting_delay, event wrong_response produces complete/compute_exchange instead of awaiting_delay/reject_sequence.

Protocols● Open access↗
FA-19967

Four-event clock measurement exchange controller: awaiting delay / wrong response · case 02

While awaiting_delay, event wrong_response produces complete/compute_exchange instead of awaiting_delay/reject_sequence.

Protocols◈ Members↗
FA-19968

Four-event clock measurement exchange controller: awaiting delay / wrong response · case 03

While awaiting_delay, event wrong_response produces complete/compute_exchange instead of awaiting_delay/reject_sequence.

Protocols◈ Members↗
FA-19969

Four-event clock measurement exchange controller: awaiting delay / wrong response · case 04

While awaiting_delay, event wrong_response produces complete/compute_exchange instead of awaiting_delay/reject_sequence.

Protocols◈ Members↗
FA-19970

Four-event clock measurement exchange controller: awaiting delay / wrong response · case 05

While awaiting_delay, event wrong_response produces complete/compute_exchange instead of awaiting_delay/reject_sequence.

Protocols◈ Members↗
FA-19971

Four-event clock measurement exchange controller: complete / consume · case 01

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

Protocols● Open access↗
FA-19972

Four-event clock measurement exchange controller: complete / consume · case 02

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

Protocols◈ Members↗
FA-19973

Four-event clock measurement exchange controller: complete / consume · case 03

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

Protocols◈ Members↗
FA-19974

Four-event clock measurement exchange controller: complete / consume · case 04

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

Protocols◈ Members↗
FA-19975

Four-event clock measurement exchange controller: complete / consume · case 05

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

Protocols◈ Members↗
FA-19976

Four-event clock measurement exchange controller: have origin / new sync · case 01

While have_origin, event new_sync produces have_origin/ignore instead of have_sync/restart_exchange.

Protocols● Open access↗
FA-19977

Four-event clock measurement exchange controller: have origin / new sync · case 02

While have_origin, event new_sync produces have_origin/ignore instead of have_sync/restart_exchange.

Protocols◈ Members↗
FA-19978

Four-event clock measurement exchange controller: have origin / new sync · case 03

While have_origin, event new_sync produces have_origin/ignore instead of have_sync/restart_exchange.

Protocols◈ Members↗
FA-19979

Four-event clock measurement exchange controller: have origin / new sync · case 04

While have_origin, event new_sync produces have_origin/ignore instead of have_sync/restart_exchange.

Protocols◈ Members↗
FA-19980

Four-event clock measurement exchange controller: have origin / new sync · case 05

While have_origin, event new_sync produces have_origin/ignore instead of have_sync/restart_exchange.

Protocols◈ Members↗
FA-19981

Four-event clock measurement exchange controller: idle / delay response · case 01

While idle, event delay_response produces complete/compute_exchange instead of idle/reject_orphan.

Protocols● Open access↗
FA-19982

Four-event clock measurement exchange controller: idle / delay response · case 02

While idle, event delay_response produces complete/compute_exchange instead of idle/reject_orphan.

Protocols◈ Members↗
FA-19983

Four-event clock measurement exchange controller: idle / delay response · case 03

While idle, event delay_response produces complete/compute_exchange instead of idle/reject_orphan.

Protocols◈ Members↗
FA-19984

Four-event clock measurement exchange controller: idle / delay response · case 04

While idle, event delay_response produces complete/compute_exchange instead of idle/reject_orphan.

Protocols◈ Members↗
FA-19985

Four-event clock measurement exchange controller: idle / delay response · case 05

While idle, event delay_response produces complete/compute_exchange instead of idle/reject_orphan.

Protocols◈ Members↗
FA-19986

Four-event clock measurement exchange controller: awaiting delay / exchange expired · case 01

While awaiting_delay, event exchange_expired produces complete/publish_offset instead of idle/discard_measurement.

Protocols● Open access↗
FA-19987

Four-event clock measurement exchange controller: awaiting delay / exchange expired · case 02

While awaiting_delay, event exchange_expired produces complete/publish_offset instead of idle/discard_measurement.

Protocols◈ Members↗
FA-19988

Four-event clock measurement exchange controller: awaiting delay / exchange expired · case 03

While awaiting_delay, event exchange_expired produces complete/publish_offset instead of idle/discard_measurement.

Protocols◈ Members↗
FA-19989

Four-event clock measurement exchange controller: awaiting delay / exchange expired · case 04

While awaiting_delay, event exchange_expired produces complete/publish_offset instead of idle/discard_measurement.

Protocols◈ Members↗
FA-19990

Four-event clock measurement exchange controller: awaiting delay / exchange expired · case 05

While awaiting_delay, event exchange_expired produces complete/publish_offset instead of idle/discard_measurement.

Protocols◈ Members↗
FA-19991

Half-duplex speaking-turn controller: listening / turn offer · case 01

While listening, event turn_offer produces speaking/send_payload instead of offered/ack_offer.

Protocols● Open access↗
FA-19992

Half-duplex speaking-turn controller: listening / turn offer · case 02

While listening, event turn_offer produces speaking/send_payload instead of offered/ack_offer.

Protocols◈ Members↗
FA-19993

Half-duplex speaking-turn controller: listening / turn offer · case 03

While listening, event turn_offer produces speaking/send_payload instead of offered/ack_offer.

Protocols◈ Members↗
FA-19994

Half-duplex speaking-turn controller: listening / turn offer · case 04

While listening, event turn_offer produces speaking/send_payload instead of offered/ack_offer.

Protocols◈ Members↗
FA-19995

Half-duplex speaking-turn controller: listening / turn offer · case 05

While listening, event turn_offer produces speaking/send_payload instead of offered/ack_offer.

Protocols◈ Members↗
FA-19996

Half-duplex speaking-turn controller: offered / turn commit · case 01

While offered, event turn_commit produces offered/wait instead of speaking/enable_transmit.

Protocols● Open access↗
FA-19997

Half-duplex speaking-turn controller: offered / turn commit · case 02

While offered, event turn_commit produces offered/wait instead of speaking/enable_transmit.

Protocols◈ Members↗
FA-19998

Half-duplex speaking-turn controller: offered / turn commit · case 03

While offered, event turn_commit produces offered/wait instead of speaking/enable_transmit.

Protocols◈ Members↗
FA-19999

Half-duplex speaking-turn controller: offered / turn commit · case 04

While offered, event turn_commit produces offered/wait instead of speaking/enable_transmit.

Protocols◈ Members↗
FA-20000

Half-duplex speaking-turn controller: offered / turn commit · case 05

While offered, event turn_commit produces offered/wait instead of speaking/enable_transmit.

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 ↗