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
Tap versus hold command arbitration: Hold eligibility uses an exclusive boundary or absolute timestamp · case 01
The event trace violates the tick threshold rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: Hold eligibility uses an exclusive boundary or absolute timestamp · case 02
The event trace violates the tick threshold rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: Hold eligibility uses an exclusive boundary or absolute timestamp · case 03
The event trace violates the tick threshold rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: Hold eligibility uses an exclusive boundary or absolute timestamp · case 04
The event trace violates the tick threshold rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: Hold eligibility uses an exclusive boundary or absolute timestamp · case 05
The event trace violates the tick threshold rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: Repeated ticks emit the hold command more than once · case 01
The event trace violates the single hold rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: Repeated ticks emit the hold command more than once · case 02
The event trace violates the single hold rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: Repeated ticks emit the hold command more than once · case 03
The event trace violates the single hold rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: Repeated ticks emit the hold command more than once · case 04
The event trace violates the single hold rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: Repeated ticks emit the hold command more than once · case 05
The event trace violates the single hold rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: The timer emits the wrong gesture or uses the tick event key instead of pending key · case 01
The event trace violates the hold kind rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: The timer emits the wrong gesture or uses the tick event key instead of pending key · case 02
The event trace violates the hold kind rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: The timer emits the wrong gesture or uses the tick event key instead of pending key · case 03
The event trace violates the hold kind rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: The timer emits the wrong gesture or uses the tick event key instead of pending key · case 04
The event trace violates the hold kind rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: The timer emits the wrong gesture or uses the tick event key instead of pending key · case 05
The event trace violates the hold kind rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: The pending state does not record that a hold has already dispatched · case 01
The event trace violates the mark emitted rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: The pending state does not record that a hold has already dispatched · case 02
The event trace violates the mark emitted rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: The pending state does not record that a hold has already dispatched · case 03
The event trace violates the mark emitted rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: The pending state does not record that a hold has already dispatched · case 04
The event trace violates the mark emitted rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: The pending state does not record that a hold has already dispatched · case 05
The event trace violates the mark emitted rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: Releasing a dispatched hold emits a second command or suppresses taps · case 01
The event trace violates the up after hold rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: Releasing a dispatched hold emits a second command or suppresses taps · case 02
The event trace violates the up after hold rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: Releasing a dispatched hold emits a second command or suppresses taps · case 03
The event trace violates the up after hold rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: Releasing a dispatched hold emits a second command or suppresses taps · case 04
The event trace violates the up after hold rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: Releasing a dispatched hold emits a second command or suppresses taps · case 05
The event trace violates the up after hold rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: A release at the hold boundary is misclassified · case 01
The event trace violates the up threshold rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: A release at the hold boundary is misclassified · case 02
The event trace violates the up threshold rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: A release at the hold boundary is misclassified · case 03
The event trace violates the up threshold rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: A release at the hold boundary is misclassified · case 04
The event trace violates the up threshold rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: A release at the hold boundary is misclassified · case 05
The event trace violates the up threshold rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: Release clears other presses or retains a completed key · case 01
The event trace violates the release disarm rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: Release clears other presses or retains a completed key · case 02
The event trace violates the release disarm rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: Release clears other presses or retains a completed key · case 03
The event trace violates the release disarm rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: Release clears other presses or retains a completed key · case 04
The event trace violates the release disarm rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: Release clears other presses or retains a completed key · case 05
The event trace violates the release disarm rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: Cancellation disarms the wrong press set · case 01
The event trace violates the cancel key rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: Cancellation disarms the wrong press set · case 02
The event trace violates the cancel key rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: Cancellation disarms the wrong press set · case 03
The event trace violates the cancel key rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: Cancellation disarms the wrong press set · case 04
The event trace violates the cancel key rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: Cancellation disarms the wrong press set · case 05
The event trace violates the cancel key rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: Repeated press notifications toggle or replace the held set · case 01
The event trace violates the repeat down rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: Repeated press notifications toggle or replace the held set · case 02
The event trace violates the repeat down rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: Repeated press notifications toggle or replace the held set · case 03
The event trace violates the repeat down rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: Repeated press notifications toggle or replace the held set · case 04
The event trace violates the repeat down rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: Repeated press notifications toggle or replace the held set · case 05
The event trace violates the repeat down rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: An unmatched release counts as a tap even without its own down · case 01
The event trace violates the matched release rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: An unmatched release counts as a tap even without its own down · case 02
The event trace violates the matched release rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: An unmatched release counts as a tap even without its own down · case 03
The event trace violates the matched release rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: An unmatched release counts as a tap even without its own down · case 04
The event trace violates the matched release rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: An unmatched release counts as a tap even without its own down · case 05
The event trace violates the matched release rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: The matched release transition removes unrelated keys · case 01
The event trace violates the release remove rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: The matched release transition removes unrelated keys · case 02
The event trace violates the release remove rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: The matched release transition removes unrelated keys · case 03
The event trace violates the release remove rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: The matched release transition removes unrelated keys · case 04
The event trace violates the release remove rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: The matched release transition removes unrelated keys · case 05
The event trace violates the release remove rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: Tap accounting replaces its cumulative count or uses remaining held keys · case 01
The event trace violates the tap count rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: Tap accounting replaces its cumulative count or uses remaining held keys · case 02
The event trace violates the tap count rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: Tap accounting replaces its cumulative count or uses remaining held keys · case 03
The event trace violates the tap count rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: Tap accounting replaces its cumulative count or uses remaining held keys · case 04
The event trace violates the tap count rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: Tap accounting replaces its cumulative count or uses remaining held keys · case 05
The event trace violates the tap count rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: Double-tap matching borrows a release timestamp from a different key · case 01
The event trace violates the per key history rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: Double-tap matching borrows a release timestamp from a different key · case 02
The event trace violates the per key history rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: Double-tap matching borrows a release timestamp from a different key · case 03
The event trace violates the per key history rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: Double-tap matching borrows a release timestamp from a different key · case 04
The event trace violates the per key history rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: Double-tap matching borrows a release timestamp from a different key · case 05
The event trace violates the per key history rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: A valid first release at timestamp zero is mistaken for missing history · case 01
The event trace violates the zero timestamp rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: A valid first release at timestamp zero is mistaken for missing history · case 02
The event trace violates the zero timestamp rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: A valid first release at timestamp zero is mistaken for missing history · case 03
The event trace violates the zero timestamp rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: A valid first release at timestamp zero is mistaken for missing history · case 04
The event trace violates the zero timestamp rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: A valid first release at timestamp zero is mistaken for missing history · case 05
The event trace violates the zero timestamp rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: Double-tap acceptance excludes the deadline or compares the absolute time · case 01
The event trace violates the inclusive window rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: Double-tap acceptance excludes the deadline or compares the absolute time · case 02
The event trace violates the inclusive window rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: Double-tap acceptance excludes the deadline or compares the absolute time · case 03
The event trace violates the inclusive window rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: Double-tap acceptance excludes the deadline or compares the absolute time · case 04
The event trace violates the inclusive window rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: Double-tap acceptance excludes the deadline or compares the absolute time · case 05
The event trace violates the inclusive window rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: A completed double leaves a reusable release or consumes other keys history · case 01
The event trace violates the consume pair rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: A completed double leaves a reusable release or consumes other keys history · case 02
The event trace violates the consume pair rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: A completed double leaves a reusable release or consumes other keys history · case 03
The event trace violates the consume pair rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: A completed double leaves a reusable release or consumes other keys history · case 04
The event trace violates the consume pair rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: A completed double leaves a reusable release or consumes other keys history · case 05
The event trace violates the consume pair rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: An expired first tap does not replace its stale release timestamp · case 01
The event trace violates the new release rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: An expired first tap does not replace its stale release timestamp · case 02
The event trace violates the new release rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: An expired first tap does not replace its stale release timestamp · case 03
The event trace violates the new release rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: An expired first tap does not replace its stale release timestamp · case 04
The event trace violates the new release rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: An expired first tap does not replace its stale release timestamp · case 05
The event trace violates the new release rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: Losing input ownership only resets one half of double-tap state · case 01
The event trace violates the blur history rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: Losing input ownership only resets one half of double-tap state · case 02
The event trace violates the blur history rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: Losing input ownership only resets one half of double-tap state · case 03
The event trace violates the blur history rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: Losing input ownership only resets one half of double-tap state · case 04
The event trace violates the blur history rule and produces incorrect keyboard state or command output.
Per-key double tap recognizer: Losing input ownership only resets one half of double-tap state · case 05
The event trace violates the blur history rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Registration tie order is derived from priority instead of insertion chronology · case 01
The event trace violates the registration serial rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Registration tie order is derived from priority instead of insertion chronology · case 02
The event trace violates the registration serial rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Registration tie order is derived from priority instead of insertion chronology · case 03
The event trace violates the registration serial rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Registration tie order is derived from priority instead of insertion chronology · case 04
The event trace violates the registration serial rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Registration tie order is derived from priority instead of insertion chronology · case 05
The event trace violates the registration serial rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Re-registering an ID keeps stale binding data or keys storage by chord · case 01
The event trace violates the replace id rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Re-registering an ID keeps stale binding data or keys storage by chord · case 02
The event trace violates the replace id rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Re-registering an ID keeps stale binding data or keys storage by chord · case 03
The event trace violates the replace id rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Re-registering an ID keeps stale binding data or keys storage by chord · case 04
The event trace violates the replace id rule and produces incorrect keyboard state or command output.
Keyboard binding registration lifecycle: Re-registering an ID keeps stale binding data or keys storage by chord · case 05
The event trace violates the replace id 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 ↗