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
Asynchronous keyboard capture grant lifecycle: Requested capture keys are duplicated or retain noncanonical request order · case 01
The event trace violates the key dedup rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: Requested capture keys are duplicated or retain noncanonical request order · case 02
The event trace violates the key dedup rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: Requested capture keys are duplicated or retain noncanonical request order · case 03
The event trace violates the key dedup rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: Requested capture keys are duplicated or retain noncanonical request order · case 04
The event trace violates the key dedup rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: Requested capture keys are duplicated or retain noncanonical request order · case 05
The event trace violates the key dedup rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: A stale asynchronous grant activates a different pending keyboard request · case 01
The event trace violates the grant id rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: A stale asynchronous grant activates a different pending keyboard request · case 02
The event trace violates the grant id rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: A stale asynchronous grant activates a different pending keyboard request · case 03
The event trace violates the grant id rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: A stale asynchronous grant activates a different pending keyboard request · case 04
The event trace violates the grant id rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: A stale asynchronous grant activates a different pending keyboard request · case 05
The event trace violates the grant id rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: Reserved Escape is captured or all ordinary keys are discarded · case 01
The event trace violates the reserved escape rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: Reserved Escape is captured or all ordinary keys are discarded · case 02
The event trace violates the reserved escape rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: Reserved Escape is captured or all ordinary keys are discarded · case 03
The event trace violates the reserved escape rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: Reserved Escape is captured or all ordinary keys are discarded · case 04
The event trace violates the reserved escape rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: Reserved Escape is captured or all ordinary keys are discarded · case 05
The event trace violates the reserved escape rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: A new granted keyboard capture accumulates stale keys or captures no requested keys · case 01
The event trace violates the grant replace rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: A new granted keyboard capture accumulates stale keys or captures no requested keys · case 02
The event trace violates the grant replace rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: A new granted keyboard capture accumulates stale keys or captures no requested keys · case 03
The event trace violates the grant replace rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: A new granted keyboard capture accumulates stale keys or captures no requested keys · case 04
The event trace violates the grant replace rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: A new granted keyboard capture accumulates stale keys or captures no requested keys · case 05
The event trace violates the grant replace rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: A successful grant retains a pending callback token · case 01
The event trace violates the grant close rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: A successful grant retains a pending callback token · case 02
The event trace violates the grant close rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: A successful grant retains a pending callback token · case 03
The event trace violates the grant close rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: A successful grant retains a pending callback token · case 04
The event trace violates the grant close rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: A successful grant retains a pending callback token · case 05
The event trace violates the grant close rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: An old denial cancels a newer keyboard capture request · case 01
The event trace violates the deny id rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: An old denial cancels a newer keyboard capture request · case 02
The event trace violates the deny id rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: An old denial cancels a newer keyboard capture request · case 03
The event trace violates the deny id rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: An old denial cancels a newer keyboard capture request · case 04
The event trace violates the deny id rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: An old denial cancels a newer keyboard capture request · case 05
The event trace violates the deny id rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: Blur revokes only active capture or pending requests, leaving the other live · case 01
The event trace violates the blur clear rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: Blur revokes only active capture or pending requests, leaving the other live · case 02
The event trace violates the blur clear rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: Blur revokes only active capture or pending requests, leaving the other live · case 03
The event trace violates the blur clear rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: Blur revokes only active capture or pending requests, leaving the other live · case 04
The event trace violates the blur clear rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: Blur revokes only active capture or pending requests, leaving the other live · case 05
The event trace violates the blur clear rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: Explicit unlock leaves pending or already granted key capture active · case 01
The event trace violates the release all rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: Explicit unlock leaves pending or already granted key capture active · case 02
The event trace violates the release all rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: Explicit unlock leaves pending or already granted key capture active · case 03
The event trace violates the release all rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: Explicit unlock leaves pending or already granted key capture active · case 04
The event trace violates the release all rule and produces incorrect keyboard state or command output.
Asynchronous keyboard capture grant lifecycle: Explicit unlock leaves pending or already granted key capture active · case 05
The event trace violates the release all rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: Lock indicator toggle sets a bit permanently or treats bit index as mask · case 01
The event trace violates the lock toggle rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: Lock indicator toggle sets a bit permanently or treats bit index as mask · case 02
The event trace violates the lock toggle rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: Lock indicator toggle sets a bit permanently or treats bit index as mask · case 03
The event trace violates the lock toggle rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: Lock indicator toggle sets a bit permanently or treats bit index as mask · case 04
The event trace violates the lock toggle rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: Lock indicator toggle sets a bit permanently or treats bit index as mask · case 05
The event trace violates the lock toggle rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: LED snapshot requests are sent for unchanged state or omitted for dirty state · case 01
The event trace violates the send dirty rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: LED snapshot requests are sent for unchanged state or omitted for dirty state · case 02
The event trace violates the send dirty rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: LED snapshot requests are sent for unchanged state or omitted for dirty state · case 03
The event trace violates the send dirty rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: LED snapshot requests are sent for unchanged state or omitted for dirty state · case 04
The event trace violates the send dirty rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: LED snapshot requests are sent for unchanged state or omitted for dirty state · case 05
The event trace violates the send dirty rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: LED request sequence repeats or advances according to the lock mask · case 01
The event trace violates the request sequence rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: LED request sequence repeats or advances according to the lock mask · case 02
The event trace violates the request sequence rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: LED request sequence repeats or advances according to the lock mask · case 03
The event trace violates the request sequence rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: LED request sequence repeats or advances according to the lock mask · case 04
The event trace violates the request sequence rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: LED request sequence repeats or advances according to the lock mask · case 05
The event trace violates the request sequence rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: A request captures the acknowledged state or uses lock bits as request identity · case 01
The event trace violates the snapshot capture rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: A request captures the acknowledged state or uses lock bits as request identity · case 02
The event trace violates the snapshot capture rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: A request captures the acknowledged state or uses lock bits as request identity · case 03
The event trace violates the snapshot capture rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: A request captures the acknowledged state or uses lock bits as request identity · case 04
The event trace violates the snapshot capture rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: A request captures the acknowledged state or uses lock bits as request identity · case 05
The event trace violates the snapshot capture rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: Keyboard LED write serializes the wrong request id or mask · case 01
The event trace violates the wire payload rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: Keyboard LED write serializes the wrong request id or mask · case 02
The event trace violates the wire payload rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: Keyboard LED write serializes the wrong request id or mask · case 03
The event trace violates the wire payload rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: Keyboard LED write serializes the wrong request id or mask · case 04
The event trace violates the wire payload rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: Keyboard LED write serializes the wrong request id or mask · case 05
The event trace violates the wire payload rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: A valid LED acknowledgment is rejected by the wrong ordering watermark · case 01
The event trace violates the ack watermark rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: A valid LED acknowledgment is rejected by the wrong ordering watermark · case 02
The event trace violates the ack watermark rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: A valid LED acknowledgment is rejected by the wrong ordering watermark · case 03
The event trace violates the ack watermark rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: A valid LED acknowledgment is rejected by the wrong ordering watermark · case 04
The event trace violates the ack watermark rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: A valid LED acknowledgment is rejected by the wrong ordering watermark · case 05
The event trace violates the ack watermark rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: A delayed LED acknowledgment applies current desired bits or the request id rather than the sent snapshot · case 01
The event trace violates the apply snapshot rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: A delayed LED acknowledgment applies current desired bits or the request id rather than the sent snapshot · case 02
The event trace violates the apply snapshot rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: A delayed LED acknowledgment applies current desired bits or the request id rather than the sent snapshot · case 03
The event trace violates the apply snapshot rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: A delayed LED acknowledgment applies current desired bits or the request id rather than the sent snapshot · case 04
The event trace violates the apply snapshot rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: A delayed LED acknowledgment applies current desired bits or the request id rather than the sent snapshot · case 05
The event trace violates the apply snapshot rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: Acknowledgment watermark takes the latest sent serial or lock mask instead of completed request · case 01
The event trace violates the accepted id rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: Acknowledgment watermark takes the latest sent serial or lock mask instead of completed request · case 02
The event trace violates the accepted id rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: Acknowledgment watermark takes the latest sent serial or lock mask instead of completed request · case 03
The event trace violates the accepted id rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: Acknowledgment watermark takes the latest sent serial or lock mask instead of completed request · case 04
The event trace violates the accepted id rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: Acknowledgment watermark takes the latest sent serial or lock mask instead of completed request · case 05
The event trace violates the accepted id rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: Acknowledged and obsolete LED writes are retained or newer writes are discarded · case 01
The event trace violates the retire requests rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: Acknowledged and obsolete LED writes are retained or newer writes are discarded · case 02
The event trace violates the retire requests rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: Acknowledged and obsolete LED writes are retained or newer writes are discarded · case 03
The event trace violates the retire requests rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: Acknowledged and obsolete LED writes are retained or newer writes are discarded · case 04
The event trace violates the retire requests rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: Acknowledged and obsolete LED writes are retained or newer writes are discarded · case 05
The event trace violates the retire requests rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: Keyboard device reset loses desired lock state or preserves obsolete in-flight writes · case 01
The event trace violates the device reset rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: Keyboard device reset loses desired lock state or preserves obsolete in-flight writes · case 02
The event trace violates the device reset rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: Keyboard device reset loses desired lock state or preserves obsolete in-flight writes · case 03
The event trace violates the device reset rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: Keyboard device reset loses desired lock state or preserves obsolete in-flight writes · case 04
The event trace violates the device reset rule and produces incorrect keyboard state or command output.
Keyboard lock indicator request acknowledgements: Keyboard device reset loses desired lock state or preserves obsolete in-flight writes · case 05
The event trace violates the device reset rule and produces incorrect keyboard state or command output.
Keyboard matrix rectangle ghost quarantine: Matrix scan validation excludes row zero or admits an out-of-range row · case 01
The event trace violates the row domain rule and produces incorrect keyboard state or command output.
Keyboard matrix rectangle ghost quarantine: Matrix scan validation excludes row zero or admits an out-of-range row · case 02
The event trace violates the row domain rule and produces incorrect keyboard state or command output.
Keyboard matrix rectangle ghost quarantine: Matrix scan validation excludes row zero or admits an out-of-range row · case 03
The event trace violates the row domain rule and produces incorrect keyboard state or command output.
Keyboard matrix rectangle ghost quarantine: Matrix scan validation excludes row zero or admits an out-of-range row · case 04
The event trace violates the row domain rule and produces incorrect keyboard state or command output.
Keyboard matrix rectangle ghost quarantine: Matrix scan validation excludes row zero or admits an out-of-range row · case 05
The event trace violates the row domain rule and produces incorrect keyboard state or command output.
Keyboard matrix rectangle ghost quarantine: Matrix scan validation excludes column zero or admits an out-of-range column · case 01
The event trace violates the column domain rule and produces incorrect keyboard state or command output.
Keyboard matrix rectangle ghost quarantine: Matrix scan validation excludes column zero or admits an out-of-range column · case 02
The event trace violates the column domain rule and produces incorrect keyboard state or command output.
Keyboard matrix rectangle ghost quarantine: Matrix scan validation excludes column zero or admits an out-of-range column · case 03
The event trace violates the column domain rule and produces incorrect keyboard state or command output.
Keyboard matrix rectangle ghost quarantine: Matrix scan validation excludes column zero or admits an out-of-range column · case 04
The event trace violates the column domain rule and produces incorrect keyboard state or command output.
Keyboard matrix rectangle ghost quarantine: Matrix scan validation excludes column zero or admits an out-of-range column · case 05
The event trace violates the column domain 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 ↗