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

Release-completed dot chord keyboard: A dot repeat toggles physical held state or drops other still-held dots · case 01

The event trace violates the held dot rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-31902

Release-completed dot chord keyboard: A dot repeat toggles physical held state or drops other still-held dots · case 02

The event trace violates the held dot rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31903

Release-completed dot chord keyboard: A dot repeat toggles physical held state or drops other still-held dots · case 03

The event trace violates the held dot rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31904

Release-completed dot chord keyboard: A dot repeat toggles physical held state or drops other still-held dots · case 04

The event trace violates the held dot rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31905

Release-completed dot chord keyboard: A dot repeat toggles physical held state or drops other still-held dots · case 05

The event trace violates the held dot rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31906

Release-completed dot chord keyboard: Rolling dot chord forgets earlier dots or removes a repeated dot · case 01

The event trace violates the accumulate dot rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-31907

Release-completed dot chord keyboard: Rolling dot chord forgets earlier dots or removes a repeated dot · case 02

The event trace violates the accumulate dot rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31908

Release-completed dot chord keyboard: Rolling dot chord forgets earlier dots or removes a repeated dot · case 03

The event trace violates the accumulate dot rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31909

Release-completed dot chord keyboard: Rolling dot chord forgets earlier dots or removes a repeated dot · case 04

The event trace violates the accumulate dot rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31910

Release-completed dot chord keyboard: Rolling dot chord forgets earlier dots or removes a repeated dot · case 05

The event trace violates the accumulate dot rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31911

Release-completed dot chord keyboard: An unmatched dot release is treated as a chord release transition · case 01

The event trace violates the release membership rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-31912

Release-completed dot chord keyboard: An unmatched dot release is treated as a chord release transition · case 02

The event trace violates the release membership rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31913

Release-completed dot chord keyboard: An unmatched dot release is treated as a chord release transition · case 03

The event trace violates the release membership rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31914

Release-completed dot chord keyboard: An unmatched dot release is treated as a chord release transition · case 04

The event trace violates the release membership rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31915

Release-completed dot chord keyboard: An unmatched dot release is treated as a chord release transition · case 05

The event trace violates the release membership rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31916

Release-completed dot chord keyboard: Releasing one dot clears other physical chord members · case 01

The event trace violates the release dot rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-31917

Release-completed dot chord keyboard: Releasing one dot clears other physical chord members · case 02

The event trace violates the release dot rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31918

Release-completed dot chord keyboard: Releasing one dot clears other physical chord members · case 03

The event trace violates the release dot rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31919

Release-completed dot chord keyboard: Releasing one dot clears other physical chord members · case 04

The event trace violates the release dot rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31920

Release-completed dot chord keyboard: Releasing one dot clears other physical chord members · case 05

The event trace violates the release dot rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31921

Release-completed dot chord keyboard: Dot chord commits before all participating keys have been released · case 01

The event trace violates the commit final rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-31922

Release-completed dot chord keyboard: Dot chord commits before all participating keys have been released · case 02

The event trace violates the commit final rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31923

Release-completed dot chord keyboard: Dot chord commits before all participating keys have been released · case 03

The event trace violates the commit final rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31924

Release-completed dot chord keyboard: Dot chord commits before all participating keys have been released · case 04

The event trace violates the commit final rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31925

Release-completed dot chord keyboard: Dot chord commits before all participating keys have been released · case 05

The event trace violates the commit final rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31926

Release-completed dot chord keyboard: Committed dot pattern uses remaining held dots or noncanonical dot order · case 01

The event trace violates the commit content rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-31927

Release-completed dot chord keyboard: Committed dot pattern uses remaining held dots or noncanonical dot order · case 02

The event trace violates the commit content rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31928

Release-completed dot chord keyboard: Committed dot pattern uses remaining held dots or noncanonical dot order · case 03

The event trace violates the commit content rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31929

Release-completed dot chord keyboard: Committed dot pattern uses remaining held dots or noncanonical dot order · case 04

The event trace violates the commit content rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31930

Release-completed dot chord keyboard: Committed dot pattern uses remaining held dots or noncanonical dot order · case 05

The event trace violates the commit content rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31931

Release-completed dot chord keyboard: A completed dot chord leaks dot membership into the next chord · case 01

The event trace violates the clear committed rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-31932

Release-completed dot chord keyboard: A completed dot chord leaks dot membership into the next chord · case 02

The event trace violates the clear committed rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31933

Release-completed dot chord keyboard: A completed dot chord leaks dot membership into the next chord · case 03

The event trace violates the clear committed rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31934

Release-completed dot chord keyboard: A completed dot chord leaks dot membership into the next chord · case 04

The event trace violates the clear committed rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31935

Release-completed dot chord keyboard: A completed dot chord leaks dot membership into the next chord · case 05

The event trace violates the clear committed rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31936

Release-completed dot chord keyboard: Separator is represented as a padding dot or omitted instead of an explicit empty chord · case 01

