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 inbox reconnect recovery: snapshot-current from reconciling · case 01
The snapshot-current event leaves a notification in offline-cached instead of live.
Notification inbox reconnect recovery: snapshot-current from reconciling · case 02
The snapshot-current event leaves a notification in offline-cached instead of live.
Notification inbox reconnect recovery: snapshot-current from reconciling · case 03
The snapshot-current event leaves a notification in offline-cached instead of live.
Notification inbox reconnect recovery: snapshot-current from reconciling · case 04
The snapshot-current event leaves a notification in offline-cached instead of live.
Notification inbox reconnect recovery: snapshot-current from reconciling · case 05
The snapshot-current event leaves a notification in offline-cached instead of live.
Notification inbox reconnect recovery: snapshot-failed from reconciling · case 01
The snapshot-failed event leaves a notification in live instead of offline-error.
Notification inbox reconnect recovery: snapshot-failed from reconciling · case 02
The snapshot-failed event leaves a notification in live instead of offline-error.
Notification inbox reconnect recovery: snapshot-failed from reconciling · case 03
The snapshot-failed event leaves a notification in live instead of offline-error.
Notification inbox reconnect recovery: snapshot-failed from reconciling · case 04
The snapshot-failed event leaves a notification in live instead of offline-error.
Notification inbox reconnect recovery: snapshot-failed from reconciling · case 05
The snapshot-failed event leaves a notification in live instead of offline-error.
Notification inbox reconnect recovery: retry-refresh from offline-error · case 01
The retry-refresh event leaves a notification in live instead of reconciling.
Notification inbox reconnect recovery: retry-refresh from offline-error · case 02
The retry-refresh event leaves a notification in live instead of reconciling.
Notification inbox reconnect recovery: retry-refresh from offline-error · case 03
The retry-refresh event leaves a notification in live instead of reconciling.
Notification inbox reconnect recovery: retry-refresh from offline-error · case 04
The retry-refresh event leaves a notification in live instead of reconciling.
Notification inbox reconnect recovery: retry-refresh from offline-error · case 05
The retry-refresh event leaves a notification in live instead of reconciling.
Notification inbox reconnect recovery: connection-lost from reconciling · case 01
The connection-lost event leaves a notification in live instead of offline-cached.
Notification inbox reconnect recovery: connection-lost from reconciling · case 02
The connection-lost event leaves a notification in live instead of offline-cached.
Notification inbox reconnect recovery: connection-lost from reconciling · case 03
The connection-lost event leaves a notification in live instead of offline-cached.
Notification inbox reconnect recovery: connection-lost from reconciling · case 04
The connection-lost event leaves a notification in live instead of offline-cached.
Notification inbox reconnect recovery: connection-lost from reconciling · case 05
The connection-lost event leaves a notification in live instead of offline-cached.
Notification inbox reconnect recovery: open-cached-item from offline-cached · case 01
The open-cached-item event leaves a notification in live instead of offline-preview.
Notification inbox reconnect recovery: open-cached-item from offline-cached · case 02
The open-cached-item event leaves a notification in live instead of offline-preview.
Notification inbox reconnect recovery: open-cached-item from offline-cached · case 03
The open-cached-item event leaves a notification in live instead of offline-preview.
Notification inbox reconnect recovery: open-cached-item from offline-cached · case 04
The open-cached-item event leaves a notification in live instead of offline-preview.
Notification inbox reconnect recovery: open-cached-item from offline-cached · case 05
The open-cached-item event leaves a notification in live instead of offline-preview.
Notification inbox reconnect recovery: close-preview from offline-preview · case 01
The close-preview event leaves a notification in live instead of offline-cached.
Notification inbox reconnect recovery: close-preview from offline-preview · case 02
The close-preview event leaves a notification in live instead of offline-cached.
Notification inbox reconnect recovery: close-preview from offline-preview · case 03
The close-preview event leaves a notification in live instead of offline-cached.
Notification inbox reconnect recovery: close-preview from offline-preview · case 04
The close-preview event leaves a notification in live instead of offline-cached.
Notification inbox reconnect recovery: close-preview from offline-preview · case 05
The close-preview event leaves a notification in live instead of offline-cached.
Notification inbox reconnect recovery: connection-restored from offline-preview · case 01
The connection-restored event leaves a notification in live instead of reconciling-preview.
Notification inbox reconnect recovery: connection-restored from offline-preview · case 02
The connection-restored event leaves a notification in live instead of reconciling-preview.
Notification inbox reconnect recovery: connection-restored from offline-preview · case 03
The connection-restored event leaves a notification in live instead of reconciling-preview.
Notification inbox reconnect recovery: connection-restored from offline-preview · case 04
The connection-restored event leaves a notification in live instead of reconciling-preview.
Notification inbox reconnect recovery: connection-restored from offline-preview · case 05
The connection-restored event leaves a notification in live instead of reconciling-preview.
Notification inbox reconnect recovery: snapshot-current from reconciling-preview · case 01
The snapshot-current event leaves a notification in live instead of live-preview.
Notification inbox reconnect recovery: snapshot-current from reconciling-preview · case 02
The snapshot-current event leaves a notification in live instead of live-preview.
Notification inbox reconnect recovery: snapshot-current from reconciling-preview · case 03
The snapshot-current event leaves a notification in live instead of live-preview.
Notification inbox reconnect recovery: snapshot-current from reconciling-preview · case 04
The snapshot-current event leaves a notification in live instead of live-preview.
Notification inbox reconnect recovery: snapshot-current from reconciling-preview · case 05
The snapshot-current event leaves a notification in live instead of live-preview.
Single-surface notification display ownership: request-display from standby · case 01
The request-display event leaves a notification in displaying instead of claiming.
Single-surface notification display ownership: request-display from standby · case 02
The request-display event leaves a notification in displaying instead of claiming.
Single-surface notification display ownership: request-display from standby · case 03
The request-display event leaves a notification in displaying instead of claiming.
Single-surface notification display ownership: request-display from standby · case 04
The request-display event leaves a notification in displaying instead of claiming.
Single-surface notification display ownership: request-display from standby · case 05
The request-display event leaves a notification in displaying instead of claiming.
Single-surface notification display ownership: lease-granted from claiming · case 01
The lease-granted event leaves a notification in standby instead of displaying.
Single-surface notification display ownership: lease-granted from claiming · case 02
The lease-granted event leaves a notification in standby instead of displaying.
Single-surface notification display ownership: lease-granted from claiming · case 03
The lease-granted event leaves a notification in standby instead of displaying.
Single-surface notification display ownership: lease-granted from claiming · case 04
The lease-granted event leaves a notification in standby instead of displaying.
Single-surface notification display ownership: lease-granted from claiming · case 05
The lease-granted event leaves a notification in standby instead of displaying.
Single-surface notification display ownership: lease-denied from claiming · case 01
The lease-denied event leaves a notification in displaying instead of standby.
Single-surface notification display ownership: lease-denied from claiming · case 02
The lease-denied event leaves a notification in displaying instead of standby.
Single-surface notification display ownership: lease-denied from claiming · case 03
The lease-denied event leaves a notification in displaying instead of standby.
Single-surface notification display ownership: lease-denied from claiming · case 04
The lease-denied event leaves a notification in displaying instead of standby.
Single-surface notification display ownership: lease-denied from claiming · case 05
The lease-denied event leaves a notification in displaying instead of standby.
Single-surface notification display ownership: lease-revoked from displaying · case 01
The lease-revoked event leaves a notification in displaying instead of withdrawing.
Single-surface notification display ownership: lease-revoked from displaying · case 02
The lease-revoked event leaves a notification in displaying instead of withdrawing.
Single-surface notification display ownership: lease-revoked from displaying · case 03
The lease-revoked event leaves a notification in displaying instead of withdrawing.
Single-surface notification display ownership: lease-revoked from displaying · case 04
The lease-revoked event leaves a notification in displaying instead of withdrawing.
Single-surface notification display ownership: lease-revoked from displaying · case 05
The lease-revoked event leaves a notification in displaying instead of withdrawing.
Single-surface notification display ownership: unmounted from withdrawing · case 01
The unmounted event leaves a notification in displaying instead of standby.
Single-surface notification display ownership: unmounted from withdrawing · case 02
The unmounted event leaves a notification in displaying instead of standby.
Single-surface notification display ownership: unmounted from withdrawing · case 03
The unmounted event leaves a notification in displaying instead of standby.
Single-surface notification display ownership: unmounted from withdrawing · case 04
The unmounted event leaves a notification in displaying instead of standby.
Single-surface notification display ownership: unmounted from withdrawing · case 05
The unmounted event leaves a notification in displaying instead of standby.
Single-surface notification display ownership: close-surface from displaying · case 01
The close-surface event leaves a notification in standby instead of releasing.
Single-surface notification display ownership: close-surface from displaying · case 02
The close-surface event leaves a notification in standby instead of releasing.
Single-surface notification display ownership: close-surface from displaying · case 03
The close-surface event leaves a notification in standby instead of releasing.
Single-surface notification display ownership: close-surface from displaying · case 04
The close-surface event leaves a notification in standby instead of releasing.
Single-surface notification display ownership: close-surface from displaying · case 05
The close-surface event leaves a notification in standby instead of releasing.
Single-surface notification display ownership: release-confirmed from releasing · case 01
The release-confirmed event leaves a notification in displaying instead of standby.
Single-surface notification display ownership: release-confirmed from releasing · case 02
The release-confirmed event leaves a notification in displaying instead of standby.
Single-surface notification display ownership: release-confirmed from releasing · case 03
The release-confirmed event leaves a notification in displaying instead of standby.
Single-surface notification display ownership: release-confirmed from releasing · case 04
The release-confirmed event leaves a notification in displaying instead of standby.
Single-surface notification display ownership: release-confirmed from releasing · case 05
The release-confirmed event leaves a notification in displaying instead of standby.
Single-surface notification display ownership: cancel-display from claiming · case 01
The cancel-display event leaves a notification in standby instead of claim-canceled.
Single-surface notification display ownership: cancel-display from claiming · case 02
The cancel-display event leaves a notification in standby instead of claim-canceled.
Single-surface notification display ownership: cancel-display from claiming · case 03
The cancel-display event leaves a notification in standby instead of claim-canceled.
Single-surface notification display ownership: cancel-display from claiming · case 04
The cancel-display event leaves a notification in standby instead of claim-canceled.
Single-surface notification display ownership: cancel-display from claiming · case 05
The cancel-display event leaves a notification in standby instead of claim-canceled.
Single-surface notification display ownership: late-lease-granted from claim-canceled · case 01
The late-lease-granted event leaves a notification in displaying instead of releasing.
Single-surface notification display ownership: late-lease-granted from claim-canceled · case 02
The late-lease-granted event leaves a notification in displaying instead of releasing.
Single-surface notification display ownership: late-lease-granted from claim-canceled · case 03
The late-lease-granted event leaves a notification in displaying instead of releasing.
Single-surface notification display ownership: late-lease-granted from claim-canceled · case 04
The late-lease-granted event leaves a notification in displaying instead of releasing.
Single-surface notification display ownership: late-lease-granted from claim-canceled · case 05
The late-lease-granted event leaves a notification in displaying instead of releasing.
Single-surface notification display ownership: foreign-release from standby · case 01
The foreign-release event leaves a notification in displaying instead of standby.
Single-surface notification display ownership: foreign-release from standby · case 02
The foreign-release event leaves a notification in displaying instead of standby.
Single-surface notification display ownership: foreign-release from standby · case 03
The foreign-release event leaves a notification in displaying instead of standby.
Single-surface notification display ownership: foreign-release from standby · case 04
The foreign-release event leaves a notification in displaying instead of standby.
Single-surface notification display ownership: foreign-release from standby · case 05
The foreign-release event leaves a notification in displaying instead of standby.
Notification digest assembly presentation: close-window from collecting · case 01
The close-window event leaves a notification in published instead of sealing.
Notification digest assembly presentation: close-window from collecting · case 02
The close-window event leaves a notification in published instead of sealing.
Notification digest assembly presentation: close-window from collecting · case 03
The close-window event leaves a notification in published instead of sealing.
Notification digest assembly presentation: close-window from collecting · case 04
The close-window event leaves a notification in published instead of sealing.
Notification digest assembly presentation: close-window from collecting · case 05
The close-window event leaves a notification in published instead of sealing.
Notification digest assembly presentation: seal-success from sealing · case 01
The seal-success event leaves a notification in published instead of ready.
Notification digest assembly presentation: seal-success from sealing · case 02
The seal-success event leaves a notification in published instead of ready.
Notification digest assembly presentation: seal-success from sealing · case 03
The seal-success event leaves a notification in published instead of ready.
Notification digest assembly presentation: seal-success from sealing · case 04
The seal-success event leaves a notification in published instead of ready.
Notification digest assembly presentation: seal-success from sealing · case 05
The seal-success event leaves a notification in published instead of ready.
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 ↗