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 binding registration lifecycle: Removing one binding uses a chord identifier or clears all registrations · case 01
The event trace violates the remove id rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Removing one binding uses a chord identifier or clears all registrations · case 02
The event trace violates the remove id rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Removing one binding uses a chord identifier or clears all registrations · case 03
The event trace violates the remove id rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Removing one binding uses a chord identifier or clears all registrations · case 04
The event trace violates the remove id rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Removing one binding uses a chord identifier or clears all registrations · case 05
The event trace violates the remove id rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Scope teardown selects registrations using an inverted or unrelated identity · case 01
The event trace violates the clear scope rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Scope teardown selects registrations using an inverted or unrelated identity · case 02
The event trace violates the clear scope rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Scope teardown selects registrations using an inverted or unrelated identity · case 03
The event trace violates the clear scope rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Scope teardown selects registrations using an inverted or unrelated identity · case 04
The event trace violates the clear scope rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Scope teardown selects registrations using an inverted or unrelated identity · case 05
The event trace violates the clear scope rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Binding resolution crosses the requested scope boundary · case 01
The event trace violates the resolve scope rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Binding resolution crosses the requested scope boundary · case 02
The event trace violates the resolve scope rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Binding resolution crosses the requested scope boundary · case 03
The event trace violates the resolve scope rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Binding resolution crosses the requested scope boundary · case 04
The event trace violates the resolve scope rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Binding resolution crosses the requested scope boundary · case 05
The event trace violates the resolve scope rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: A chord is matched as a prefix or ignored rather than an exact configured sequence · case 01
The event trace violates the resolve chord rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: A chord is matched as a prefix or ignored rather than an exact configured sequence · case 02
The event trace violates the resolve chord rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: A chord is matched as a prefix or ignored rather than an exact configured sequence · case 03
The event trace violates the resolve chord rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: A chord is matched as a prefix or ignored rather than an exact configured sequence · case 04
The event trace violates the resolve chord rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: A chord is matched as a prefix or ignored rather than an exact configured sequence · case 05
The event trace violates the resolve chord rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: An unassigned empty shortcut is admitted into keyboard resolution · case 01
The event trace violates the empty chord rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: An unassigned empty shortcut is admitted into keyboard resolution · case 02
The event trace violates the empty chord rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: An unassigned empty shortcut is admitted into keyboard resolution · case 03
The event trace violates the empty chord rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: An unassigned empty shortcut is admitted into keyboard resolution · case 04
The event trace violates the empty chord rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: An unassigned empty shortcut is admitted into keyboard resolution · case 05
The event trace violates the empty chord rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Binding precedence uses recency before explicit priority or reverses priority · case 01
The event trace violates the priority sort rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Binding precedence uses recency before explicit priority or reverses priority · case 02
The event trace violates the priority sort rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Binding precedence uses recency before explicit priority or reverses priority · case 03
The event trace violates the priority sort rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Binding precedence uses recency before explicit priority or reverses priority · case 04
The event trace violates the priority sort rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Binding precedence uses recency before explicit priority or reverses priority · case 05
The event trace violates the priority sort rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Tie ordering is accidentally oldest-first outside a special scope · case 01
The event trace violates the tie recency rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Tie ordering is accidentally oldest-first outside a special scope · case 02
The event trace violates the tie recency rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Tie ordering is accidentally oldest-first outside a special scope · case 03
The event trace violates the tie recency rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Tie ordering is accidentally oldest-first outside a special scope · case 04
The event trace violates the tie recency rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Tie ordering is accidentally oldest-first outside a special scope · case 05
The event trace violates the tie recency rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Resolution returns the last candidate or its scope instead of winning ID · case 01
The event trace violates the winner rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Resolution returns the last candidate or its scope instead of winning ID · case 02
The event trace violates the winner rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Resolution returns the last candidate or its scope instead of winning ID · case 03
The event trace violates the winner rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Resolution returns the last candidate or its scope instead of winning ID · case 04
The event trace violates the winner rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Resolution returns the last candidate or its scope instead of winning ID · case 05
The event trace violates the winner rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Layout switch keeps the previous generation or reverses generation ownership · case 01
The event trace violates the generation replace rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Layout switch keeps the previous generation or reverses generation ownership · case 02
The event trace violates the generation replace rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Layout switch keeps the previous generation or reverses generation ownership · case 03
The event trace violates the generation replace rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Layout switch keeps the previous generation or reverses generation ownership · case 04
The event trace violates the generation replace rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Layout switch keeps the previous generation or reverses generation ownership · case 05
The event trace violates the generation replace rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Changing one keyboard layout invalidates unrelated devices or preserves its own stale labels · case 01
The event trace violates the layout invalidate rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Changing one keyboard layout invalidates unrelated devices or preserves its own stale labels · case 02
The event trace violates the layout invalidate rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Changing one keyboard layout invalidates unrelated devices or preserves its own stale labels · case 03
The event trace violates the layout invalidate rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Changing one keyboard layout invalidates unrelated devices or preserves its own stale labels · case 04
The event trace violates the layout invalidate rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Changing one keyboard layout invalidates unrelated devices or preserves its own stale labels · case 05
The event trace violates the layout invalidate rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Mapping entries are accepted before a keyboard layout is established · case 01
The event trace violates the map lifecycle rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Mapping entries are accepted before a keyboard layout is established · case 02
The event trace violates the map lifecycle rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Mapping entries are accepted before a keyboard layout is established · case 03
The event trace violates the map lifecycle rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Mapping entries are accepted before a keyboard layout is established · case 04
The event trace violates the map lifecycle rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Mapping entries are accepted before a keyboard layout is established · case 05
The event trace violates the map lifecycle rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Physical code and device identity are misplaced in the layout cache key · case 01
The event trace violates the map key rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Physical code and device identity are misplaced in the layout cache key · case 02
The event trace violates the map key rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Physical code and device identity are misplaced in the layout cache key · case 03
The event trace violates the map key rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Physical code and device identity are misplaced in the layout cache key · case 04
The event trace violates the map key rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Physical code and device identity are misplaced in the layout cache key · case 05
The event trace violates the map key rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: An updated code label fails to replace the previous cached label · case 01
The event trace violates the map replace rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: An updated code label fails to replace the previous cached label · case 02
The event trace violates the map replace rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: An updated code label fails to replace the previous cached label · case 03
The event trace violates the map replace rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: An updated code label fails to replace the previous cached label · case 04
The event trace violates the map replace rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: An updated code label fails to replace the previous cached label · case 05
The event trace violates the map replace rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: A lookup on an uninitialized device emits labels from an unrelated layout lifecycle · case 01
The event trace violates the lookup lifecycle rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: A lookup on an uninitialized device emits labels from an unrelated layout lifecycle · case 02
The event trace violates the lookup lifecycle rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: A lookup on an uninitialized device emits labels from an unrelated layout lifecycle · case 03
The event trace violates the lookup lifecycle rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: A lookup on an uninitialized device emits labels from an unrelated layout lifecycle · case 04
The event trace violates the lookup lifecycle rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: A lookup on an uninitialized device emits labels from an unrelated layout lifecycle · case 05
The event trace violates the lookup lifecycle rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Layout lookup indexes by reversed ownership or unrelated payload · case 01
The event trace violates the lookup key rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Layout lookup indexes by reversed ownership or unrelated payload · case 02
The event trace violates the lookup key rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Layout lookup indexes by reversed ownership or unrelated payload · case 03
The event trace violates the lookup key rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Layout lookup indexes by reversed ownership or unrelated payload · case 04
The event trace violates the lookup key rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Layout lookup indexes by reversed ownership or unrelated payload · case 05
The event trace violates the lookup key rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: An unmapped physical code loses its stable fallback label · case 01
The event trace violates the lookup fallback rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: An unmapped physical code loses its stable fallback label · case 02
The event trace violates the lookup fallback rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: An unmapped physical code loses its stable fallback label · case 03
The event trace violates the lookup fallback rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: An unmapped physical code loses its stable fallback label · case 04
The event trace violates the lookup fallback rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: An unmapped physical code loses its stable fallback label · case 05
The event trace violates the lookup fallback rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Disconnect removes the wrong generation records · case 01
The event trace violates the disconnect generation rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Disconnect removes the wrong generation records · case 02
The event trace violates the disconnect generation rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Disconnect removes the wrong generation records · case 03
The event trace violates the disconnect generation rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Disconnect removes the wrong generation records · case 04
The event trace violates the disconnect generation rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Disconnect removes the wrong generation records · case 05
The event trace violates the disconnect generation rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Disconnect preserves stale labels or erases another keyboard cache · case 01
The event trace violates the disconnect cache rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Disconnect preserves stale labels or erases another keyboard cache · case 02
The event trace violates the disconnect cache rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Disconnect preserves stale labels or erases another keyboard cache · case 03
The event trace violates the disconnect cache rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Disconnect preserves stale labels or erases another keyboard cache · case 04
The event trace violates the disconnect cache rule and produces incorrect keyboard state or command output.
Keyboard layout mapping generations: Disconnect preserves stale labels or erases another keyboard cache · case 05
The event trace violates the disconnect cache rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Layer activation refuses known empty transparent layers · case 01
The event trace violates the unknown layer rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Layer activation refuses known empty transparent layers · case 02
The event trace violates the unknown layer rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Layer activation refuses known empty transparent layers · case 03
The event trace violates the unknown layer rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Layer activation refuses known empty transparent layers · case 04
The event trace violates the unknown layer rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Layer activation refuses known empty transparent layers · case 05
The event trace violates the unknown layer rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Activating an already active remap layer duplicates its lifecycle entry · case 01
The event trace violates the duplicate push rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Activating an already active remap layer duplicates its lifecycle entry · case 02
The event trace violates the duplicate push rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Activating an already active remap layer duplicates its lifecycle entry · case 03
The event trace violates the duplicate push rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Activating an already active remap layer duplicates its lifecycle entry · case 04
The event trace violates the duplicate push rule and produces incorrect keyboard state or command output.
Layered physical keyboard remapping: Activating an already active remap layer duplicates its lifecycle entry · case 05
The event trace violates the duplicate push 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 ↗