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 channel preference feedback: save-failure from disable-pending · case 01
The save-failure event leaves a notification in disabled instead of disable-error.
Notification channel preference feedback: save-failure from disable-pending · case 02
The save-failure event leaves a notification in disabled instead of disable-error.
Notification channel preference feedback: save-failure from disable-pending · case 03
The save-failure event leaves a notification in disabled instead of disable-error.
Notification channel preference feedback: save-failure from disable-pending · case 04
The save-failure event leaves a notification in disabled instead of disable-error.
Notification channel preference feedback: save-failure from disable-pending · case 05
The save-failure event leaves a notification in disabled instead of disable-error.
Notification channel preference feedback: enable-toggle from disabled · case 01
The enable-toggle event leaves a notification in enabled instead of enable-pending.
Notification channel preference feedback: enable-toggle from disabled · case 02
The enable-toggle event leaves a notification in enabled instead of enable-pending.
Notification channel preference feedback: enable-toggle from disabled · case 03
The enable-toggle event leaves a notification in enabled instead of enable-pending.
Notification channel preference feedback: enable-toggle from disabled · case 04
The enable-toggle event leaves a notification in enabled instead of enable-pending.
Notification channel preference feedback: enable-toggle from disabled · case 05
The enable-toggle event leaves a notification in enabled instead of enable-pending.
Notification channel preference feedback: save-success from enable-pending · case 01
The save-success event leaves a notification in disabled instead of enabled.
Notification channel preference feedback: save-success from enable-pending · case 02
The save-success event leaves a notification in disabled instead of enabled.
Notification channel preference feedback: save-success from enable-pending · case 03
The save-success event leaves a notification in disabled instead of enabled.
Notification channel preference feedback: save-success from enable-pending · case 04
The save-success event leaves a notification in disabled instead of enabled.
Notification channel preference feedback: save-success from enable-pending · case 05
The save-success event leaves a notification in disabled instead of enabled.
Notification channel preference feedback: save-failure from enable-pending · case 01
The save-failure event leaves a notification in enabled instead of enable-error.
Notification channel preference feedback: save-failure from enable-pending · case 02
The save-failure event leaves a notification in enabled instead of enable-error.
Notification channel preference feedback: save-failure from enable-pending · case 03
The save-failure event leaves a notification in enabled instead of enable-error.
Notification channel preference feedback: save-failure from enable-pending · case 04
The save-failure event leaves a notification in enabled instead of enable-error.
Notification channel preference feedback: save-failure from enable-pending · case 05
The save-failure event leaves a notification in enabled instead of enable-error.
Notification channel preference feedback: retry-disable from disable-error · case 01
The retry-disable event leaves a notification in disabled instead of disable-pending.
Notification channel preference feedback: retry-disable from disable-error · case 02
The retry-disable event leaves a notification in disabled instead of disable-pending.
Notification channel preference feedback: retry-disable from disable-error · case 03
The retry-disable event leaves a notification in disabled instead of disable-pending.
Notification channel preference feedback: retry-disable from disable-error · case 04
The retry-disable event leaves a notification in disabled instead of disable-pending.
Notification channel preference feedback: retry-disable from disable-error · case 05
The retry-disable event leaves a notification in disabled instead of disable-pending.
Notification channel preference feedback: retry-enable from enable-error · case 01
The retry-enable event leaves a notification in enabled instead of enable-pending.
Notification channel preference feedback: retry-enable from enable-error · case 02
The retry-enable event leaves a notification in enabled instead of enable-pending.
Notification channel preference feedback: retry-enable from enable-error · case 03
The retry-enable event leaves a notification in enabled instead of enable-pending.
Notification channel preference feedback: retry-enable from enable-error · case 04
The retry-enable event leaves a notification in enabled instead of enable-pending.
Notification channel preference feedback: retry-enable from enable-error · case 05
The retry-enable event leaves a notification in enabled instead of enable-pending.
Notification channel preference feedback: toggle-back-on from disable-pending · case 01
The toggle-back-on event leaves a notification in enabled instead of cancel-disable-pending.
Notification channel preference feedback: toggle-back-on from disable-pending · case 02
The toggle-back-on event leaves a notification in enabled instead of cancel-disable-pending.
Notification channel preference feedback: toggle-back-on from disable-pending · case 03
The toggle-back-on event leaves a notification in enabled instead of cancel-disable-pending.
Notification channel preference feedback: toggle-back-on from disable-pending · case 04
The toggle-back-on event leaves a notification in enabled instead of cancel-disable-pending.
Notification channel preference feedback: toggle-back-on from disable-pending · case 05
The toggle-back-on event leaves a notification in enabled instead of cancel-disable-pending.
Notification channel preference feedback: disable-save-completes from cancel-disable-pending · case 01
The disable-save-completes event leaves a notification in disabled instead of enable-pending.
Notification channel preference feedback: disable-save-completes from cancel-disable-pending · case 02
The disable-save-completes event leaves a notification in disabled instead of enable-pending.
Notification channel preference feedback: disable-save-completes from cancel-disable-pending · case 03
The disable-save-completes event leaves a notification in disabled instead of enable-pending.
Notification channel preference feedback: disable-save-completes from cancel-disable-pending · case 04
The disable-save-completes event leaves a notification in disabled instead of enable-pending.
Notification channel preference feedback: disable-save-completes from cancel-disable-pending · case 05
The disable-save-completes event leaves a notification in disabled instead of enable-pending.
Notification surface account switch: switch-to-b from account-a-visible · case 01
The switch-to-b event leaves a notification in account-b-loading instead of scrubbing-a.
Notification surface account switch: switch-to-b from account-a-visible · case 02
The switch-to-b event leaves a notification in account-b-loading instead of scrubbing-a.
Notification surface account switch: switch-to-b from account-a-visible · case 03
The switch-to-b event leaves a notification in account-b-loading instead of scrubbing-a.
Notification surface account switch: switch-to-b from account-a-visible · case 04
The switch-to-b event leaves a notification in account-b-loading instead of scrubbing-a.
Notification surface account switch: switch-to-b from account-a-visible · case 05
The switch-to-b event leaves a notification in account-b-loading instead of scrubbing-a.
Notification surface account switch: scrub-complete from scrubbing-a · case 01
The scrub-complete event leaves a notification in account-a-visible instead of account-b-loading.
Notification surface account switch: scrub-complete from scrubbing-a · case 02
The scrub-complete event leaves a notification in account-a-visible instead of account-b-loading.
Notification surface account switch: scrub-complete from scrubbing-a · case 03
The scrub-complete event leaves a notification in account-a-visible instead of account-b-loading.
Notification surface account switch: scrub-complete from scrubbing-a · case 04
The scrub-complete event leaves a notification in account-a-visible instead of account-b-loading.
Notification surface account switch: scrub-complete from scrubbing-a · case 05
The scrub-complete event leaves a notification in account-a-visible instead of account-b-loading.
Notification surface account switch: b-inbox-loaded from account-b-loading · case 01
The b-inbox-loaded event leaves a notification in account-a-visible instead of account-b-visible.
Notification surface account switch: b-inbox-loaded from account-b-loading · case 02
The b-inbox-loaded event leaves a notification in account-a-visible instead of account-b-visible.
Notification surface account switch: b-inbox-loaded from account-b-loading · case 03
The b-inbox-loaded event leaves a notification in account-a-visible instead of account-b-visible.
Notification surface account switch: b-inbox-loaded from account-b-loading · case 04
The b-inbox-loaded event leaves a notification in account-a-visible instead of account-b-visible.
Notification surface account switch: b-inbox-loaded from account-b-loading · case 05
The b-inbox-loaded event leaves a notification in account-a-visible instead of account-b-visible.
Notification surface account switch: b-inbox-failed from account-b-loading · case 01
The b-inbox-failed event leaves a notification in account-a-visible instead of switch-error.
Notification surface account switch: b-inbox-failed from account-b-loading · case 02
The b-inbox-failed event leaves a notification in account-a-visible instead of switch-error.
Notification surface account switch: b-inbox-failed from account-b-loading · case 03
The b-inbox-failed event leaves a notification in account-a-visible instead of switch-error.
Notification surface account switch: b-inbox-failed from account-b-loading · case 04
The b-inbox-failed event leaves a notification in account-a-visible instead of switch-error.
Notification surface account switch: b-inbox-failed from account-b-loading · case 05
The b-inbox-failed event leaves a notification in account-a-visible instead of switch-error.
Notification surface account switch: late-a-response from account-b-loading · case 01
The late-a-response event leaves a notification in account-a-visible instead of account-b-loading.
Notification surface account switch: late-a-response from account-b-loading · case 02
The late-a-response event leaves a notification in account-a-visible instead of account-b-loading.
Notification surface account switch: late-a-response from account-b-loading · case 03
The late-a-response event leaves a notification in account-a-visible instead of account-b-loading.
Notification surface account switch: late-a-response from account-b-loading · case 04
The late-a-response event leaves a notification in account-a-visible instead of account-b-loading.
Notification surface account switch: late-a-response from account-b-loading · case 05
The late-a-response event leaves a notification in account-a-visible instead of account-b-loading.
Notification surface account switch: retry-b-load from switch-error · case 01
The retry-b-load event leaves a notification in account-a-visible instead of account-b-loading.
Notification surface account switch: retry-b-load from switch-error · case 02
The retry-b-load event leaves a notification in account-a-visible instead of account-b-loading.
Notification surface account switch: retry-b-load from switch-error · case 03
The retry-b-load event leaves a notification in account-a-visible instead of account-b-loading.
Notification surface account switch: retry-b-load from switch-error · case 04
The retry-b-load event leaves a notification in account-a-visible instead of account-b-loading.
Notification surface account switch: retry-b-load from switch-error · case 05
The retry-b-load event leaves a notification in account-a-visible instead of account-b-loading.
Notification surface account switch: sign-out from account-b-visible · case 01
The sign-out event leaves a notification in signed-out instead of scrubbing-b.
Notification surface account switch: sign-out from account-b-visible · case 02
The sign-out event leaves a notification in signed-out instead of scrubbing-b.
Notification surface account switch: sign-out from account-b-visible · case 03
The sign-out event leaves a notification in signed-out instead of scrubbing-b.
Notification surface account switch: sign-out from account-b-visible · case 04
The sign-out event leaves a notification in signed-out instead of scrubbing-b.
Notification surface account switch: sign-out from account-b-visible · case 05
The sign-out event leaves a notification in signed-out instead of scrubbing-b.
Notification surface account switch: scrub-complete from scrubbing-b · case 01
The scrub-complete event leaves a notification in account-b-visible instead of signed-out.
Notification surface account switch: scrub-complete from scrubbing-b · case 02
The scrub-complete event leaves a notification in account-b-visible instead of signed-out.
Notification surface account switch: scrub-complete from scrubbing-b · case 03
The scrub-complete event leaves a notification in account-b-visible instead of signed-out.
Notification surface account switch: scrub-complete from scrubbing-b · case 04
The scrub-complete event leaves a notification in account-b-visible instead of signed-out.
Notification surface account switch: scrub-complete from scrubbing-b · case 05
The scrub-complete event leaves a notification in account-b-visible instead of signed-out.
Notification surface account switch: late-b-response from signed-out · case 01
The late-b-response event leaves a notification in account-b-visible instead of signed-out.
Notification surface account switch: late-b-response from signed-out · case 02
The late-b-response event leaves a notification in account-b-visible instead of signed-out.
Notification surface account switch: late-b-response from signed-out · case 03
The late-b-response event leaves a notification in account-b-visible instead of signed-out.
Notification surface account switch: late-b-response from signed-out · case 04
The late-b-response event leaves a notification in account-b-visible instead of signed-out.
Notification surface account switch: late-b-response from signed-out · case 05
The late-b-response event leaves a notification in account-b-visible instead of signed-out.
Notification surface account switch: switch-back-to-a from scrubbing-a · case 01
The switch-back-to-a event leaves a notification in account-a-visible instead of scrubbing-for-a.
Notification surface account switch: switch-back-to-a from scrubbing-a · case 02
The switch-back-to-a event leaves a notification in account-a-visible instead of scrubbing-for-a.
Notification surface account switch: switch-back-to-a from scrubbing-a · case 03
The switch-back-to-a event leaves a notification in account-a-visible instead of scrubbing-for-a.
Notification surface account switch: switch-back-to-a from scrubbing-a · case 04
The switch-back-to-a event leaves a notification in account-a-visible instead of scrubbing-for-a.
Notification surface account switch: switch-back-to-a from scrubbing-a · case 05
The switch-back-to-a event leaves a notification in account-a-visible instead of scrubbing-for-a.
Inbox notification pin persistence: pin-click from unpinned · case 01
The pin-click event leaves a notification in pinned instead of pin-pending.
Inbox notification pin persistence: pin-click from unpinned · case 02
The pin-click event leaves a notification in pinned instead of pin-pending.
Inbox notification pin persistence: pin-click from unpinned · case 03
The pin-click event leaves a notification in pinned instead of pin-pending.
Inbox notification pin persistence: pin-click from unpinned · case 04
The pin-click event leaves a notification in pinned instead of pin-pending.
Inbox notification pin persistence: pin-click from unpinned · case 05
The pin-click event leaves a notification in pinned instead of pin-pending.
Inbox notification pin persistence: pin-success from pin-pending · case 01
The pin-success event leaves a notification in unpinned instead of pinned.
Inbox notification pin persistence: pin-success from pin-pending · case 02
The pin-success event leaves a notification in unpinned instead of pinned.
Inbox notification pin persistence: pin-success from pin-pending · case 03
The pin-success event leaves a notification in unpinned instead of pinned.
Inbox notification pin persistence: pin-success from pin-pending · case 04
The pin-success event leaves a notification in unpinned instead of pinned.
Inbox notification pin persistence: pin-success from pin-pending · case 05
The pin-success event leaves a notification in unpinned instead of pinned.
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 ↗