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 macro deterministic playback scheduler: Cycle scheduling omits the inter-cycle gap or recorded duration · case 01
The event trace violates the cycle origin rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Cycle scheduling omits the inter-cycle gap or recorded duration · case 02
The event trace violates the cycle origin rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Cycle scheduling omits the inter-cycle gap or recorded duration · case 03
The event trace violates the cycle origin rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Cycle scheduling omits the inter-cycle gap or recorded duration · case 04
The event trace violates the cycle origin rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Cycle scheduling omits the inter-cycle gap or recorded duration · case 05
The event trace violates the cycle origin rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Synthesized key releases reverse canonical ordering or omit additional held keys · case 01
The event trace violates the cleanup order rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Synthesized key releases reverse canonical ordering or omit additional held keys · case 02
The event trace violates the cleanup order rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Synthesized key releases reverse canonical ordering or omit additional held keys · case 03
The event trace violates the cleanup order rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Synthesized key releases reverse canonical ordering or omit additional held keys · case 04
The event trace violates the cleanup order rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Synthesized key releases reverse canonical ordering or omit additional held keys · case 05
The event trace violates the cleanup order rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Stroke speed scaling is inverted or scales the absolute start time · case 01
The event trace violates the deadline ratio rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Stroke speed scaling is inverted or scales the absolute start time · case 02
The event trace violates the deadline ratio rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Stroke speed scaling is inverted or scales the absolute start time · case 03
The event trace violates the deadline ratio rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Stroke speed scaling is inverted or scales the absolute start time · case 04
The event trace violates the deadline ratio rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Stroke speed scaling is inverted or scales the absolute start time · case 05
The event trace violates the deadline ratio rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Stroke deadlines round upward rather than applying the contract floor · case 01
The event trace violates the deadline rounding rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Stroke deadlines round upward rather than applying the contract floor · case 02
The event trace violates the deadline rounding rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Stroke deadlines round upward rather than applying the contract floor · case 03
The event trace violates the deadline rounding rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Stroke deadlines round upward rather than applying the contract floor · case 04
The event trace violates the deadline rounding rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Stroke deadlines round upward rather than applying the contract floor · case 05
The event trace violates the deadline rounding rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Playback cleanup loses held keys after repeated or simultaneous downs · case 01
The event trace violates the press track rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Playback cleanup loses held keys after repeated or simultaneous downs · case 02
The event trace violates the press track rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Playback cleanup loses held keys after repeated or simultaneous downs · case 03
The event trace violates the press track rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Playback cleanup loses held keys after repeated or simultaneous downs · case 04
The event trace violates the press track rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Playback cleanup loses held keys after repeated or simultaneous downs · case 05
The event trace violates the press track rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: A recorded release clears unrelated held keys or fails to disarm its key · case 01
The event trace violates the release track rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: A recorded release clears unrelated held keys or fails to disarm its key · case 02
The event trace violates the release track rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: A recorded release clears unrelated held keys or fails to disarm its key · case 03
The event trace violates the release track rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: A recorded release clears unrelated held keys or fails to disarm its key · case 04
The event trace violates the release track rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: A recorded release clears unrelated held keys or fails to disarm its key · case 05
The event trace violates the release track rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Playback changes release events into presses or swaps key and phase · case 01
The event trace violates the output phase rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Playback changes release events into presses or swaps key and phase · case 02
The event trace violates the output phase rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Playback changes release events into presses or swaps key and phase · case 03
The event trace violates the output phase rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Playback changes release events into presses or swaps key and phase · case 04
The event trace violates the output phase rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Playback changes release events into presses or swaps key and phase · case 05
The event trace violates the output phase rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Synthesized release cleanup happens after the gap or uses the first cycle time · case 01
The event trace violates the cleanup time rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Synthesized release cleanup happens after the gap or uses the first cycle time · case 02
The event trace violates the cleanup time rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Synthesized release cleanup happens after the gap or uses the first cycle time · case 03
The event trace violates the cleanup time rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Synthesized release cleanup happens after the gap or uses the first cycle time · case 04
The event trace violates the cleanup time rule and produces incorrect keyboard state or command output.
Keyboard macro deterministic playback scheduler: Synthesized release cleanup happens after the gap or uses the first cycle time · case 05
The event trace violates the cleanup time rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Raw release candidates disappear from the scan domain before their timer matures · case 01
The event trace violates the released scan domain rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Raw release candidates disappear from the scan domain before their timer matures · case 02
The event trace violates the released scan domain rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Raw release candidates disappear from the scan domain before their timer matures · case 03
The event trace violates the released scan domain rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Raw release candidates disappear from the scan domain before their timer matures · case 04
The event trace violates the released scan domain rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Raw release candidates disappear from the scan domain before their timer matures · case 05
The event trace violates the released scan domain rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: One held switch makes every known switch appear pressed · case 01
The event trace violates the raw membership rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: One held switch makes every known switch appear pressed · case 02
The event trace violates the raw membership rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: One held switch makes every known switch appear pressed · case 03
The event trace violates the raw membership rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: One held switch makes every known switch appear pressed · case 04
The event trace violates the raw membership rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: One held switch makes every known switch appear pressed · case 05
The event trace violates the raw membership rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Contact bounce fails to restart the candidate timer or stable samples continually restart it · case 01
The event trace violates the candidate change rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Contact bounce fails to restart the candidate timer or stable samples continually restart it · case 02
The event trace violates the candidate change rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Contact bounce fails to restart the candidate timer or stable samples continually restart it · case 03
The event trace violates the candidate change rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Contact bounce fails to restart the candidate timer or stable samples continually restart it · case 04
The event trace violates the candidate change rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Contact bounce fails to restart the candidate timer or stable samples continually restart it · case 05
The event trace violates the candidate change rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Candidate state records the opposite level or assumes every transition is a press · case 01
The event trace violates the candidate value rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Candidate state records the opposite level or assumes every transition is a press · case 02
The event trace violates the candidate value rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Candidate state records the opposite level or assumes every transition is a press · case 03
The event trace violates the candidate value rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Candidate state records the opposite level or assumes every transition is a press · case 04
The event trace violates the candidate value rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Candidate state records the opposite level or assumes every transition is a press · case 05
The event trace violates the candidate value rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Debounce dwell time is measured from the epoch or the first-ever contact transition · case 01
The event trace violates the timer origin rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Debounce dwell time is measured from the epoch or the first-ever contact transition · case 02
The event trace violates the timer origin rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Debounce dwell time is measured from the epoch or the first-ever contact transition · case 03
The event trace violates the timer origin rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Debounce dwell time is measured from the epoch or the first-ever contact transition · case 04
The event trace violates the timer origin rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Debounce dwell time is measured from the epoch or the first-ever contact transition · case 05
The event trace violates the timer origin rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Debounce commits before sufficient stable dwell or misses the exact threshold · case 01
The event trace violates the inclusive dwell rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Debounce commits before sufficient stable dwell or misses the exact threshold · case 02
The event trace violates the inclusive dwell rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Debounce commits before sufficient stable dwell or misses the exact threshold · case 03
The event trace violates the inclusive dwell rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Debounce commits before sufficient stable dwell or misses the exact threshold · case 04
The event trace violates the inclusive dwell rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Debounce commits before sufficient stable dwell or misses the exact threshold · case 05
The event trace violates the inclusive dwell rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Debounced notifications fire for unchanged level samples instead of stable edges · case 01
The event trace violates the edge only rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Debounced notifications fire for unchanged level samples instead of stable edges · case 02
The event trace violates the edge only rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Debounced notifications fire for unchanged level samples instead of stable edges · case 03
The event trace violates the edge only rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Debounced notifications fire for unchanged level samples instead of stable edges · case 04
The event trace violates the edge only rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Debounced notifications fire for unchanged level samples instead of stable edges · case 05
The event trace violates the edge only rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Committed switch level disagrees with its emitted edge · case 01
The event trace violates the stable commit rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Committed switch level disagrees with its emitted edge · case 02
The event trace violates the stable commit rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Committed switch level disagrees with its emitted edge · case 03
The event trace violates the stable commit rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Committed switch level disagrees with its emitted edge · case 04
The event trace violates the stable commit rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Committed switch level disagrees with its emitted edge · case 05
The event trace violates the stable commit rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Debounced release is published as a press · case 01
The event trace violates the edge name rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Debounced release is published as a press · case 02
The event trace violates the edge name rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Debounced release is published as a press · case 03
The event trace violates the edge name rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Debounced release is published as a press · case 04
The event trace violates the edge name rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Debounced release is published as a press · case 05
The event trace violates the edge name rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Debounced transition is timestamped at raw contact time or delayed by a second dwell · case 01
The event trace violates the edge time rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Debounced transition is timestamped at raw contact time or delayed by a second dwell · case 02
The event trace violates the edge time rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Debounced transition is timestamped at raw contact time or delayed by a second dwell · case 03
The event trace violates the edge time rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Debounced transition is timestamped at raw contact time or delayed by a second dwell · case 04
The event trace violates the edge time rule and produces incorrect keyboard state or command output.
Per-switch keyboard scan debounce: Debounced transition is timestamped at raw contact time or delayed by a second dwell · case 05
The event trace violates the edge time rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: Coalescing consumes release notifications or initial nonrepeat presses · case 01
The event trace violates the repeat eligibility rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: Coalescing consumes release notifications or initial nonrepeat presses · case 02
The event trace violates the repeat eligibility rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: Coalescing consumes release notifications or initial nonrepeat presses · case 03
The event trace violates the repeat eligibility rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: Coalescing consumes release notifications or initial nonrepeat presses · case 04
The event trace violates the repeat eligibility rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: Coalescing consumes release notifications or initial nonrepeat presses · case 05
The event trace violates the repeat eligibility rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: Repeat runs are merged across physical devices or key codes · case 01
The event trace violates the device boundary rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: Repeat runs are merged across physical devices or key codes · case 02
The event trace violates the device boundary rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: Repeat runs are merged across physical devices or key codes · case 03
The event trace violates the device boundary rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: Repeat runs are merged across physical devices or key codes · case 04
The event trace violates the device boundary rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: Repeat runs are merged across physical devices or key codes · case 05
The event trace violates the device boundary 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 ↗