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 ↗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
Keyboard default edit cancellation pipeline: A named editing key is inserted as text or printable input disappears · case 01
The event trace violates the insertion kind rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: A named editing key is inserted as text or printable input disappears · case 02
The event trace violates the insertion kind rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: A named editing key is inserted as text or printable input disappears · case 03
The event trace violates the insertion kind rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: A named editing key is inserted as text or printable input disappears · case 04
The event trace violates the insertion kind rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: A named editing key is inserted as text or printable input disappears · case 05
The event trace violates the insertion kind rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Backspace expands an already selected range or removes two code points · case 01
The event trace violates the backspace selection rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Backspace expands an already selected range or removes two code points · case 02
The event trace violates the backspace selection rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Backspace expands an already selected range or removes two code points · case 03
The event trace violates the backspace selection rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Backspace expands an already selected range or removes two code points · case 04
The event trace violates the backspace selection rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Backspace expands an already selected range or removes two code points · case 05
The event trace violates the backspace selection rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Forward delete extends an existing selection or consumes two characters · case 01
The event trace violates the delete selection rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Forward delete extends an existing selection or consumes two characters · case 02
The event trace violates the delete selection rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Forward delete extends an existing selection or consumes two characters · case 03
The event trace violates the delete selection rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Forward delete extends an existing selection or consumes two characters · case 04
The event trace violates the delete selection rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Forward delete extends an existing selection or consumes two characters · case 05
The event trace violates the delete selection rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: The keyboard default action emits the wrong pre-mutation notification or dispatches it before keydown · case 01
The event trace violates the beforeinput order rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: The keyboard default action emits the wrong pre-mutation notification or dispatches it before keydown · case 02
The event trace violates the beforeinput order rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: The keyboard default action emits the wrong pre-mutation notification or dispatches it before keydown · case 03
The event trace violates the beforeinput order rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: The keyboard default action emits the wrong pre-mutation notification or dispatches it before keydown · case 04
The event trace violates the beforeinput order rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: The keyboard default action emits the wrong pre-mutation notification or dispatches it before keydown · case 05
The event trace violates the beforeinput order rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Boundary deletion dispatches a mutation event or empty result is mistaken for no change · case 01
The event trace violates the no op events rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Boundary deletion dispatches a mutation event or empty result is mistaken for no change · case 02
The event trace violates the no op events rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Boundary deletion dispatches a mutation event or empty result is mistaken for no change · case 03
The event trace violates the no op events rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Boundary deletion dispatches a mutation event or empty result is mistaken for no change · case 04
The event trace violates the no op events rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Boundary deletion dispatches a mutation event or empty result is mistaken for no change · case 05
The event trace violates the no op events rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Beforeinput cancellation incorrectly depends on the earlier keydown state · case 01
The event trace violates the beforeinput cancel rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Beforeinput cancellation incorrectly depends on the earlier keydown state · case 02
The event trace violates the beforeinput cancel rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Beforeinput cancellation incorrectly depends on the earlier keydown state · case 03
The event trace violates the beforeinput cancel rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Beforeinput cancellation incorrectly depends on the earlier keydown state · case 04
The event trace violates the beforeinput cancel rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Beforeinput cancellation incorrectly depends on the earlier keydown state · case 05
The event trace violates the beforeinput cancel rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Successful keyboard mutation loses the release notification or places it before the press phase · case 01
The event trace violates the keyup completion rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Successful keyboard mutation loses the release notification or places it before the press phase · case 02
The event trace violates the keyup completion rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Successful keyboard mutation loses the release notification or places it before the press phase · case 03
The event trace violates the keyup completion rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Successful keyboard mutation loses the release notification or places it before the press phase · case 04
The event trace violates the keyup completion rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Successful keyboard mutation loses the release notification or places it before the press phase · case 05
The event trace violates the keyup completion rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: A completed keyboard default edit publishes the wrong mutation event · case 01
The event trace violates the input notification rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: A completed keyboard default edit publishes the wrong mutation event · case 02
The event trace violates the input notification rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: A completed keyboard default edit publishes the wrong mutation event · case 03
The event trace violates the input notification rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: A completed keyboard default edit publishes the wrong mutation event · case 04
The event trace violates the input notification rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: A completed keyboard default edit publishes the wrong mutation event · case 05
The event trace violates the input notification rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Cancelling a key sequence leaves either its prefix or timeout origin live · case 01
The event trace violates the cancel clock rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Cancelling a key sequence leaves either its prefix or timeout origin live · case 02
The event trace violates the cancel clock rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Cancelling a key sequence leaves either its prefix or timeout origin live · case 03
The event trace violates the cancel clock rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Cancelling a key sequence leaves either its prefix or timeout origin live · case 04
The event trace violates the cancel clock rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Cancelling a key sequence leaves either its prefix or timeout origin live · case 05
The event trace violates the cancel clock rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: A timer expires a valid exact-boundary sequence or uses absolute time · case 01
The event trace violates the tick expiry rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: A timer expires a valid exact-boundary sequence or uses absolute time · case 02
The event trace violates the tick expiry rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: A timer expires a valid exact-boundary sequence or uses absolute time · case 03
The event trace violates the tick expiry rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: A timer expires a valid exact-boundary sequence or uses absolute time · case 04
The event trace violates the tick expiry rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: A timer expires a valid exact-boundary sequence or uses absolute time · case 05
The event trace violates the tick expiry rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Repeat or release events advance the logical key sequence · case 01
The event trace violates the repeat feed rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Repeat or release events advance the logical key sequence · case 02
The event trace violates the repeat feed rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Repeat or release events advance the logical key sequence · case 03
The event trace violates the repeat feed rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Repeat or release events advance the logical key sequence · case 04
The event trace violates the repeat feed rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Repeat or release events advance the logical key sequence · case 05
The event trace violates the repeat feed rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: An arriving key expires a prefix at the wrong timeout boundary · case 01
The event trace violates the input expiry rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: An arriving key expires a prefix at the wrong timeout boundary · case 02
The event trace violates the input expiry rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: An arriving key expires a prefix at the wrong timeout boundary · case 03
The event trace violates the input expiry rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: An arriving key expires a prefix at the wrong timeout boundary · case 04
The event trace violates the input expiry rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: An arriving key expires a prefix at the wrong timeout boundary · case 05
The event trace violates the input expiry rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: The newest physical key is prepended or replaces the current matched prefix · case 01
The event trace violates the candidate append rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: The newest physical key is prepended or replaces the current matched prefix · case 02
The event trace violates the candidate append rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: The newest physical key is prepended or replaces the current matched prefix · case 03
The event trace violates the candidate append rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: The newest physical key is prepended or replaces the current matched prefix · case 04
The event trace violates the candidate append rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: The newest physical key is prepended or replaces the current matched prefix · case 05
The event trace violates the candidate append rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Accepted key events fail to refresh the inter-key timeout origin · case 01
The event trace violates the accepted clock rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Accepted key events fail to refresh the inter-key timeout origin · case 02
The event trace violates the accepted clock rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Accepted key events fail to refresh the inter-key timeout origin · case 03
The event trace violates the accepted clock rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Accepted key events fail to refresh the inter-key timeout origin · case 04
The event trace violates the accepted clock rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Accepted key events fail to refresh the inter-key timeout origin · case 05
The event trace violates the accepted clock rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Prefix search selects a shorter suffix or excludes the full candidate · case 01
The event trace violates the prefix search rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Prefix search selects a shorter suffix or excludes the full candidate · case 02
The event trace violates the prefix search rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Prefix search selects a shorter suffix or excludes the full candidate · case 03
The event trace violates the prefix search rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Prefix search selects a shorter suffix or excludes the full candidate · case 04
The event trace violates the prefix search rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Prefix search selects a shorter suffix or excludes the full candidate · case 05
The event trace violates the prefix search rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Sequence recovery compares the wrong end of the candidate or configured sequence · case 01
The event trace violates the suffix comparison rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Sequence recovery compares the wrong end of the candidate or configured sequence · case 02
The event trace violates the suffix comparison rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Sequence recovery compares the wrong end of the candidate or configured sequence · case 03
The event trace violates the suffix comparison rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Sequence recovery compares the wrong end of the candidate or configured sequence · case 04
The event trace violates the suffix comparison rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Sequence recovery compares the wrong end of the candidate or configured sequence · case 05
The event trace violates the suffix comparison rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: A completed key sequence reports a synthetic timestamp instead of the triggering event time · case 01
The event trace violates the match clock rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: A completed key sequence reports a synthetic timestamp instead of the triggering event time · case 02
The event trace violates the match clock rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: A completed key sequence reports a synthetic timestamp instead of the triggering event time · case 03
The event trace violates the match clock rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: A completed key sequence reports a synthetic timestamp instead of the triggering event time · case 04
The event trace violates the match clock rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: A completed key sequence reports a synthetic timestamp instead of the triggering event time · case 05
The event trace violates the match clock rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Sequence completion loses a multi-key overlapping prefix for the next match · case 01
The event trace violates the overlap retention rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Sequence completion loses a multi-key overlapping prefix for the next match · case 02
The event trace violates the overlap retention rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Sequence completion loses a multi-key overlapping prefix for the next match · case 03
The event trace violates the overlap retention rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Sequence completion loses a multi-key overlapping prefix for the next match · case 04
The event trace violates the overlap retention rule and produces incorrect keyboard state or command output.
Overlapping keyboard sequence matcher: Sequence completion loses a multi-key overlapping prefix for the next match · case 05
The event trace violates the overlap retention rule and produces incorrect keyboard state or command output.
Explicit dead-key text composition: A second dead key discards or replaces the pending literal accent · case 01
The event trace violates the successive dead rule and produces incorrect keyboard state or command output.
Explicit dead-key text composition: A second dead key discards or replaces the pending literal accent · case 02
The event trace violates the successive dead rule and produces incorrect keyboard state or command output.
Explicit dead-key text composition: A second dead key discards or replaces the pending literal accent · case 03
The event trace violates the successive dead rule and produces incorrect keyboard state or command output.
Explicit dead-key text composition: A second dead key discards or replaces the pending literal accent · case 04
The event trace violates the successive dead rule and produces incorrect keyboard state or command output.
Explicit dead-key text composition: A second dead key discards or replaces the pending literal accent · case 05
The event trace violates the successive dead rule and produces incorrect keyboard state or command output.
Explicit dead-key text composition: Dead key activation fails to replace the pending accent · case 01
The event trace violates the pending accent rule and produces incorrect keyboard state or command output.
Explicit dead-key text composition: Dead key activation fails to replace the pending accent · case 02
The event trace violates the pending accent rule and produces incorrect keyboard state or command output.
Explicit dead-key text composition: Dead key activation fails to replace the pending accent · case 03
The event trace violates the pending accent rule and produces incorrect keyboard state or command output.
Explicit dead-key text composition: Dead key activation fails to replace the pending accent · case 04
The event trace violates the pending accent rule and produces incorrect keyboard state or command output.
Explicit dead-key text composition: Dead key activation fails to replace the pending accent · case 05
The event trace violates the pending accent rule and produces incorrect keyboard state or command output.
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 ↗