The event trace violates the separator empty rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-31937

Release-completed dot chord keyboard: Separator is represented as a padding dot or omitted instead of an explicit empty chord · case 02

The event trace violates the separator empty rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31938

Release-completed dot chord keyboard: Separator is represented as a padding dot or omitted instead of an explicit empty chord · case 03

The event trace violates the separator empty rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31939

Release-completed dot chord keyboard: Separator is represented as a padding dot or omitted instead of an explicit empty chord · case 04

The event trace violates the separator empty rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31940

Release-completed dot chord keyboard: Separator is represented as a padding dot or omitted instead of an explicit empty chord · case 05

The event trace violates the separator empty rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31941

Multi-tap keyboard character commit timing: A press at the keypad commit deadline cycles the expired character or uses absolute time · case 01

The event trace violates the press expiry rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-31942

Multi-tap keyboard character commit timing: A press at the keypad commit deadline cycles the expired character or uses absolute time · case 02

The event trace violates the press expiry rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31943

Multi-tap keyboard character commit timing: A press at the keypad commit deadline cycles the expired character or uses absolute time · case 03

The event trace violates the press expiry rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31944

Multi-tap keyboard character commit timing: A press at the keypad commit deadline cycles the expired character or uses absolute time · case 04

The event trace violates the press expiry rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31945

Multi-tap keyboard character commit timing: A press at the keypad commit deadline cycles the expired character or uses absolute time · case 05

The event trace violates the press expiry rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31946

Multi-tap keyboard character commit timing: Changing keypad key cycles an unrelated pending character · case 01

The event trace violates the same key cycle rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-31947

Multi-tap keyboard character commit timing: Changing keypad key cycles an unrelated pending character · case 02

The event trace violates the same key cycle rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31948

Multi-tap keyboard character commit timing: Changing keypad key cycles an unrelated pending character · case 03

The event trace violates the same key cycle rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31949

Multi-tap keyboard character commit timing: Changing keypad key cycles an unrelated pending character · case 04

The event trace violates the same key cycle rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31950

Multi-tap keyboard character commit timing: Changing keypad key cycles an unrelated pending character · case 05

The event trace violates the same key cycle rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31951

Multi-tap keyboard character commit timing: Multi-tap character cycling saturates or moves backward instead of wrapping · case 01

The event trace violates the cycle wrap rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-31952

Multi-tap keyboard character commit timing: Multi-tap character cycling saturates or moves backward instead of wrapping · case 02

The event trace violates the cycle wrap rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31953

Multi-tap keyboard character commit timing: Multi-tap character cycling saturates or moves backward instead of wrapping · case 03

The event trace violates the cycle wrap rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31954

Multi-tap keyboard character commit timing: Multi-tap character cycling saturates or moves backward instead of wrapping · case 04

The event trace violates the cycle wrap rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31955

Multi-tap keyboard character commit timing: Multi-tap character cycling saturates or moves backward instead of wrapping · case 05

The event trace violates the cycle wrap rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31956

Multi-tap keyboard character commit timing: Repeated tap extends the timeout from an old deadline or expires immediately · case 01

The event trace violates the cycle deadline rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-31957

Multi-tap keyboard character commit timing: Repeated tap extends the timeout from an old deadline or expires immediately · case 02

The event trace violates the cycle deadline rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31958

Multi-tap keyboard character commit timing: Repeated tap extends the timeout from an old deadline or expires immediately · case 03

The event trace violates the cycle deadline rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31959

Multi-tap keyboard character commit timing: Repeated tap extends the timeout from an old deadline or expires immediately · case 04

The event trace violates the cycle deadline rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31960

Multi-tap keyboard character commit timing: Repeated tap extends the timeout from an old deadline or expires immediately · case 05

The event trace violates the cycle deadline rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31961

Multi-tap keyboard character commit timing: Changing keypad key commits the new key character or loses the old pending one · case 01

The event trace violates the switch commit rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-31962

Multi-tap keyboard character commit timing: Changing keypad key commits the new key character or loses the old pending one · case 02

The event trace violates the switch commit rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31963

Multi-tap keyboard character commit timing: Changing keypad key commits the new key character or loses the old pending one · case 03

The event trace violates the switch commit rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31964

Multi-tap keyboard character commit timing: Changing keypad key commits the new key character or loses the old pending one · case 04

The event trace violates the switch commit rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31965

Multi-tap keyboard character commit timing: Changing keypad key commits the new key character or loses the old pending one · case 05

The event trace violates the switch commit rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31966

Multi-tap keyboard character commit timing: A newly selected keypad key starts on its last character or an absolute deadline · case 01

The event trace violates the new character rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-31967

Multi-tap keyboard character commit timing: A newly selected keypad key starts on its last character or an absolute deadline · case 02

The event trace violates the new character rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31968

