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
Retry hook failure containment: Hook failure fatal violates retry transition semantics · case 01
Hook failure fatal violates retry transition semantics
Retry hook failure containment: Hook failure fatal violates retry transition semantics · case 02
Hook failure fatal violates retry transition semantics
Retry hook failure containment: Hook failure fatal violates retry transition semantics · case 03
Hook failure fatal violates retry transition semantics
Retry hook failure containment: Hook failure fatal violates retry transition semantics · case 04
Hook failure fatal violates retry transition semantics
Retry hook failure containment: Hook failure fatal violates retry transition semantics · case 05
Hook failure fatal violates retry transition semantics
Retry hook failure containment: Hook error not network violates retry transition semantics · case 01
Hook error not network violates retry transition semantics
Retry hook failure containment: Hook error not network violates retry transition semantics · case 02
Hook error not network violates retry transition semantics
Retry hook failure containment: Hook error not network violates retry transition semantics · case 03
Hook error not network violates retry transition semantics
Retry hook failure containment: Hook error not network violates retry transition semantics · case 04
Hook error not network violates retry transition semantics
Retry hook failure containment: Hook error not network violates retry transition semantics · case 05
Hook error not network violates retry transition semantics
Retry hook failure containment: Hook admission budget violates retry transition semantics · case 01
Hook admission budget violates retry transition semantics
Retry hook failure containment: Hook admission budget violates retry transition semantics · case 02
Hook admission budget violates retry transition semantics
Retry hook failure containment: Hook admission budget violates retry transition semantics · case 03
Hook admission budget violates retry transition semantics
Retry hook failure containment: Hook admission budget violates retry transition semantics · case 04
Hook admission budget violates retry transition semantics
Retry hook failure containment: Hook admission budget violates retry transition semantics · case 05
Hook admission budget violates retry transition semantics
Retry hook failure containment: Await hook delay violates retry transition semantics · case 01
Await hook delay violates retry transition semantics
Retry hook failure containment: Await hook delay violates retry transition semantics · case 02
Await hook delay violates retry transition semantics
Retry hook failure containment: Await hook delay violates retry transition semantics · case 03
Await hook delay violates retry transition semantics
Retry hook failure containment: Await hook delay violates retry transition semantics · case 04
Await hook delay violates retry transition semantics
Retry hook failure containment: Await hook delay violates retry transition semantics · case 05
Await hook delay violates retry transition semantics
Retry hook failure containment: Success before observer violates retry transition semantics · case 01
Success before observer violates retry transition semantics
Retry hook failure containment: Success before observer violates retry transition semantics · case 02
Success before observer violates retry transition semantics
Retry hook failure containment: Success before observer violates retry transition semantics · case 03
Success before observer violates retry transition semantics
Retry hook failure containment: Success before observer violates retry transition semantics · case 04
Success before observer violates retry transition semantics
Retry hook failure containment: Success before observer violates retry transition semantics · case 05
Success before observer violates retry transition semantics
Retry hook failure containment: Observer only failure violates retry transition semantics · case 01
Observer only failure violates retry transition semantics
Retry hook failure containment: Observer only failure violates retry transition semantics · case 02
Observer only failure violates retry transition semantics
Retry hook failure containment: Observer only failure violates retry transition semantics · case 03
Observer only failure violates retry transition semantics
Retry hook failure containment: Observer only failure violates retry transition semantics · case 04
Observer only failure violates retry transition semantics
Retry hook failure containment: Observer only failure violates retry transition semantics · case 05
Observer only failure violates retry transition semantics
Retry hook failure containment: Late success observer violates retry transition semantics · case 01
Late success observer violates retry transition semantics
Retry hook failure containment: Late success observer violates retry transition semantics · case 02
Late success observer violates retry transition semantics
Retry hook failure containment: Late success observer violates retry transition semantics · case 03
Late success observer violates retry transition semantics
Retry hook failure containment: Late success observer violates retry transition semantics · case 04
Late success observer violates retry transition semantics
Retry hook failure containment: Late success observer violates retry transition semantics · case 05
Late success observer violates retry transition semantics
Retry hook failure containment: Cancel pending hook violates retry transition semantics · case 01
Cancel pending hook violates retry transition semantics
Retry hook failure containment: Cancel pending hook violates retry transition semantics · case 02
Cancel pending hook violates retry transition semantics
Retry hook failure containment: Cancel pending hook violates retry transition semantics · case 03
Cancel pending hook violates retry transition semantics
Retry hook failure containment: Cancel pending hook violates retry transition semantics · case 04
Cancel pending hook violates retry transition semantics
Retry hook failure containment: Cancel pending hook violates retry transition semantics · case 05
Cancel pending hook violates retry transition semantics
Physical press ownership registry: Device identity is discarded while identifying a held physical key · case 01
The event trace violates the device token rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Device identity is discarded while identifying a held physical key · case 02
The event trace violates the device token rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Device identity is discarded while identifying a held physical key · case 03
The event trace violates the device token rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Device identity is discarded while identifying a held physical key · case 04
The event trace violates the device token rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Device identity is discarded while identifying a held physical key · case 05
The event trace violates the device token rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Physical location is collapsed so two distinct locations alias · case 01
The event trace violates the location token rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Physical location is collapsed so two distinct locations alias · case 02
The event trace violates the location token rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Physical location is collapsed so two distinct locations alias · case 03
The event trace violates the location token rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Physical location is collapsed so two distinct locations alias · case 04
The event trace violates the location token rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Physical location is collapsed so two distinct locations alias · case 05
The event trace violates the location token rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Repeated down events are counted as additional physical presses · case 01
The event trace violates the repeat accounting rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Repeated down events are counted as additional physical presses · case 02
The event trace violates the repeat accounting rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Repeated down events are counted as additional physical presses · case 03
The event trace violates the repeat accounting rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Repeated down events are counted as additional physical presses · case 04
The event trace violates the repeat accounting rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Repeated down events are counted as additional physical presses · case 05
The event trace violates the repeat accounting rule and produces incorrect keyboard state or command output.
Physical press ownership registry: A physical down does not persistently insert the held token · case 01
The event trace violates the insert press rule and produces incorrect keyboard state or command output.
Physical press ownership registry: A physical down does not persistently insert the held token · case 02
The event trace violates the insert press rule and produces incorrect keyboard state or command output.
Physical press ownership registry: A physical down does not persistently insert the held token · case 03
The event trace violates the insert press rule and produces incorrect keyboard state or command output.
Physical press ownership registry: A physical down does not persistently insert the held token · case 04
The event trace violates the insert press rule and produces incorrect keyboard state or command output.
Physical press ownership registry: A physical down does not persistently insert the held token · case 05
The event trace violates the insert press rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Peak simultaneous keys is replaced by the latest or cumulative count · case 01
The event trace violates the peak count rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Peak simultaneous keys is replaced by the latest or cumulative count · case 02
The event trace violates the peak count rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Peak simultaneous keys is replaced by the latest or cumulative count · case 03
The event trace violates the peak count rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Peak simultaneous keys is replaced by the latest or cumulative count · case 04
The event trace violates the peak count rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Peak simultaneous keys is replaced by the latest or cumulative count · case 05
The event trace violates the peak count rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Releasing one physical key clears unrelated held tokens · case 01
The event trace violates the release identity rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Releasing one physical key clears unrelated held tokens · case 02
The event trace violates the release identity rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Releasing one physical key clears unrelated held tokens · case 03
The event trace violates the release identity rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Releasing one physical key clears unrelated held tokens · case 04
The event trace violates the release identity rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Releasing one physical key clears unrelated held tokens · case 05
The event trace violates the release identity rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Accepted releases are not accumulated one per matched up · case 01
The event trace violates the release count rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Accepted releases are not accumulated one per matched up · case 02
The event trace violates the release count rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Accepted releases are not accumulated one per matched up · case 03
The event trace violates the release count rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Accepted releases are not accumulated one per matched up · case 04
The event trace violates the release count rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Accepted releases are not accumulated one per matched up · case 05
The event trace violates the release count rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Unmatched release events are not counted individually · case 01
The event trace violates the orphan count rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Unmatched release events are not counted individually · case 02
The event trace violates the orphan count rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Unmatched release events are not counted individually · case 03
The event trace violates the orphan count rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Unmatched release events are not counted individually · case 04
The event trace violates the orphan count rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Unmatched release events are not counted individually · case 05
The event trace violates the orphan count rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Device disconnect removes the wrong ownership set · case 01
The event trace violates the disconnect scope rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Device disconnect removes the wrong ownership set · case 02
The event trace violates the disconnect scope rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Device disconnect removes the wrong ownership set · case 03
The event trace violates the disconnect scope rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Device disconnect removes the wrong ownership set · case 04
The event trace violates the disconnect scope rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Device disconnect removes the wrong ownership set · case 05
The event trace violates the disconnect scope rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Window blur leaves physical keys held without future release delivery · case 01
The event trace violates the blur reset rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Window blur leaves physical keys held without future release delivery · case 02
The event trace violates the blur reset rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Window blur leaves physical keys held without future release delivery · case 03
The event trace violates the blur reset rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Window blur leaves physical keys held without future release delivery · case 04
The event trace violates the blur reset rule and produces incorrect keyboard state or command output.
Physical press ownership registry: Window blur leaves physical keys held without future release delivery · case 05
The event trace violates the blur reset rule and produces incorrect keyboard state or command output.
Composition transaction ownership: A new composition keeps stale transaction ownership · case 01
The event trace violates the start owner rule and produces incorrect keyboard state or command output.
Composition transaction ownership: A new composition keeps stale transaction ownership · case 02
The event trace violates the start owner rule and produces incorrect keyboard state or command output.
Composition transaction ownership: A new composition keeps stale transaction ownership · case 03
The event trace violates the start owner rule and produces incorrect keyboard state or command output.
Composition transaction ownership: A new composition keeps stale transaction ownership · case 04
The event trace violates the start owner rule and produces incorrect keyboard state or command output.
Composition transaction ownership: A new composition keeps stale transaction ownership · case 05
The event trace violates the start owner rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Starting a composition fails to replace the previous preedit · case 01
The event trace violates the start preedit rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Starting a composition fails to replace the previous preedit · case 02
The event trace violates the start preedit rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Starting a composition fails to replace the previous preedit · case 03
The event trace violates the start preedit rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Starting a composition fails to replace the previous preedit · case 04
The event trace violates the start preedit rule and produces incorrect keyboard state or command output.
Composition transaction ownership: Starting a composition fails to replace the previous preedit · case 05
The event trace violates the start preedit 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 ↗