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
Layered physical keyboard remapping: Layer release pops the latest layer instead of the named one · case 01
The event trace violates the named pop rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Layer release pops the latest layer instead of the named one · case 02
The event trace violates the named pop rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Layer release pops the latest layer instead of the named one · case 03
The event trace violates the named pop rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Layer release pops the latest layer instead of the named one · case 04
The event trace violates the named pop rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Layer release pops the latest layer instead of the named one · case 05
The event trace violates the named pop rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Global layer reset retains active remapping context · case 01
The event trace violates the clear stack rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Global layer reset retains active remapping context · case 02
The event trace violates the clear stack rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Global layer reset retains active remapping context · case 03
The event trace violates the clear stack rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Global layer reset retains active remapping context · case 04
The event trace violates the clear stack rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Global layer reset retains active remapping context · case 05
The event trace violates the clear stack rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: An unmapped key loses its original identity in transparent layers · case 01
The event trace violates the fallback key rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: An unmapped key loses its original identity in transparent layers · case 02
The event trace violates the fallback key rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: An unmapped key loses its original identity in transparent layers · case 03
The event trace violates the fallback key rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: An unmapped key loses its original identity in transparent layers · case 04
The event trace violates the fallback key rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: An unmapped key loses its original identity in transparent layers · case 05
The event trace violates the fallback key rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Oldest active layer overrides the newest remap layer · case 01
The event trace violates the layer precedence rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Oldest active layer overrides the newest remap layer · case 02
The event trace violates the layer precedence rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Oldest active layer overrides the newest remap layer · case 03
The event trace violates the layer precedence rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Oldest active layer overrides the newest remap layer · case 04
The event trace violates the layer precedence rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Oldest active layer overrides the newest remap layer · case 05
The event trace violates the layer precedence rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Falsy defined remaps are confused with transparent missing entries · case 01
The event trace violates the defined entry rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Falsy defined remaps are confused with transparent missing entries · case 02
The event trace violates the defined entry rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Falsy defined remaps are confused with transparent missing entries · case 03
The event trace violates the defined entry rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Falsy defined remaps are confused with transparent missing entries · case 04
The event trace violates the defined entry rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Falsy defined remaps are confused with transparent missing entries · case 05
The event trace violates the defined entry rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Resolution continues into lower layers after finding an explicit mapping · case 01
The event trace violates the stop resolution rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Resolution continues into lower layers after finding an explicit mapping · case 02
The event trace violates the stop resolution rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Resolution continues into lower layers after finding an explicit mapping · case 03
The event trace violates the stop resolution rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Resolution continues into lower layers after finding an explicit mapping · case 04
The event trace violates the stop resolution rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Resolution continues into lower layers after finding an explicit mapping · case 05
The event trace violates the stop resolution rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Empty output and blocked output have their meanings conflated · case 01
The event trace violates the blocked output rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Empty output and blocked output have their meanings conflated · case 02
The event trace violates the blocked output rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Empty output and blocked output have their meanings conflated · case 03
The event trace violates the blocked output rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Empty output and blocked output have their meanings conflated · case 04
The event trace violates the blocked output rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Empty output and blocked output have their meanings conflated · case 05
The event trace violates the blocked output rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: A remapped key emits its physical name or wraps its output in a different shape · case 01
The event trace violates the emitted value rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: A remapped key emits its physical name or wraps its output in a different shape · case 02
The event trace violates the emitted value rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: A remapped key emits its physical name or wraps its output in a different shape · case 03
The event trace violates the emitted value rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: A remapped key emits its physical name or wraps its output in a different shape · case 04
The event trace violates the emitted value rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: A remapped key emits its physical name or wraps its output in a different shape · case 05
The event trace violates the emitted value rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Sticky modifier taps never reach locked or never unlock · case 01
The event trace violates the latch cycle rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Sticky modifier taps never reach locked or never unlock · case 02
The event trace violates the latch cycle rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Sticky modifier taps never reach locked or never unlock · case 03
The event trace violates the latch cycle rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Sticky modifier taps never reach locked or never unlock · case 04
The event trace violates the latch cycle rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Sticky modifier taps never reach locked or never unlock · case 05
The event trace violates the latch cycle rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: A latch transition writes to a shared key or retains the previous state · case 01
The event trace violates the latch key rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: A latch transition writes to a shared key or retains the previous state · case 02
The event trace violates the latch key rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: A latch transition writes to a shared key or retains the previous state · case 03
The event trace violates the latch key rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: A latch transition writes to a shared key or retains the previous state · case 04
The event trace violates the latch key rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: A latch transition writes to a shared key or retains the previous state · case 05
The event trace violates the latch key rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Unlocking one modifier erases unrelated latches or retains a false entry · case 01
The event trace violates the unlock removal rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Unlocking one modifier erases unrelated latches or retains a false entry · case 02
The event trace violates the unlock removal rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Unlocking one modifier erases unrelated latches or retains a false entry · case 03
The event trace violates the unlock removal rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Unlocking one modifier erases unrelated latches or retains a false entry · case 04
The event trace violates the unlock removal rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Unlocking one modifier erases unrelated latches or retains a false entry · case 05
The event trace violates the unlock removal rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Physical modifier down replaces other keys or toggles on repeats · case 01
The event trace violates the physical down rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Physical modifier down replaces other keys or toggles on repeats · case 02
The event trace violates the physical down rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Physical modifier down replaces other keys or toggles on repeats · case 03
The event trace violates the physical down rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Physical modifier down replaces other keys or toggles on repeats · case 04
The event trace violates the physical down rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Physical modifier down replaces other keys or toggles on repeats · case 05
The event trace violates the physical down rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Modifier release erases the entire held set or keeps the released modifier active · case 01
The event trace violates the physical up rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Modifier release erases the entire held set or keeps the released modifier active · case 02
The event trace violates the physical up rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Modifier release erases the entire held set or keeps the released modifier active · case 03
The event trace violates the physical up rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Modifier release erases the entire held set or keeps the released modifier active · case 04
The event trace violates the physical up rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Modifier release erases the entire held set or keeps the released modifier active · case 05
The event trace violates the physical up rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Command modifier calculation loses physical or latched modifiers · case 01
The event trace violates the effective union rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Command modifier calculation loses physical or latched modifiers · case 02
The event trace violates the effective union rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Command modifier calculation loses physical or latched modifiers · case 03
The event trace violates the effective union rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Command modifier calculation loses physical or latched modifiers · case 04
The event trace violates the effective union rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Command modifier calculation loses physical or latched modifiers · case 05
The event trace violates the effective union rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Emitted chord modifier representation is noncanonical or omits latches · case 01
The event trace violates the modifier order rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Emitted chord modifier representation is noncanonical or omits latches · case 02
The event trace violates the modifier order rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Emitted chord modifier representation is noncanonical or omits latches · case 03
The event trace violates the modifier order rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Emitted chord modifier representation is noncanonical or omits latches · case 04
The event trace violates the modifier order rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Emitted chord modifier representation is noncanonical or omits latches · case 05
The event trace violates the modifier order rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Character dispatch consumes locked latches or preserves one-shot modifiers · case 01
The event trace violates the once consumption rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Character dispatch consumes locked latches or preserves one-shot modifiers · case 02
The event trace violates the once consumption rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Character dispatch consumes locked latches or preserves one-shot modifiers · case 03
The event trace violates the once consumption rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Character dispatch consumes locked latches or preserves one-shot modifiers · case 04
The event trace violates the once consumption rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Character dispatch consumes locked latches or preserves one-shot modifiers · case 05
The event trace violates the once consumption rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Cancelling sticky state incorrectly changes physically held modifiers · case 01
The event trace violates the cancel scope rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Cancelling sticky state incorrectly changes physically held modifiers · case 02
The event trace violates the cancel scope rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Cancelling sticky state incorrectly changes physically held modifiers · case 03
The event trace violates the cancel scope rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Cancelling sticky state incorrectly changes physically held modifiers · case 04
The event trace violates the cancel scope rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Cancelling sticky state incorrectly changes physically held modifiers · case 05
The event trace violates the cancel scope rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Input ownership loss clears only one source of effective modifiers · case 01
The event trace violates the blur reset rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Input ownership loss clears only one source of effective modifiers · case 02
The event trace violates the blur reset rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Input ownership loss clears only one source of effective modifiers · case 03
The event trace violates the blur reset rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Input ownership loss clears only one source of effective modifiers · case 04
The event trace violates the blur reset rule and produces incorrect keyboard state or command output.
Sticky modifier latch lifecycle: Input ownership loss clears only one source of effective modifiers · case 05
The event trace violates the blur reset rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Keyboard default mutation is suppressed despite a noncancelable keydown · case 01
The event trace violates the keydown cancelable rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Keyboard default mutation is suppressed despite a noncancelable keydown · case 02
The event trace violates the keydown cancelable rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Keyboard default mutation is suppressed despite a noncancelable keydown · case 03
The event trace violates the keydown cancelable rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Keyboard default mutation is suppressed despite a noncancelable keydown · case 04
The event trace violates the keydown cancelable rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Keyboard default mutation is suppressed despite a noncancelable keydown · case 05
The event trace violates the keydown cancelable rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Read-only input still runs an editing default action · case 01
The event trace violates the readonly gate rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Read-only input still runs an editing default action · case 02
The event trace violates the readonly gate rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Read-only input still runs an editing default action · case 03
The event trace violates the readonly gate rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Read-only input still runs an editing default action · case 04
The event trace violates the readonly gate rule and produces incorrect keyboard state or command output.
Keyboard default edit cancellation pipeline: Read-only input still runs an editing default action · case 05
The event trace violates the readonly gate 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 ↗