Multi-tap keyboard character commit timing: A newly selected keypad key starts on its last character or an absolute deadline · case 03

The event trace violates the new character rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31969

Multi-tap keyboard character commit timing: A newly selected keypad key starts on its last character or an absolute deadline · case 04

The event trace violates the new character rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31970

Multi-tap keyboard character commit timing: A newly selected keypad key starts on its last character or an absolute deadline · case 05

The event trace violates the new character rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31971

Multi-tap keyboard character commit timing: Timer commits early or fails to commit a character at its deadline · case 01

The event trace violates the tick expiry rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-31972

Multi-tap keyboard character commit timing: Timer commits early or fails to commit a character at its deadline · case 02

The event trace violates the tick expiry rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31973

Multi-tap keyboard character commit timing: Timer commits early or fails to commit a character at its deadline · case 03

The event trace violates the tick expiry rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31974

Multi-tap keyboard character commit timing: Timer commits early or fails to commit a character at its deadline · case 04

The event trace violates the tick expiry rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31975

Multi-tap keyboard character commit timing: Timer commits early or fails to commit a character at its deadline · case 05

The event trace violates the tick expiry rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31976

Multi-tap keyboard character commit timing: Backspace with a pending character deletes committed text · case 01

The event trace violates the pending backspace rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-31977

Multi-tap keyboard character commit timing: Backspace with a pending character deletes committed text · case 02

The event trace violates the pending backspace rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31978

Multi-tap keyboard character commit timing: Backspace with a pending character deletes committed text · case 03

The event trace violates the pending backspace rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31979

Multi-tap keyboard character commit timing: Backspace with a pending character deletes committed text · case 04

The event trace violates the pending backspace rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31980

Multi-tap keyboard character commit timing: Backspace with a pending character deletes committed text · case 05

The event trace violates the pending backspace rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31981

Multi-tap keyboard character commit timing: Backspace removes the first character or clears the whole committed buffer · case 01

The event trace violates the committed backspace rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-31982

Multi-tap keyboard character commit timing: Backspace removes the first character or clears the whole committed buffer · case 02

The event trace violates the committed backspace rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31983

Multi-tap keyboard character commit timing: Backspace removes the first character or clears the whole committed buffer · case 03

The event trace violates the committed backspace rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31984

Multi-tap keyboard character commit timing: Backspace removes the first character or clears the whole committed buffer · case 04

The event trace violates the committed backspace rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31985

Multi-tap keyboard character commit timing: Backspace removes the first character or clears the whole committed buffer · case 05

The event trace violates the committed backspace rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31986

Multi-tap keyboard character commit timing: Space fails to close pending character state or erases previous text · case 01

The event trace violates the space close rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-31987

Multi-tap keyboard character commit timing: Space fails to close pending character state or erases previous text · case 02

The event trace violates the space close rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31988

Multi-tap keyboard character commit timing: Space fails to close pending character state or erases previous text · case 03

The event trace violates the space close rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31989

Multi-tap keyboard character commit timing: Space fails to close pending character state or erases previous text · case 04

The event trace violates the space close rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31990

Multi-tap keyboard character commit timing: Space fails to close pending character state or erases previous text · case 05

The event trace violates the space close rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31991

Keyboard numeric character entry transaction: Starting numeric entry preserves stale digits or discards hexadecimal mode · case 01

The event trace violates the begin reset rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-31992

Keyboard numeric character entry transaction: Starting numeric entry preserves stale digits or discards hexadecimal mode · case 02

The event trace violates the begin reset rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31993

Keyboard numeric character entry transaction: Starting numeric entry preserves stale digits or discards hexadecimal mode · case 03

The event trace violates the begin reset rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31994

Keyboard numeric character entry transaction: Starting numeric entry preserves stale digits or discards hexadecimal mode · case 04

The event trace violates the begin reset rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31995

Keyboard numeric character entry transaction: Starting numeric entry preserves stale digits or discards hexadecimal mode · case 05

The event trace violates the begin reset rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31996

Keyboard numeric character entry transaction: Hexadecimal digit admission loses the final digit or normalized letters · case 01

The event trace violates the digit alphabet rule and produces incorrect keyboard state or command output.

Keyboard interactions● Open access↗
FA-31997

Keyboard numeric character entry transaction: Hexadecimal digit admission loses the final digit or normalized letters · case 02

The event trace violates the digit alphabet rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31998

Keyboard numeric character entry transaction: Hexadecimal digit admission loses the final digit or normalized letters · case 03

The event trace violates the digit alphabet rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-31999

Keyboard numeric character entry transaction: Hexadecimal digit admission loses the final digit or normalized letters · case 04

The event trace violates the digit alphabet rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ Members↗
FA-32000

Keyboard numeric character entry transaction: Hexadecimal digit admission loses the final digit or normalized letters · case 05

The event trace violates the digit alphabet rule and produces incorrect keyboard state or command output.

Keyboard interactions◈ 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 ↗