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
Composition transaction ownership: Preedit updates from another focused editor cross the transaction boundary · case 01
The event trace violates the update owner rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Preedit updates from another focused editor cross the transaction boundary · case 02
The event trace violates the update owner rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Preedit updates from another focused editor cross the transaction boundary · case 03
The event trace violates the update owner rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Preedit updates from another focused editor cross the transaction boundary · case 04
The event trace violates the update owner rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Preedit updates from another focused editor cross the transaction boundary · case 05
The event trace violates the update owner rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Composition update is treated as incremental text rather than a replacement · case 01
The event trace violates the replace update rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Composition update is treated as incremental text rather than a replacement · case 02
The event trace violates the replace update rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Composition update is treated as incremental text rather than a replacement · case 03
The event trace violates the replace update rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Composition update is treated as incremental text rather than a replacement · case 04
The event trace violates the replace update rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Composition update is treated as incremental text rather than a replacement · case 05
The event trace violates the replace update rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Applied update count is confused with text length or latest state · case 01
The event trace violates the update count rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Applied update count is confused with text length or latest state · case 02
The event trace violates the update count rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Applied update count is confused with text length or latest state · case 03
The event trace violates the update count rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Applied update count is confused with text length or latest state · case 04
The event trace violates the update count rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Applied update count is confused with text length or latest state · case 05
The event trace violates the update count rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Foreign or orphan commits append text outside an active owned transaction · case 01
The event trace violates the commit owner rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Foreign or orphan commits append text outside an active owned transaction · case 02
The event trace violates the commit owner rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Foreign or orphan commits append text outside an active owned transaction · case 03
The event trace violates the commit owner rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Foreign or orphan commits append text outside an active owned transaction · case 04
The event trace violates the commit owner rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Foreign or orphan commits append text outside an active owned transaction · case 05
The event trace violates the commit owner rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Final composition payload is replaced with provisional text or split into characters · case 01
The event trace violates the commit payload rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Final composition payload is replaced with provisional text or split into characters · case 02
The event trace violates the commit payload rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Final composition payload is replaced with provisional text or split into characters · case 03
The event trace violates the commit payload rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Final composition payload is replaced with provisional text or split into characters · case 04
The event trace violates the commit payload rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Final composition payload is replaced with provisional text or split into characters · case 05
The event trace violates the commit payload rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Committing leaves a reusable ownership token that permits duplicate commits · case 01
The event trace violates the commit close rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Committing leaves a reusable ownership token that permits duplicate commits · case 02
The event trace violates the commit close rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Committing leaves a reusable ownership token that permits duplicate commits · case 03
The event trace violates the commit close rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Committing leaves a reusable ownership token that permits duplicate commits · case 04
The event trace violates the commit close rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Committing leaves a reusable ownership token that permits duplicate commits · case 05
The event trace violates the commit close rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Cancellation from another editor closes the current composition · case 01
The event trace violates the cancel match rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Cancellation from another editor closes the current composition · case 02
The event trace violates the cancel match rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Cancellation from another editor closes the current composition · case 03
The event trace violates the cancel match rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Cancellation from another editor closes the current composition · case 04
The event trace violates the cancel match rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Cancellation from another editor closes the current composition · case 05
The event trace violates the cancel match rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Moving focus fails to invalidate the composition belonging to the old editor · case 01
The event trace violates the focus invalidation rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Moving focus fails to invalidate the composition belonging to the old editor · case 02
The event trace violates the focus invalidation rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Moving focus fails to invalidate the composition belonging to the old editor · case 03
The event trace violates the focus invalidation rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Moving focus fails to invalidate the composition belonging to the old editor · case 04
The event trace violates the focus invalidation rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Moving focus fails to invalidate the composition belonging to the old editor · case 05
The event trace violates the focus invalidation rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Down events toggle or replace physical chord state instead of inserting · case 01
The event trace violates the down set rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Down events toggle or replace physical chord state instead of inserting · case 02
The event trace violates the down set rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Down events toggle or replace physical chord state instead of inserting · case 03
The event trace violates the down set rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Down events toggle or replace physical chord state instead of inserting · case 04
The event trace violates the down set rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Down events toggle or replace physical chord state instead of inserting · case 05
The event trace violates the down set rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: One released member erases unrelated held chord members · case 01
The event trace violates the up removal rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: One released member erases unrelated held chord members · case 02
The event trace violates the up removal rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: One released member erases unrelated held chord members · case 03
The event trace violates the up removal rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: One released member erases unrelated held chord members · case 04
The event trace violates the up removal rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: One released member erases unrelated held chord members · case 05
The event trace violates the up removal rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Cancellation retains a partial chord across input ownership loss · case 01
The event trace violates the cancel reset rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Cancellation retains a partial chord across input ownership loss · case 02
The event trace violates the cancel reset rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Cancellation retains a partial chord across input ownership loss · case 03
The event trace violates the cancel reset rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Cancellation retains a partial chord across input ownership loss · case 04
The event trace violates the cancel reset rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Cancellation retains a partial chord across input ownership loss · case 05
The event trace violates the cancel reset rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: An empty configured chord is treated as complete · case 01
The event trace violates the empty chord rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: An empty configured chord is treated as complete · case 02
The event trace violates the empty chord rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: An empty configured chord is treated as complete · case 03
The event trace violates the empty chord rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: An empty configured chord is treated as complete · case 04
The event trace violates the empty chord rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: An empty configured chord is treated as complete · case 05
The event trace violates the empty chord rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Chord activation ignores extra depressed keys or missing members · case 01
The event trace violates the extra key rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Chord activation ignores extra depressed keys or missing members · case 02
The event trace violates the extra key rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Chord activation ignores extra depressed keys or missing members · case 03
The event trace violates the extra key rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Chord activation ignores extra depressed keys or missing members · case 04
The event trace violates the extra key rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Chord activation ignores extra depressed keys or missing members · case 05
The event trace violates the extra key rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Held complete chord dispatches on repeated downs after its activation edge · case 01
The event trace violates the edge latch rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Held complete chord dispatches on repeated downs after its activation edge · case 02
The event trace violates the edge latch rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Held complete chord dispatches on repeated downs after its activation edge · case 03
The event trace violates the edge latch rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Held complete chord dispatches on repeated downs after its activation edge · case 04
The event trace violates the edge latch rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Held complete chord dispatches on repeated downs after its activation edge · case 05
The event trace violates the edge latch rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: A release that removes an extra key activates the chord without a press edge · case 01
The event trace violates the event phase rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: A release that removes an extra key activates the chord without a press edge · case 02
The event trace violates the event phase rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: A release that removes an extra key activates the chord without a press edge · case 03
The event trace violates the event phase rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: A release that removes an extra key activates the chord without a press edge · case 04
The event trace violates the event phase rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: A release that removes an extra key activates the chord without a press edge · case 05
The event trace violates the event phase rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Chord dispatch count uses member count or overwrites previous activations · case 01
The event trace violates the fire counter rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Chord dispatch count uses member count or overwrites previous activations · case 02
The event trace violates the fire counter rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Chord dispatch count uses member count or overwrites previous activations · case 03
The event trace violates the fire counter rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Chord dispatch count uses member count or overwrites previous activations · case 04
The event trace violates the fire counter rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Chord dispatch count uses member count or overwrites previous activations · case 05
The event trace violates the fire counter rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: The trigger is taken from sorted chord membership rather than the last pressed key · case 01
The event trace violates the trigger key rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: The trigger is taken from sorted chord membership rather than the last pressed key · case 02
The event trace violates the trigger key rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: The trigger is taken from sorted chord membership rather than the last pressed key · case 03
The event trace violates the trigger key rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: The trigger is taken from sorted chord membership rather than the last pressed key · case 04
The event trace violates the trigger key rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: The trigger is taken from sorted chord membership rather than the last pressed key · case 05
The event trace violates the trigger key rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Partial release does not rearm the chord for a new completion edge · case 01
The event trace violates the rearm rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Partial release does not rearm the chord for a new completion edge · case 02
The event trace violates the rearm rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Partial release does not rearm the chord for a new completion edge · case 03
The event trace violates the rearm rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Partial release does not rearm the chord for a new completion edge · case 04
The event trace violates the rearm rule and produces incorrect keyboard state or command output.
Simultaneous chord edge recognizer: Partial release does not rearm the chord for a new completion edge · case 05
The event trace violates the rearm rule and produces incorrect keyboard state or command output.
Release activated command binding: A repeat transfers release ownership to a different receiver · case 01
The event trace violates the repeat owner rule and produces incorrect keyboard state or command output.
Release activated command binding: A repeat transfers release ownership to a different receiver · case 02
The event trace violates the repeat owner rule and produces incorrect keyboard state or command output.
Release activated command binding: A repeat transfers release ownership to a different receiver · case 03
The event trace violates the repeat owner rule and produces incorrect keyboard state or command output.
Release activated command binding: A repeat transfers release ownership to a different receiver · case 04
The event trace violates the repeat owner rule and produces incorrect keyboard state or command output.
Release activated command binding: A repeat transfers release ownership to a different receiver · case 05
The event trace violates the repeat owner rule and produces incorrect keyboard state or command output.
Release activated command binding: Release dispatch ignores the owner that accepted the press · case 01
The event trace violates the up owner rule and produces incorrect keyboard state or command output.
Release activated command binding: Release dispatch ignores the owner that accepted the press · case 02
The event trace violates the up owner rule and produces incorrect keyboard state or command output.
Release activated command binding: Release dispatch ignores the owner that accepted the press · case 03
The event trace violates the up owner rule and produces incorrect keyboard state or command output.
Release activated command binding: Release dispatch ignores the owner that accepted the press · case 04
The event trace violates the up owner rule and produces incorrect keyboard state or command output.
Release activated command binding: Release dispatch ignores the owner that accepted the press · case 05
The event trace violates the up owner 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 ↗