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
Release activated command binding: Command provenance is assembled from the wrong event fields · case 01
The event trace violates the emission pair rule and produces incorrect keyboard state or command output.
Release activated command binding: Command provenance is assembled from the wrong event fields · case 02
The event trace violates the emission pair rule and produces incorrect keyboard state or command output.
Release activated command binding: Command provenance is assembled from the wrong event fields · case 03
The event trace violates the emission pair rule and produces incorrect keyboard state or command output.
Release activated command binding: Command provenance is assembled from the wrong event fields · case 04
The event trace violates the emission pair rule and produces incorrect keyboard state or command output.
Release activated command binding: Command provenance is assembled from the wrong event fields · case 05
The event trace violates the emission pair rule and produces incorrect keyboard state or command output.
Release activated command binding: Orphan release accounting loses multiple unmatched transitions · case 01
The event trace violates the unmatched count rule and produces incorrect keyboard state or command output.
Release activated command binding: Orphan release accounting loses multiple unmatched transitions · case 02
The event trace violates the unmatched count rule and produces incorrect keyboard state or command output.
Release activated command binding: Orphan release accounting loses multiple unmatched transitions · case 03
The event trace violates the unmatched count rule and produces incorrect keyboard state or command output.
Release activated command binding: Orphan release accounting loses multiple unmatched transitions · case 04
The event trace violates the unmatched count rule and produces incorrect keyboard state or command output.
Release activated command binding: Orphan release accounting loses multiple unmatched transitions · case 05
The event trace violates the unmatched count rule and produces incorrect keyboard state or command output.
Release activated command binding: A release disarms unrelated bindings or leaves its own binding armed · case 01
The event trace violates the up disarm rule and produces incorrect keyboard state or command output.
Release activated command binding: A release disarms unrelated bindings or leaves its own binding armed · case 02
The event trace violates the up disarm rule and produces incorrect keyboard state or command output.
Release activated command binding: A release disarms unrelated bindings or leaves its own binding armed · case 03
The event trace violates the up disarm rule and produces incorrect keyboard state or command output.
Release activated command binding: A release disarms unrelated bindings or leaves its own binding armed · case 04
The event trace violates the up disarm rule and produces incorrect keyboard state or command output.
Release activated command binding: A release disarms unrelated bindings or leaves its own binding armed · case 05
The event trace violates the up disarm rule and produces incorrect keyboard state or command output.
Release activated command binding: Cancellation accounting fails to count each pending command once · case 01
The event trace violates the cancel count rule and produces incorrect keyboard state or command output.
Release activated command binding: Cancellation accounting fails to count each pending command once · case 02
The event trace violates the cancel count rule and produces incorrect keyboard state or command output.
Release activated command binding: Cancellation accounting fails to count each pending command once · case 03
The event trace violates the cancel count rule and produces incorrect keyboard state or command output.
Release activated command binding: Cancellation accounting fails to count each pending command once · case 04
The event trace violates the cancel count rule and produces incorrect keyboard state or command output.
Release activated command binding: Cancellation accounting fails to count each pending command once · case 05
The event trace violates the cancel count rule and produces incorrect keyboard state or command output.
Release activated command binding: Global cancellation leaves unrelated pending release commands alive · case 01
The event trace violates the cancel clear rule and produces incorrect keyboard state or command output.
Release activated command binding: Global cancellation leaves unrelated pending release commands alive · case 02
The event trace violates the cancel clear rule and produces incorrect keyboard state or command output.
Release activated command binding: Global cancellation leaves unrelated pending release commands alive · case 03
The event trace violates the cancel clear rule and produces incorrect keyboard state or command output.
Release activated command binding: Global cancellation leaves unrelated pending release commands alive · case 04
The event trace violates the cancel clear rule and produces incorrect keyboard state or command output.
Release activated command binding: Global cancellation leaves unrelated pending release commands alive · case 05
The event trace violates the cancel clear rule and produces incorrect keyboard state or command output.
Release activated command binding: Owner departure selects pending bindings by key or inverse owner · case 01
The event trace violates the departure owner rule and produces incorrect keyboard state or command output.
Release activated command binding: Owner departure selects pending bindings by key or inverse owner · case 02
The event trace violates the departure owner rule and produces incorrect keyboard state or command output.
Release activated command binding: Owner departure selects pending bindings by key or inverse owner · case 03
The event trace violates the departure owner rule and produces incorrect keyboard state or command output.
Release activated command binding: Owner departure selects pending bindings by key or inverse owner · case 04
The event trace violates the departure owner rule and produces incorrect keyboard state or command output.
Release activated command binding: Owner departure selects pending bindings by key or inverse owner · case 05
The event trace violates the departure owner rule and produces incorrect keyboard state or command output.
Release activated command binding: Owner departure counts one notification instead of all invalidated presses · case 01
The event trace violates the departure count rule and produces incorrect keyboard state or command output.
Release activated command binding: Owner departure counts one notification instead of all invalidated presses · case 02
The event trace violates the departure count rule and produces incorrect keyboard state or command output.
Release activated command binding: Owner departure counts one notification instead of all invalidated presses · case 03
The event trace violates the departure count rule and produces incorrect keyboard state or command output.
Release activated command binding: Owner departure counts one notification instead of all invalidated presses · case 04
The event trace violates the departure count rule and produces incorrect keyboard state or command output.
Release activated command binding: Owner departure counts one notification instead of all invalidated presses · case 05
The event trace violates the departure count rule and produces incorrect keyboard state or command output.
Release activated command binding: Owner departure removes a token named after the owner or clears other owners · case 01
The event trace violates the departure remove rule and produces incorrect keyboard state or command output.
Release activated command binding: Owner departure removes a token named after the owner or clears other owners · case 02
The event trace violates the departure remove rule and produces incorrect keyboard state or command output.
Release activated command binding: Owner departure removes a token named after the owner or clears other owners · case 03
The event trace violates the departure remove rule and produces incorrect keyboard state or command output.
Release activated command binding: Owner departure removes a token named after the owner or clears other owners · case 04
The event trace violates the departure remove rule and produces incorrect keyboard state or command output.
Release activated command binding: Owner departure removes a token named after the owner or clears other owners · case 05
The event trace violates the departure remove rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: An auto-repeat down resets the software repeat timer · case 01
The event trace violates the down rearm rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: An auto-repeat down resets the software repeat timer · case 02
The event trace violates the down rearm rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: An auto-repeat down resets the software repeat timer · case 03
The event trace violates the down rearm rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: An auto-repeat down resets the software repeat timer · case 04
The event trace violates the down rearm rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: An auto-repeat down resets the software repeat timer · case 05
The event trace violates the down rearm rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: The initial key press is omitted or timestamped at the delayed repeat · case 01
The event trace violates the initial emission rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: The initial key press is omitted or timestamped at the delayed repeat · case 02
The event trace violates the initial emission rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: The initial key press is omitted or timestamped at the delayed repeat · case 03
The event trace violates the initial emission rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: The initial key press is omitted or timestamped at the delayed repeat · case 04
The event trace violates the initial emission rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: The initial key press is omitted or timestamped at the delayed repeat · case 05
The event trace violates the initial emission rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: First-repeat delay is replaced with the repeat interval or an absolute epoch · case 01
The event trace violates the first deadline rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: First-repeat delay is replaced with the repeat interval or an absolute epoch · case 02
The event trace violates the first deadline rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: First-repeat delay is replaced with the repeat interval or an absolute epoch · case 03
The event trace violates the first deadline rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: First-repeat delay is replaced with the repeat interval or an absolute epoch · case 04
The event trace violates the first deadline rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: First-repeat delay is replaced with the repeat interval or an absolute epoch · case 05
The event trace violates the first deadline rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: Releasing one key cancels other keys or retains its own timer · case 01
The event trace violates the up unschedule rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: Releasing one key cancels other keys or retains its own timer · case 02
The event trace violates the up unschedule rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: Releasing one key cancels other keys or retains its own timer · case 03
The event trace violates the up unschedule rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: Releasing one key cancels other keys or retains its own timer · case 04
The event trace violates the up unschedule rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: Releasing one key cancels other keys or retains its own timer · case 05
The event trace violates the up unschedule rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: Window blur leaves per-key repeat deadlines running · case 01
The event trace violates the blur cancel rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: Window blur leaves per-key repeat deadlines running · case 02
The event trace violates the blur cancel rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: Window blur leaves per-key repeat deadlines running · case 03
The event trace violates the blur cancel rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: Window blur leaves per-key repeat deadlines running · case 04
The event trace violates the blur cancel rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: Window blur leaves per-key repeat deadlines running · case 05
The event trace violates the blur cancel rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: Initial timer drain omits exact-boundary or overdue deadlines · case 01
The event trace violates the first inclusive rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: Initial timer drain omits exact-boundary or overdue deadlines · case 02
The event trace violates the first inclusive rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: Initial timer drain omits exact-boundary or overdue deadlines · case 03
The event trace violates the first inclusive rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: Initial timer drain omits exact-boundary or overdue deadlines · case 04
The event trace violates the first inclusive rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: Initial timer drain omits exact-boundary or overdue deadlines · case 05
The event trace violates the first inclusive rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: Concurrent repeats are emitted in key order instead of chronological deadline order · case 01
The event trace violates the deadline order rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: Concurrent repeats are emitted in key order instead of chronological deadline order · case 02
The event trace violates the deadline order rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: Concurrent repeats are emitted in key order instead of chronological deadline order · case 03
The event trace violates the deadline order rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: Concurrent repeats are emitted in key order instead of chronological deadline order · case 04
The event trace violates the deadline order rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: Concurrent repeats are emitted in key order instead of chronological deadline order · case 05
The event trace violates the deadline order rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: A caught-up repeat receives the polling time rather than its scheduled deadline · case 01
The event trace violates the repeat time rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: A caught-up repeat receives the polling time rather than its scheduled deadline · case 02
The event trace violates the repeat time rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: A caught-up repeat receives the polling time rather than its scheduled deadline · case 03
The event trace violates the repeat time rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: A caught-up repeat receives the polling time rather than its scheduled deadline · case 04
The event trace violates the repeat time rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: A caught-up repeat receives the polling time rather than its scheduled deadline · case 05
The event trace violates the repeat time rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: Repeat advancement drifts with polling time or reuses initial delay · case 01
The event trace violates the deadline advance rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: Repeat advancement drifts with polling time or reuses initial delay · case 02
The event trace violates the deadline advance rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: Repeat advancement drifts with polling time or reuses initial delay · case 03
The event trace violates the deadline advance rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: Repeat advancement drifts with polling time or reuses initial delay · case 04
The event trace violates the deadline advance rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: Repeat advancement drifts with polling time or reuses initial delay · case 05
The event trace violates the deadline advance rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: The timer drain stops after one emission or skips a later equal deadline · case 01
The event trace violates the drain boundary rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: The timer drain stops after one emission or skips a later equal deadline · case 02
The event trace violates the drain boundary rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: The timer drain stops after one emission or skips a later equal deadline · case 03
The event trace violates the drain boundary rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: The timer drain stops after one emission or skips a later equal deadline · case 04
The event trace violates the drain boundary rule and produces incorrect keyboard state or command output.
Owned repeat deadline scheduler: The timer drain stops after one emission or skips a later equal deadline · case 05
The event trace violates the drain boundary rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: Repeated downs restart a hold duration or prevent first press arming · case 01
The event trace violates the press origin rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: Repeated downs restart a hold duration or prevent first press arming · case 02
The event trace violates the press origin rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: Repeated downs restart a hold duration or prevent first press arming · case 03
The event trace violates the press origin rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: Repeated downs restart a hold duration or prevent first press arming · case 04
The event trace violates the press origin rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: Repeated downs restart a hold duration or prevent first press arming · case 05
The event trace violates the press origin rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: A fresh press is marked already dispatched or anchored to time zero · case 01
The event trace violates the initial held rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: A fresh press is marked already dispatched or anchored to time zero · case 02
The event trace violates the initial held rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: A fresh press is marked already dispatched or anchored to time zero · case 03
The event trace violates the initial held rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: A fresh press is marked already dispatched or anchored to time zero · case 04
The event trace violates the initial held rule and produces incorrect keyboard state or command output.
Tap versus hold command arbitration: A fresh press is marked already dispatched or anchored to time zero · case 05
The event trace violates the initial held 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 ↗