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
Bounded keyboard queue with lossless release backpressure: Admitted key press is queued ahead of earlier strokes or with release phase · case 01
The event trace violates the queue press rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Admitted key press is queued ahead of earlier strokes or with release phase · case 02
The event trace violates the queue press rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Admitted key press is queued ahead of earlier strokes or with release phase · case 03
The event trace violates the queue press rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Admitted key press is queued ahead of earlier strokes or with release phase · case 04
The event trace violates the queue press rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Admitted key press is queued ahead of earlier strokes or with release phase · case 05
The event trace violates the queue press rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Release admission consults dispatched state instead of accepted-but-buffered physical presses · case 01
The event trace violates the release admission rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Release admission consults dispatched state instead of accepted-but-buffered physical presses · case 02
The event trace violates the release admission rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Release admission consults dispatched state instead of accepted-but-buffered physical presses · case 03
The event trace violates the release admission rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Release admission consults dispatched state instead of accepted-but-buffered physical presses · case 04
The event trace violates the release admission rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Release admission consults dispatched state instead of accepted-but-buffered physical presses · case 05
The event trace violates the release admission rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Release backpressure overruns the bounded queue or dispatches newest buffered input first · case 01
The event trace violates the release room rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Release backpressure overruns the bounded queue or dispatches newest buffered input first · case 02
The event trace violates the release room rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Release backpressure overruns the bounded queue or dispatches newest buffered input first · case 03
The event trace violates the release room rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Release backpressure overruns the bounded queue or dispatches newest buffered input first · case 04
The event trace violates the release room rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Release backpressure overruns the bounded queue or dispatches newest buffered input first · case 05
The event trace violates the release room rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Lossless release enqueue places up before its pending down or mislabels it as another press · case 01
The event trace violates the queued release rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Lossless release enqueue places up before its pending down or mislabels it as another press · case 02
The event trace violates the queued release rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Lossless release enqueue places up before its pending down or mislabels it as another press · case 03
The event trace violates the queued release rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Lossless release enqueue places up before its pending down or mislabels it as another press · case 04
The event trace violates the queued release rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Lossless release enqueue places up before its pending down or mislabels it as another press · case 05
The event trace violates the queued release rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Keyboard pump tick dispatches newest input or replays an entry without consuming it · case 01
The event trace violates the tick order rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Keyboard pump tick dispatches newest input or replays an entry without consuming it · case 02
The event trace violates the tick order rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Keyboard pump tick dispatches newest input or replays an entry without consuming it · case 03
The event trace violates the tick order rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Keyboard pump tick dispatches newest input or replays an entry without consuming it · case 04
The event trace violates the tick order rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Keyboard pump tick dispatches newest input or replays an entry without consuming it · case 05
The event trace violates the tick order rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Explicit keyboard queue flush reverses event ordering or drains only one edge · case 01
The event trace violates the flush order rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Explicit keyboard queue flush reverses event ordering or drains only one edge · case 02
The event trace violates the flush order rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Explicit keyboard queue flush reverses event ordering or drains only one edge · case 03
The event trace violates the flush order rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Explicit keyboard queue flush reverses event ordering or drains only one edge · case 04
The event trace violates the flush order rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Explicit keyboard queue flush reverses event ordering or drains only one edge · case 05
The event trace violates the flush order rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Keyboard reset clears only queue or accepted presses, permitting stale input ownership · case 01
The event trace violates the reset pending rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Keyboard reset clears only queue or accepted presses, permitting stale input ownership · case 02
The event trace violates the reset pending rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Keyboard reset clears only queue or accepted presses, permitting stale input ownership · case 03
The event trace violates the reset pending rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Keyboard reset clears only queue or accepted presses, permitting stale input ownership · case 04
The event trace violates the reset pending rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Keyboard reset clears only queue or accepted presses, permitting stale input ownership · case 05
The event trace violates the reset pending rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Keyboard reset releases the wrong ownership set or emits press events for held-key cleanup · case 01
The event trace violates the reset synth release rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Keyboard reset releases the wrong ownership set or emits press events for held-key cleanup · case 02
The event trace violates the reset synth release rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Keyboard reset releases the wrong ownership set or emits press events for held-key cleanup · case 03
The event trace violates the reset synth release rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Keyboard reset releases the wrong ownership set or emits press events for held-key cleanup · case 04
The event trace violates the reset synth release rule and produces incorrect keyboard state or command output.
Bounded keyboard queue with lossless release backpressure: Keyboard reset releases the wrong ownership set or emits press events for held-key cleanup · case 05
The event trace violates the reset synth release rule and produces incorrect keyboard state or command output.
Menu IDs containing separators alias other commands · case 01
Menu IDs containing separators alias other commands.
Menu IDs containing separators alias other commands · case 02
Menu IDs containing separators alias other commands.
Menu IDs containing separators alias other commands · case 03
Menu IDs containing separators alias other commands.
Menu IDs containing separators alias other commands · case 04
Menu IDs containing separators alias other commands.
Menu IDs containing separators alias other commands · case 05
Menu IDs containing separators alias other commands.
Deep menu command remains addressable through an unavailable ancestor · case 01
Deep menu command remains addressable through an unavailable ancestor.
Deep menu command remains addressable through an unavailable ancestor · case 02
Deep menu command remains addressable through an unavailable ancestor.
Deep menu command remains addressable through an unavailable ancestor · case 03
Deep menu command remains addressable through an unavailable ancestor.
Deep menu command remains addressable through an unavailable ancestor · case 04
Deep menu command remains addressable through an unavailable ancestor.
Deep menu command remains addressable through an unavailable ancestor · case 05
Deep menu command remains addressable through an unavailable ancestor.
Containing menu address drops the root instead of leaf · case 01
Containing menu address drops the root instead of leaf.
Containing menu address drops the root instead of leaf · case 02
Containing menu address drops the root instead of leaf.
Containing menu address drops the root instead of leaf · case 03
Containing menu address drops the root instead of leaf.
Containing menu address drops the root instead of leaf · case 04
Containing menu address drops the root instead of leaf.
Containing menu address drops the root instead of leaf · case 05
Containing menu address drops the root instead of leaf.
Sibling commands are mistaken for submenu descendants · case 01
Sibling commands are mistaken for submenu descendants.
Sibling commands are mistaken for submenu descendants · case 02
Sibling commands are mistaken for submenu descendants.
Sibling commands are mistaken for submenu descendants · case 03
Sibling commands are mistaken for submenu descendants.
Sibling commands are mistaken for submenu descendants · case 04
Sibling commands are mistaken for submenu descendants.
Sibling commands are mistaken for submenu descendants · case 05
Sibling commands are mistaken for submenu descendants.
Repeated local IDs route to the wrong menu branch · case 01
Repeated local IDs route to the wrong menu branch.
Repeated local IDs route to the wrong menu branch · case 02
Repeated local IDs route to the wrong menu branch.
Repeated local IDs route to the wrong menu branch · case 03
Repeated local IDs route to the wrong menu branch.
Repeated local IDs route to the wrong menu branch · case 04
Repeated local IDs route to the wrong menu branch.
Repeated local IDs route to the wrong menu branch · case 05
Repeated local IDs route to the wrong menu branch.
Relocating a menu namespace duplicates its old root · case 01
Relocating a menu namespace duplicates its old root.
Relocating a menu namespace duplicates its old root · case 02
Relocating a menu namespace duplicates its old root.
Relocating a menu namespace duplicates its old root · case 03
Relocating a menu namespace duplicates its old root.
Relocating a menu namespace duplicates its old root · case 04
Relocating a menu namespace duplicates its old root.
Relocating a menu namespace duplicates its old root · case 05
Relocating a menu namespace duplicates its old root.
Replacing a submenu retains a stale descendant cascade · case 01
Replacing a submenu retains a stale descendant cascade.
Replacing a submenu retains a stale descendant cascade · case 02
Replacing a submenu retains a stale descendant cascade.
Replacing a submenu retains a stale descendant cascade · case 03
Replacing a submenu retains a stale descendant cascade.
Replacing a submenu retains a stale descendant cascade · case 04
Replacing a submenu retains a stale descendant cascade.
Replacing a submenu retains a stale descendant cascade · case 05
Replacing a submenu retains a stale descendant cascade.
Closing a submenu destroys its owning menu · case 01
Closing a submenu destroys its owning menu.
Closing a submenu destroys its owning menu · case 02
Closing a submenu destroys its owning menu.
Closing a submenu destroys its owning menu · case 03
Closing a submenu destroys its owning menu.
Closing a submenu destroys its owning menu · case 04
Closing a submenu destroys its owning menu.
Closing a submenu destroys its owning menu · case 05
Closing a submenu destroys its owning menu.
Removing a menu owner leaves orphaned grandchildren · case 01
Removing a menu owner leaves orphaned grandchildren.
Removing a menu owner leaves orphaned grandchildren · case 02
Removing a menu owner leaves orphaned grandchildren.
Removing a menu owner leaves orphaned grandchildren · case 03
Removing a menu owner leaves orphaned grandchildren.
Removing a menu owner leaves orphaned grandchildren · case 04
Removing a menu owner leaves orphaned grandchildren.
Removing a menu owner leaves orphaned grandchildren · case 05
Removing a menu owner leaves orphaned grandchildren.
Reentering an existing submenu destroys deeper open state · case 01
Reentering an existing submenu destroys deeper open state.
Reentering an existing submenu destroys deeper open state · case 02
Reentering an existing submenu destroys deeper open state.
Reentering an existing submenu destroys deeper open state · case 03
Reentering an existing submenu destroys deeper open state.
Reentering an existing submenu destroys deeper open state · case 04
Reentering an existing submenu destroys deeper open state.
Reentering an existing submenu destroys deeper open state · case 05
Reentering an existing submenu destroys deeper open state.
A submenu subscribes to the wrong ancestor lifetime · case 01
A submenu subscribes to the wrong ancestor lifetime.
A submenu subscribes to the wrong ancestor lifetime · case 02
A submenu subscribes to the wrong ancestor lifetime.
A submenu subscribes to the wrong ancestor lifetime · case 03
A submenu subscribes to the wrong ancestor lifetime.
A submenu subscribes to the wrong ancestor lifetime · case 04
A submenu subscribes to the wrong ancestor lifetime.
A submenu subscribes to the wrong ancestor lifetime · case 05
A submenu subscribes to the wrong ancestor lifetime.
Menu owner depth is inferred from cascade length · case 01
Menu owner depth is inferred from cascade length.
Menu owner depth is inferred from cascade length · case 02
Menu owner depth is inferred from cascade length.
Menu owner depth is inferred from cascade length · case 03
Menu owner depth is inferred from cascade length.
Menu owner depth is inferred from cascade length · case 04
Menu owner depth is inferred from cascade length.
Menu owner depth is inferred from cascade length · case 05
Menu owner depth is inferred from cascade length.
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 ↗