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
Adjacent keyboard repeat batch coalescing: A repeated event overwrites the first time or leaves the last time stale · case 01
The event trace violates the latest time rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: A repeated event overwrites the first time or leaves the last time stale · case 02
The event trace violates the latest time rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: A repeated event overwrites the first time or leaves the last time stale · case 03
The event trace violates the latest time rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: A repeated event overwrites the first time or leaves the last time stale · case 04
The event trace violates the latest time rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: A repeated event overwrites the first time or leaves the last time stale · case 05
The event trace violates the latest time rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: Repeat batch count uses timestamp arithmetic instead of event cardinality · case 01
The event trace violates the repeat count rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: Repeat batch count uses timestamp arithmetic instead of event cardinality · case 02
The event trace violates the repeat count rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: Repeat batch count uses timestamp arithmetic instead of event cardinality · case 03
The event trace violates the repeat count rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: Repeat batch count uses timestamp arithmetic instead of event cardinality · case 04
The event trace violates the repeat count rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: Repeat batch count uses timestamp arithmetic instead of event cardinality · case 05
The event trace violates the repeat count rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: Changing physical token loses the previous repeat batch or emits the wrong entry type · case 01
The event trace violates the token flush rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: Changing physical token loses the previous repeat batch or emits the wrong entry type · case 02
The event trace violates the token flush rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: Changing physical token loses the previous repeat batch or emits the wrong entry type · case 03
The event trace violates the token flush rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: Changing physical token loses the previous repeat batch or emits the wrong entry type · case 04
The event trace violates the token flush rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: Changing physical token loses the previous repeat batch or emits the wrong entry type · case 05
The event trace violates the token flush rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: A new repeat batch initializes a timestamp from an unrelated epoch · case 01
The event trace violates the initial times rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: A new repeat batch initializes a timestamp from an unrelated epoch · case 02
The event trace violates the initial times rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: A new repeat batch initializes a timestamp from an unrelated epoch · case 03
The event trace violates the initial times rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: A new repeat batch initializes a timestamp from an unrelated epoch · case 04
The event trace violates the initial times rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: A new repeat batch initializes a timestamp from an unrelated epoch · case 05
The event trace violates the initial times rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: A raw key barrier loses or misclassifies the accumulated repeat batch · case 01
The event trace violates the barrier flush rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: A raw key barrier loses or misclassifies the accumulated repeat batch · case 02
The event trace violates the barrier flush rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: A raw key barrier loses or misclassifies the accumulated repeat batch · case 03
The event trace violates the barrier flush rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: A raw key barrier loses or misclassifies the accumulated repeat batch · case 04
The event trace violates the barrier flush rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: A raw key barrier loses or misclassifies the accumulated repeat batch · case 05
The event trace violates the barrier flush rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: A raw event leaves the previous repeat batch active for later merging · case 01
The event trace violates the barrier reset rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: A raw event leaves the previous repeat batch active for later merging · case 02
The event trace violates the barrier reset rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: A raw event leaves the previous repeat batch active for later merging · case 03
The event trace violates the barrier reset rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: A raw event leaves the previous repeat batch active for later merging · case 04
The event trace violates the barrier reset rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: A raw event leaves the previous repeat batch active for later merging · case 05
The event trace violates the barrier reset rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: Raw barrier event identity or timestamp is corrupted during repeat coalescing · case 01
The event trace violates the raw payload rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: Raw barrier event identity or timestamp is corrupted during repeat coalescing · case 02
The event trace violates the raw payload rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: Raw barrier event identity or timestamp is corrupted during repeat coalescing · case 03
The event trace violates the raw payload rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: Raw barrier event identity or timestamp is corrupted during repeat coalescing · case 04
The event trace violates the raw payload rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: Raw barrier event identity or timestamp is corrupted during repeat coalescing · case 05
The event trace violates the raw payload rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: The final repeat batch is not emitted with its required entry type · case 01
The event trace violates the final flush rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: The final repeat batch is not emitted with its required entry type · case 02
The event trace violates the final flush rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: The final repeat batch is not emitted with its required entry type · case 03
The event trace violates the final flush rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: The final repeat batch is not emitted with its required entry type · case 04
The event trace violates the final flush rule and produces incorrect keyboard state or command output.
Adjacent keyboard repeat batch coalescing: The final repeat batch is not emitted with its required entry type · case 05
The event trace violates the final flush rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: A remap update does not affect future physical presses · case 01
The event trace violates the future map rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: A remap update does not affect future physical presses · case 02
The event trace violates the future map rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: A remap update does not affect future physical presses · case 03
The event trace violates the future map rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: A remap update does not affect future physical presses · case 04
The event trace violates the future map rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: A remap update does not affect future physical presses · case 05
The event trace violates the future map rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Repeated physical downs acquire extra logical references · case 01
The event trace violates the repeat reference rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Repeated physical downs acquire extra logical references · case 02
The event trace violates the repeat reference rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Repeated physical downs acquire extra logical references · case 03
The event trace violates the repeat reference rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Repeated physical downs acquire extra logical references · case 04
The event trace violates the repeat reference rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Repeated physical downs acquire extra logical references · case 05
The event trace violates the repeat reference rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: An unconfigured physical key loses its passthrough mapping · case 01
The event trace violates the unmapped identity rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: An unconfigured physical key loses its passthrough mapping · case 02
The event trace violates the unmapped identity rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: An unconfigured physical key loses its passthrough mapping · case 03
The event trace violates the unmapped identity rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: An unconfigured physical key loses its passthrough mapping · case 04
The event trace violates the unmapped identity rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: An unconfigured physical key loses its passthrough mapping · case 05
The event trace violates the unmapped identity rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Physical press ownership stores event payload instead of the resolved logical target · case 01
The event trace violates the captured target rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Physical press ownership stores event payload instead of the resolved logical target · case 02
The event trace violates the captured target rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Physical press ownership stores event payload instead of the resolved logical target · case 03
The event trace violates the captured target rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Physical press ownership stores event payload instead of the resolved logical target · case 04
The event trace violates the captured target rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Physical press ownership stores event payload instead of the resolved logical target · case 05
The event trace violates the captured target rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Disabled output is counted as a logical key or empty-string targets are lost · case 01
The event trace violates the disabled target rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Disabled output is counted as a logical key or empty-string targets are lost · case 02
The event trace violates the disabled target rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Disabled output is counted as a logical key or empty-string targets are lost · case 03
The event trace violates the disabled target rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Disabled output is counted as a logical key or empty-string targets are lost · case 04
The event trace violates the disabled target rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Disabled output is counted as a logical key or empty-string targets are lost · case 05
The event trace violates the disabled target rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Logical reference count fails to represent multiple physical owners · case 01
The event trace violates the logical increment rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Logical reference count fails to represent multiple physical owners · case 02
The event trace violates the logical increment rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Logical reference count fails to represent multiple physical owners · case 03
The event trace violates the logical increment rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Logical reference count fails to represent multiple physical owners · case 04
The event trace violates the logical increment rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Logical reference count fails to represent multiple physical owners · case 05
The event trace violates the logical increment rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Logical down is emitted for every owner instead of only the first acquisition · case 01
The event trace violates the first owner edge rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Logical down is emitted for every owner instead of only the first acquisition · case 02
The event trace violates the first owner edge rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Logical down is emitted for every owner instead of only the first acquisition · case 03
The event trace violates the first owner edge rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Logical down is emitted for every owner instead of only the first acquisition · case 04
The event trace violates the first owner edge rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Logical down is emitted for every owner instead of only the first acquisition · case 05
The event trace violates the first owner edge rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Physical release resolves the current mapping instead of its press-time mapping · case 01
The event trace violates the release captured rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Physical release resolves the current mapping instead of its press-time mapping · case 02
The event trace violates the release captured rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Physical release resolves the current mapping instead of its press-time mapping · case 03
The event trace violates the release captured rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Physical release resolves the current mapping instead of its press-time mapping · case 04
The event trace violates the release captured rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Physical release resolves the current mapping instead of its press-time mapping · case 05
The event trace violates the release captured rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Logical release drops all owners or fails to release its own reference · case 01
The event trace violates the logical decrement rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Logical release drops all owners or fails to release its own reference · case 02
The event trace violates the logical decrement rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Logical release drops all owners or fails to release its own reference · case 03
The event trace violates the logical decrement rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Logical release drops all owners or fails to release its own reference · case 04
The event trace violates the logical decrement rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Logical release drops all owners or fails to release its own reference · case 05
The event trace violates the logical decrement rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Reset clears only physical or logical ownership, leaving a mismatched held-key state · case 01
The event trace violates the reset ownership rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Reset clears only physical or logical ownership, leaving a mismatched held-key state · case 02
The event trace violates the reset ownership rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Reset clears only physical or logical ownership, leaving a mismatched held-key state · case 03
The event trace violates the reset ownership rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Reset clears only physical or logical ownership, leaving a mismatched held-key state · case 04
The event trace violates the reset ownership rule and produces incorrect keyboard state or command output.
Press-time remapping and logical key reference counts: Reset clears only physical or logical ownership, leaving a mismatched held-key state · case 05
The event trace violates the reset ownership rule and produces incorrect keyboard state or command output.
Tap-hold dual-role keyboard key: Repeated dual-role down resets the hold clock or suppresses initial arming · case 01
The event trace violates the dual repeat rule and produces incorrect keyboard state or command output.
Tap-hold dual-role keyboard key: Repeated dual-role down resets the hold clock or suppresses initial arming · case 02
The event trace violates the dual repeat rule and produces incorrect keyboard state or command output.
Tap-hold dual-role keyboard key: Repeated dual-role down resets the hold clock or suppresses initial arming · case 03
The event trace violates the dual repeat rule and produces incorrect keyboard state or command output.
Tap-hold dual-role keyboard key: Repeated dual-role down resets the hold clock or suppresses initial arming · case 04
The event trace violates the dual repeat rule and produces incorrect keyboard state or command output.
Tap-hold dual-role keyboard key: Repeated dual-role down resets the hold clock or suppresses initial arming · case 05
The event trace violates the dual repeat rule and produces incorrect keyboard state or command output.
Tap-hold dual-role keyboard key: Foreign key presses re-emit modifier down or fail to promote pending tap · case 01
The event trace violates the foreign promotion rule and produces incorrect keyboard state or command output.
Tap-hold dual-role keyboard key: Foreign key presses re-emit modifier down or fail to promote pending tap · case 02
The event trace violates the foreign promotion rule and produces incorrect keyboard state or command output.
Tap-hold dual-role keyboard key: Foreign key presses re-emit modifier down or fail to promote pending tap · case 03
The event trace violates the foreign promotion rule and produces incorrect keyboard state or command output.
Tap-hold dual-role keyboard key: Foreign key presses re-emit modifier down or fail to promote pending tap · case 04
The event trace violates the foreign promotion rule and produces incorrect keyboard state or command output.
Tap-hold dual-role keyboard key: Foreign key presses re-emit modifier down or fail to promote pending tap · case 05
The event trace violates the foreign promotion 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 ↗