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
Inbox optimistic archive rollback: archive-failure from optimistically-hidden · case 01
The archive-failure event leaves a notification in archived instead of restored-error.
Inbox optimistic archive rollback: archive-failure from optimistically-hidden · case 02
The archive-failure event leaves a notification in archived instead of restored-error.
Inbox optimistic archive rollback: archive-failure from optimistically-hidden · case 03
The archive-failure event leaves a notification in archived instead of restored-error.
Inbox optimistic archive rollback: archive-failure from optimistically-hidden · case 04
The archive-failure event leaves a notification in archived instead of restored-error.
Inbox optimistic archive rollback: archive-failure from optimistically-hidden · case 05
The archive-failure event leaves a notification in archived instead of restored-error.
Inbox optimistic archive rollback: retry-archive from restored-error · case 01
The retry-archive event leaves a notification in archived instead of optimistically-hidden.
Inbox optimistic archive rollback: retry-archive from restored-error · case 02
The retry-archive event leaves a notification in archived instead of optimistically-hidden.
Inbox optimistic archive rollback: retry-archive from restored-error · case 03
The retry-archive event leaves a notification in archived instead of optimistically-hidden.
Inbox optimistic archive rollback: retry-archive from restored-error · case 04
The retry-archive event leaves a notification in archived instead of optimistically-hidden.
Inbox optimistic archive rollback: retry-archive from restored-error · case 05
The retry-archive event leaves a notification in archived instead of optimistically-hidden.
Inbox optimistic archive rollback: restore-click from archived · case 01
The restore-click event leaves a notification in row-visible instead of restoring.
Inbox optimistic archive rollback: restore-click from archived · case 02
The restore-click event leaves a notification in row-visible instead of restoring.
Inbox optimistic archive rollback: restore-click from archived · case 03
The restore-click event leaves a notification in row-visible instead of restoring.
Inbox optimistic archive rollback: restore-click from archived · case 04
The restore-click event leaves a notification in row-visible instead of restoring.
Inbox optimistic archive rollback: restore-click from archived · case 05
The restore-click event leaves a notification in row-visible instead of restoring.
Inbox optimistic archive rollback: restore-success from restoring · case 01
The restore-success event leaves a notification in archived instead of row-visible.
Inbox optimistic archive rollback: restore-success from restoring · case 02
The restore-success event leaves a notification in archived instead of row-visible.
Inbox optimistic archive rollback: restore-success from restoring · case 03
The restore-success event leaves a notification in archived instead of row-visible.
Inbox optimistic archive rollback: restore-success from restoring · case 04
The restore-success event leaves a notification in archived instead of row-visible.
Inbox optimistic archive rollback: restore-success from restoring · case 05
The restore-success event leaves a notification in archived instead of row-visible.
Inbox optimistic archive rollback: restore-failure from restoring · case 01
The restore-failure event leaves a notification in row-visible instead of restore-error.
Inbox optimistic archive rollback: restore-failure from restoring · case 02
The restore-failure event leaves a notification in row-visible instead of restore-error.
Inbox optimistic archive rollback: restore-failure from restoring · case 03
The restore-failure event leaves a notification in row-visible instead of restore-error.
Inbox optimistic archive rollback: restore-failure from restoring · case 04
The restore-failure event leaves a notification in row-visible instead of restore-error.
Inbox optimistic archive rollback: restore-failure from restoring · case 05
The restore-failure event leaves a notification in row-visible instead of restore-error.
Inbox optimistic archive rollback: retry-restore from restore-error · case 01
The retry-restore event leaves a notification in row-visible instead of restoring.
Inbox optimistic archive rollback: retry-restore from restore-error · case 02
The retry-restore event leaves a notification in row-visible instead of restoring.
Inbox optimistic archive rollback: retry-restore from restore-error · case 03
The retry-restore event leaves a notification in row-visible instead of restoring.
Inbox optimistic archive rollback: retry-restore from restore-error · case 04
The retry-restore event leaves a notification in row-visible instead of restoring.
Inbox optimistic archive rollback: retry-restore from restore-error · case 05
The retry-restore event leaves a notification in row-visible instead of restoring.
Inbox optimistic archive rollback: new-revision-arrives from optimistically-hidden · case 01
The new-revision-arrives event leaves a notification in row-visible instead of hidden-new-revision.
Inbox optimistic archive rollback: new-revision-arrives from optimistically-hidden · case 02
The new-revision-arrives event leaves a notification in row-visible instead of hidden-new-revision.
Inbox optimistic archive rollback: new-revision-arrives from optimistically-hidden · case 03
The new-revision-arrives event leaves a notification in row-visible instead of hidden-new-revision.
Inbox optimistic archive rollback: new-revision-arrives from optimistically-hidden · case 04
The new-revision-arrives event leaves a notification in row-visible instead of hidden-new-revision.
Inbox optimistic archive rollback: new-revision-arrives from optimistically-hidden · case 05
The new-revision-arrives event leaves a notification in row-visible instead of hidden-new-revision.
Inbox optimistic archive rollback: archive-failure from hidden-new-revision · case 01
The archive-failure event leaves a notification in restored-error instead of restored-new-revision-error.
Inbox optimistic archive rollback: archive-failure from hidden-new-revision · case 02
The archive-failure event leaves a notification in restored-error instead of restored-new-revision-error.
Inbox optimistic archive rollback: archive-failure from hidden-new-revision · case 03
The archive-failure event leaves a notification in restored-error instead of restored-new-revision-error.
Inbox optimistic archive rollback: archive-failure from hidden-new-revision · case 04
The archive-failure event leaves a notification in restored-error instead of restored-new-revision-error.
Inbox optimistic archive rollback: archive-failure from hidden-new-revision · case 05
The archive-failure event leaves a notification in restored-error instead of restored-new-revision-error.
Notification severity escalation acknowledgement: warning-arrives from informational · case 01
The warning-arrives event leaves a notification in informational instead of warning-unacknowledged.
Notification severity escalation acknowledgement: warning-arrives from informational · case 02
The warning-arrives event leaves a notification in informational instead of warning-unacknowledged.
Notification severity escalation acknowledgement: warning-arrives from informational · case 03
The warning-arrives event leaves a notification in informational instead of warning-unacknowledged.
Notification severity escalation acknowledgement: warning-arrives from informational · case 04
The warning-arrives event leaves a notification in informational instead of warning-unacknowledged.
Notification severity escalation acknowledgement: warning-arrives from informational · case 05
The warning-arrives event leaves a notification in informational instead of warning-unacknowledged.
Notification severity escalation acknowledgement: ack-warning from warning-unacknowledged · case 01
The ack-warning event leaves a notification in informational instead of warning-acknowledged.
Notification severity escalation acknowledgement: ack-warning from warning-unacknowledged · case 02
The ack-warning event leaves a notification in informational instead of warning-acknowledged.
Notification severity escalation acknowledgement: ack-warning from warning-unacknowledged · case 03
The ack-warning event leaves a notification in informational instead of warning-acknowledged.
Notification severity escalation acknowledgement: ack-warning from warning-unacknowledged · case 04
The ack-warning event leaves a notification in informational instead of warning-acknowledged.
Notification severity escalation acknowledgement: ack-warning from warning-unacknowledged · case 05
The ack-warning event leaves a notification in informational instead of warning-acknowledged.
Notification severity escalation acknowledgement: critical-arrives from warning-acknowledged · case 01
The critical-arrives event leaves a notification in warning-acknowledged instead of critical-unacknowledged.
Notification severity escalation acknowledgement: critical-arrives from warning-acknowledged · case 02
The critical-arrives event leaves a notification in warning-acknowledged instead of critical-unacknowledged.
Notification severity escalation acknowledgement: critical-arrives from warning-acknowledged · case 03
The critical-arrives event leaves a notification in warning-acknowledged instead of critical-unacknowledged.
Notification severity escalation acknowledgement: critical-arrives from warning-acknowledged · case 04
The critical-arrives event leaves a notification in warning-acknowledged instead of critical-unacknowledged.
Notification severity escalation acknowledgement: critical-arrives from warning-acknowledged · case 05
The critical-arrives event leaves a notification in warning-acknowledged instead of critical-unacknowledged.
Notification severity escalation acknowledgement: ack-critical from critical-unacknowledged · case 01
The ack-critical event leaves a notification in warning-acknowledged instead of critical-acknowledged.
Notification severity escalation acknowledgement: ack-critical from critical-unacknowledged · case 02
The ack-critical event leaves a notification in warning-acknowledged instead of critical-acknowledged.
Notification severity escalation acknowledgement: ack-critical from critical-unacknowledged · case 03
The ack-critical event leaves a notification in warning-acknowledged instead of critical-acknowledged.
Notification severity escalation acknowledgement: ack-critical from critical-unacknowledged · case 04
The ack-critical event leaves a notification in warning-acknowledged instead of critical-acknowledged.
Notification severity escalation acknowledgement: ack-critical from critical-unacknowledged · case 05
The ack-critical event leaves a notification in warning-acknowledged instead of critical-acknowledged.
Notification severity escalation acknowledgement: warning-arrives from critical-acknowledged · case 01
The warning-arrives event leaves a notification in warning-acknowledged instead of critical-acknowledged.
Notification severity escalation acknowledgement: warning-arrives from critical-acknowledged · case 02
The warning-arrives event leaves a notification in warning-acknowledged instead of critical-acknowledged.
Notification severity escalation acknowledgement: warning-arrives from critical-acknowledged · case 03
The warning-arrives event leaves a notification in warning-acknowledged instead of critical-acknowledged.
Notification severity escalation acknowledgement: warning-arrives from critical-acknowledged · case 04
The warning-arrives event leaves a notification in warning-acknowledged instead of critical-acknowledged.
Notification severity escalation acknowledgement: warning-arrives from critical-acknowledged · case 05
The warning-arrives event leaves a notification in warning-acknowledged instead of critical-acknowledged.
Notification severity escalation acknowledgement: condition-cleared from critical-unacknowledged · case 01
The condition-cleared event leaves a notification in resolved instead of resolved-unread.
Notification severity escalation acknowledgement: condition-cleared from critical-unacknowledged · case 02
The condition-cleared event leaves a notification in resolved instead of resolved-unread.
Notification severity escalation acknowledgement: condition-cleared from critical-unacknowledged · case 03
The condition-cleared event leaves a notification in resolved instead of resolved-unread.
Notification severity escalation acknowledgement: condition-cleared from critical-unacknowledged · case 04
The condition-cleared event leaves a notification in resolved instead of resolved-unread.
Notification severity escalation acknowledgement: condition-cleared from critical-unacknowledged · case 05
The condition-cleared event leaves a notification in resolved instead of resolved-unread.
Notification severity escalation acknowledgement: condition-cleared from critical-acknowledged · case 01
The condition-cleared event leaves a notification in critical-acknowledged instead of resolved.
Notification severity escalation acknowledgement: condition-cleared from critical-acknowledged · case 02
The condition-cleared event leaves a notification in critical-acknowledged instead of resolved.
Notification severity escalation acknowledgement: condition-cleared from critical-acknowledged · case 03
The condition-cleared event leaves a notification in critical-acknowledged instead of resolved.
Notification severity escalation acknowledgement: condition-cleared from critical-acknowledged · case 04
The condition-cleared event leaves a notification in critical-acknowledged instead of resolved.
Notification severity escalation acknowledgement: condition-cleared from critical-acknowledged · case 05
The condition-cleared event leaves a notification in critical-acknowledged instead of resolved.
Notification severity escalation acknowledgement: open-resolution from resolved-unread · case 01
The open-resolution event leaves a notification in critical-acknowledged instead of resolved.
Notification severity escalation acknowledgement: open-resolution from resolved-unread · case 02
The open-resolution event leaves a notification in critical-acknowledged instead of resolved.
Notification severity escalation acknowledgement: open-resolution from resolved-unread · case 03
The open-resolution event leaves a notification in critical-acknowledged instead of resolved.
Notification severity escalation acknowledgement: open-resolution from resolved-unread · case 04
The open-resolution event leaves a notification in critical-acknowledged instead of resolved.
Notification severity escalation acknowledgement: open-resolution from resolved-unread · case 05
The open-resolution event leaves a notification in critical-acknowledged instead of resolved.
Notification severity escalation acknowledgement: recurrence from resolved · case 01
The recurrence event leaves a notification in warning-acknowledged instead of warning-unacknowledged.
Notification severity escalation acknowledgement: recurrence from resolved · case 02
The recurrence event leaves a notification in warning-acknowledged instead of warning-unacknowledged.
Notification severity escalation acknowledgement: recurrence from resolved · case 03
The recurrence event leaves a notification in warning-acknowledged instead of warning-unacknowledged.
Notification severity escalation acknowledgement: recurrence from resolved · case 04
The recurrence event leaves a notification in warning-acknowledged instead of warning-unacknowledged.
Notification severity escalation acknowledgement: recurrence from resolved · case 05
The recurrence event leaves a notification in warning-acknowledged instead of warning-unacknowledged.
Notification severity escalation acknowledgement: critical-arrives from warning-unacknowledged · case 01
The critical-arrives event leaves a notification in warning-unacknowledged instead of critical-unacknowledged.
Notification severity escalation acknowledgement: critical-arrives from warning-unacknowledged · case 02
The critical-arrives event leaves a notification in warning-unacknowledged instead of critical-unacknowledged.
Notification severity escalation acknowledgement: critical-arrives from warning-unacknowledged · case 03
The critical-arrives event leaves a notification in warning-unacknowledged instead of critical-unacknowledged.
Notification severity escalation acknowledgement: critical-arrives from warning-unacknowledged · case 04
The critical-arrives event leaves a notification in warning-unacknowledged instead of critical-unacknowledged.
Notification severity escalation acknowledgement: critical-arrives from warning-unacknowledged · case 05
The critical-arrives event leaves a notification in warning-unacknowledged instead of critical-unacknowledged.
Notification channel preference feedback: disable-toggle from enabled · case 01
The disable-toggle event leaves a notification in disabled instead of disable-pending.
Notification channel preference feedback: disable-toggle from enabled · case 02
The disable-toggle event leaves a notification in disabled instead of disable-pending.
Notification channel preference feedback: disable-toggle from enabled · case 03
The disable-toggle event leaves a notification in disabled instead of disable-pending.
Notification channel preference feedback: disable-toggle from enabled · case 04
The disable-toggle event leaves a notification in disabled instead of disable-pending.
Notification channel preference feedback: disable-toggle from enabled · case 05
The disable-toggle event leaves a notification in disabled instead of disable-pending.
Notification channel preference feedback: save-success from disable-pending · case 01
The save-success event leaves a notification in enabled instead of disabled.
Notification channel preference feedback: save-success from disable-pending · case 02
The save-success event leaves a notification in enabled instead of disabled.
Notification channel preference feedback: save-success from disable-pending · case 03
The save-success event leaves a notification in enabled instead of disabled.
Notification channel preference feedback: save-success from disable-pending · case 04
The save-success event leaves a notification in enabled instead of disabled.
Notification channel preference feedback: save-success from disable-pending · case 05
The save-success event leaves a notification in enabled instead of disabled.
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 ↗