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
Notification undo affordance: undo-failure from undo-pending · case 01
The undo-failure event leaves a notification in restored instead of retry-offered.
Notification undo affordance: undo-failure from undo-pending · case 02
The undo-failure event leaves a notification in restored instead of retry-offered.
Notification undo affordance: undo-failure from undo-pending · case 03
The undo-failure event leaves a notification in restored instead of retry-offered.
Notification undo affordance: undo-failure from undo-pending · case 04
The undo-failure event leaves a notification in restored instead of retry-offered.
Notification undo affordance: undo-failure from undo-pending · case 05
The undo-failure event leaves a notification in restored instead of retry-offered.
Notification undo affordance: window-end from offered · case 01
The window-end event leaves a notification in restored instead of committed.
Notification undo affordance: window-end from offered · case 02
The window-end event leaves a notification in restored instead of committed.
Notification undo affordance: window-end from offered · case 03
The window-end event leaves a notification in restored instead of committed.
Notification undo affordance: window-end from offered · case 04
The window-end event leaves a notification in restored instead of committed.
Notification undo affordance: window-end from offered · case 05
The window-end event leaves a notification in restored instead of committed.
Notification undo affordance: window-end from undo-pending · case 01
The window-end event leaves a notification in committed instead of undo-pending.
Notification undo affordance: window-end from undo-pending · case 02
The window-end event leaves a notification in committed instead of undo-pending.
Notification undo affordance: window-end from undo-pending · case 03
The window-end event leaves a notification in committed instead of undo-pending.
Notification undo affordance: window-end from undo-pending · case 04
The window-end event leaves a notification in committed instead of undo-pending.
Notification undo affordance: window-end from undo-pending · case 05
The window-end event leaves a notification in committed instead of undo-pending.
Notification undo affordance: retry-click from retry-offered · case 01
The retry-click event leaves a notification in restored instead of undo-pending.
Notification undo affordance: retry-click from retry-offered · case 02
The retry-click event leaves a notification in restored instead of undo-pending.
Notification undo affordance: retry-click from retry-offered · case 03
The retry-click event leaves a notification in restored instead of undo-pending.
Notification undo affordance: retry-click from retry-offered · case 04
The retry-click event leaves a notification in restored instead of undo-pending.
Notification undo affordance: retry-click from retry-offered · case 05
The retry-click event leaves a notification in restored instead of undo-pending.
Notification undo affordance: late-window-end from restored · case 01
The late-window-end event leaves a notification in committed instead of restored.
Notification undo affordance: late-window-end from restored · case 02
The late-window-end event leaves a notification in committed instead of restored.
Notification undo affordance: late-window-end from restored · case 03
The late-window-end event leaves a notification in committed instead of restored.
Notification undo affordance: late-window-end from restored · case 04
The late-window-end event leaves a notification in committed instead of restored.
Notification undo affordance: late-window-end from restored · case 05
The late-window-end event leaves a notification in committed instead of restored.
Notification undo affordance: late-undo-click from committed · case 01
The late-undo-click event leaves a notification in undo-pending instead of too-late.
Notification undo affordance: late-undo-click from committed · case 02
The late-undo-click event leaves a notification in undo-pending instead of too-late.
Notification undo affordance: late-undo-click from committed · case 03
The late-undo-click event leaves a notification in undo-pending instead of too-late.
Notification undo affordance: late-undo-click from committed · case 04
The late-undo-click event leaves a notification in undo-pending instead of too-late.
Notification undo affordance: late-undo-click from committed · case 05
The late-undo-click event leaves a notification in undo-pending instead of too-late.
Notification undo affordance: acknowledge from too-late · case 01
The acknowledge event leaves a notification in offered instead of closed.
Notification undo affordance: acknowledge from too-late · case 02
The acknowledge event leaves a notification in offered instead of closed.
Notification undo affordance: acknowledge from too-late · case 03
The acknowledge event leaves a notification in offered instead of closed.
Notification undo affordance: acknowledge from too-late · case 04
The acknowledge event leaves a notification in offered instead of closed.
Notification undo affordance: acknowledge from too-late · case 05
The acknowledge event leaves a notification in offered instead of closed.
Notification undo affordance: dismiss-error from retry-offered · case 01
The dismiss-error event leaves a notification in restored instead of committed.
Notification undo affordance: dismiss-error from retry-offered · case 02
The dismiss-error event leaves a notification in restored instead of committed.
Notification undo affordance: dismiss-error from retry-offered · case 03
The dismiss-error event leaves a notification in restored instead of committed.
Notification undo affordance: dismiss-error from retry-offered · case 04
The dismiss-error event leaves a notification in restored instead of committed.
Notification undo affordance: dismiss-error from retry-offered · case 05
The dismiss-error event leaves a notification in restored instead of committed.
Toast action request feedback: action-click from ready · case 01
The action-click event leaves a notification in succeeded instead of submitting.
Toast action request feedback: action-click from ready · case 02
The action-click event leaves a notification in succeeded instead of submitting.
Toast action request feedback: action-click from ready · case 03
The action-click event leaves a notification in succeeded instead of submitting.
Toast action request feedback: action-click from ready · case 04
The action-click event leaves a notification in succeeded instead of submitting.
Toast action request feedback: action-click from ready · case 05
The action-click event leaves a notification in succeeded instead of submitting.
Toast action request feedback: second-click from submitting · case 01
The second-click event leaves a notification in ready instead of submitting.
Toast action request feedback: second-click from submitting · case 02
The second-click event leaves a notification in ready instead of submitting.
Toast action request feedback: second-click from submitting · case 03
The second-click event leaves a notification in ready instead of submitting.
Toast action request feedback: second-click from submitting · case 04
The second-click event leaves a notification in ready instead of submitting.
Toast action request feedback: second-click from submitting · case 05
The second-click event leaves a notification in ready instead of submitting.
Toast action request feedback: accepted from submitting · case 01
The accepted event leaves a notification in succeeded instead of running.
Toast action request feedback: accepted from submitting · case 02
The accepted event leaves a notification in succeeded instead of running.
Toast action request feedback: accepted from submitting · case 03
The accepted event leaves a notification in succeeded instead of running.
Toast action request feedback: accepted from submitting · case 04
The accepted event leaves a notification in succeeded instead of running.
Toast action request feedback: accepted from submitting · case 05
The accepted event leaves a notification in succeeded instead of running.
Toast action request feedback: completion from running · case 01
The completion event leaves a notification in ready instead of succeeded.
Toast action request feedback: completion from running · case 02
The completion event leaves a notification in ready instead of succeeded.
Toast action request feedback: completion from running · case 03
The completion event leaves a notification in ready instead of succeeded.
Toast action request feedback: completion from running · case 04
The completion event leaves a notification in ready instead of succeeded.
Toast action request feedback: completion from running · case 05
The completion event leaves a notification in ready instead of succeeded.
Toast action request feedback: rejection from running · case 01
The rejection event leaves a notification in succeeded instead of failed.
Toast action request feedback: rejection from running · case 02
The rejection event leaves a notification in succeeded instead of failed.
Toast action request feedback: rejection from running · case 03
The rejection event leaves a notification in succeeded instead of failed.
Toast action request feedback: rejection from running · case 04
The rejection event leaves a notification in succeeded instead of failed.
Toast action request feedback: rejection from running · case 05
The rejection event leaves a notification in succeeded instead of failed.
Toast action request feedback: retry-click from failed · case 01
The retry-click event leaves a notification in running instead of submitting.
Toast action request feedback: retry-click from failed · case 02
The retry-click event leaves a notification in running instead of submitting.
Toast action request feedback: retry-click from failed · case 03
The retry-click event leaves a notification in running instead of submitting.
Toast action request feedback: retry-click from failed · case 04
The retry-click event leaves a notification in running instead of submitting.
Toast action request feedback: retry-click from failed · case 05
The retry-click event leaves a notification in running instead of submitting.
Toast action request feedback: transport-unknown from submitting · case 01
The transport-unknown event leaves a notification in failed instead of uncertain.
Toast action request feedback: transport-unknown from submitting · case 02
The transport-unknown event leaves a notification in failed instead of uncertain.
Toast action request feedback: transport-unknown from submitting · case 03
The transport-unknown event leaves a notification in failed instead of uncertain.
Toast action request feedback: transport-unknown from submitting · case 04
The transport-unknown event leaves a notification in failed instead of uncertain.
Toast action request feedback: transport-unknown from submitting · case 05
The transport-unknown event leaves a notification in failed instead of uncertain.
Toast action request feedback: status-confirmed-running from uncertain · case 01
The status-confirmed-running event leaves a notification in submitting instead of running.
Toast action request feedback: status-confirmed-running from uncertain · case 02
The status-confirmed-running event leaves a notification in submitting instead of running.
Toast action request feedback: status-confirmed-running from uncertain · case 03
The status-confirmed-running event leaves a notification in submitting instead of running.
Toast action request feedback: status-confirmed-running from uncertain · case 04
The status-confirmed-running event leaves a notification in submitting instead of running.
Toast action request feedback: status-confirmed-running from uncertain · case 05
The status-confirmed-running event leaves a notification in submitting instead of running.
Toast action request feedback: status-confirmed-absent from uncertain · case 01
The status-confirmed-absent event leaves a notification in succeeded instead of ready.
Toast action request feedback: status-confirmed-absent from uncertain · case 02
The status-confirmed-absent event leaves a notification in succeeded instead of ready.
Toast action request feedback: status-confirmed-absent from uncertain · case 03
The status-confirmed-absent event leaves a notification in succeeded instead of ready.
Toast action request feedback: status-confirmed-absent from uncertain · case 04
The status-confirmed-absent event leaves a notification in succeeded instead of ready.
Toast action request feedback: status-confirmed-absent from uncertain · case 05
The status-confirmed-absent event leaves a notification in succeeded instead of ready.
Toast action request feedback: stale-rejection from succeeded · case 01
The stale-rejection event leaves a notification in failed instead of succeeded.
Toast action request feedback: stale-rejection from succeeded · case 02
The stale-rejection event leaves a notification in failed instead of succeeded.
Toast action request feedback: stale-rejection from succeeded · case 03
The stale-rejection event leaves a notification in failed instead of succeeded.
Toast action request feedback: stale-rejection from succeeded · case 04
The stale-rejection event leaves a notification in failed instead of succeeded.
Toast action request feedback: stale-rejection from succeeded · case 05
The stale-rejection event leaves a notification in failed instead of succeeded.
Inbox read receipt rendering: open-preview from unread · case 01
The open-preview event leaves a notification in read-confirmed instead of previewing.
Inbox read receipt rendering: open-preview from unread · case 02
The open-preview event leaves a notification in read-confirmed instead of previewing.
Inbox read receipt rendering: open-preview from unread · case 03
The open-preview event leaves a notification in read-confirmed instead of previewing.
Inbox read receipt rendering: open-preview from unread · case 04
The open-preview event leaves a notification in read-confirmed instead of previewing.
Inbox read receipt rendering: open-preview from unread · case 05
The open-preview event leaves a notification in read-confirmed instead of previewing.
Inbox read receipt rendering: close-preview from previewing · case 01
The close-preview event leaves a notification in read-confirmed instead of unread.
Inbox read receipt rendering: close-preview from previewing · case 02
The close-preview event leaves a notification in read-confirmed instead of unread.
Inbox read receipt rendering: close-preview from previewing · case 03
The close-preview event leaves a notification in read-confirmed instead of unread.
Inbox read receipt rendering: close-preview from previewing · case 04
The close-preview event leaves a notification in read-confirmed instead of unread.
Inbox read receipt rendering: close-preview from previewing · case 05
The close-preview event leaves a notification in read-confirmed instead of unread.
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 ↗