FAILURE MAP

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 ↗
100840Executable case variants
20168Distinct failure mechanisms
302520Executed implementations
20168Open-access cases

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

Python · Standard library
REFERENCEFAILURE MECHANISMDOMAINACCESS
FA-35001

Notification target opening feedback: navigation-complete from navigating · case 01

The navigation-complete event leaves a notification in actionable instead of opened.

Notification interfaces● Open access↗
FA-35002

Notification target opening feedback: navigation-complete from navigating · case 02

The navigation-complete event leaves a notification in actionable instead of opened.

Notification interfaces◈ Members↗
FA-35003

Notification target opening feedback: navigation-complete from navigating · case 03

The navigation-complete event leaves a notification in actionable instead of opened.

Notification interfaces◈ Members↗
FA-35004

Notification target opening feedback: navigation-complete from navigating · case 04

The navigation-complete event leaves a notification in actionable instead of opened.

Notification interfaces◈ Members↗
FA-35005

Notification target opening feedback: navigation-complete from navigating · case 05

The navigation-complete event leaves a notification in actionable instead of opened.

Notification interfaces◈ Members↗
FA-35006

Notification target opening feedback: target-deleted from resolving · case 01

The target-deleted event leaves a notification in navigating instead of unavailable.

Notification interfaces● Open access↗
FA-35007

Notification target opening feedback: target-deleted from resolving · case 02

The target-deleted event leaves a notification in navigating instead of unavailable.

Notification interfaces◈ Members↗
FA-35008

Notification target opening feedback: target-deleted from resolving · case 03

The target-deleted event leaves a notification in navigating instead of unavailable.

Notification interfaces◈ Members↗
FA-35009

Notification target opening feedback: target-deleted from resolving · case 04

The target-deleted event leaves a notification in navigating instead of unavailable.

Notification interfaces◈ Members↗
FA-35010

Notification target opening feedback: target-deleted from resolving · case 05

The target-deleted event leaves a notification in navigating instead of unavailable.

Notification interfaces◈ Members↗
FA-35011

Notification target opening feedback: access-required from resolving · case 01

The access-required event leaves a notification in unavailable instead of permission-needed.

Notification interfaces● Open access↗
FA-35012

Notification target opening feedback: access-required from resolving · case 02

The access-required event leaves a notification in unavailable instead of permission-needed.

Notification interfaces◈ Members↗
FA-35013

Notification target opening feedback: access-required from resolving · case 03

The access-required event leaves a notification in unavailable instead of permission-needed.

Notification interfaces◈ Members↗
FA-35014

Notification target opening feedback: access-required from resolving · case 04

The access-required event leaves a notification in unavailable instead of permission-needed.

Notification interfaces◈ Members↗
FA-35015

Notification target opening feedback: access-required from resolving · case 05

The access-required event leaves a notification in unavailable instead of permission-needed.

Notification interfaces◈ Members↗
FA-35016

Notification target opening feedback: request-access from permission-needed · case 01

The request-access event leaves a notification in opened instead of access-pending.

Notification interfaces● Open access↗
FA-35017

Notification target opening feedback: request-access from permission-needed · case 02

The request-access event leaves a notification in opened instead of access-pending.

Notification interfaces◈ Members↗
FA-35018

Notification target opening feedback: request-access from permission-needed · case 03

The request-access event leaves a notification in opened instead of access-pending.

Notification interfaces◈ Members↗
FA-35019

Notification target opening feedback: request-access from permission-needed · case 04

The request-access event leaves a notification in opened instead of access-pending.

Notification interfaces◈ Members↗
FA-35020

Notification target opening feedback: request-access from permission-needed · case 05

The request-access event leaves a notification in opened instead of access-pending.

Notification interfaces◈ Members↗
FA-35021

Notification target opening feedback: access-granted from access-pending · case 01

The access-granted event leaves a notification in opened instead of resolving.

Notification interfaces● Open access↗
FA-35022

Notification target opening feedback: access-granted from access-pending · case 02

The access-granted event leaves a notification in opened instead of resolving.

Notification interfaces◈ Members↗
FA-35023

Notification target opening feedback: access-granted from access-pending · case 03

The access-granted event leaves a notification in opened instead of resolving.

Notification interfaces◈ Members↗
FA-35024

Notification target opening feedback: access-granted from access-pending · case 04

The access-granted event leaves a notification in opened instead of resolving.

Notification interfaces◈ Members↗
FA-35025

Notification target opening feedback: access-granted from access-pending · case 05

The access-granted event leaves a notification in opened instead of resolving.

Notification interfaces◈ Members↗
FA-35026

Notification target opening feedback: navigation-failed from navigating · case 01

The navigation-failed event leaves a notification in opened instead of navigation-error.

Notification interfaces● Open access↗
FA-35027

Notification target opening feedback: navigation-failed from navigating · case 02

The navigation-failed event leaves a notification in opened instead of navigation-error.

Notification interfaces◈ Members↗
FA-35028

Notification target opening feedback: navigation-failed from navigating · case 03

The navigation-failed event leaves a notification in opened instead of navigation-error.

Notification interfaces◈ Members↗
FA-35029

Notification target opening feedback: navigation-failed from navigating · case 04

The navigation-failed event leaves a notification in opened instead of navigation-error.

Notification interfaces◈ Members↗
FA-35030

Notification target opening feedback: navigation-failed from navigating · case 05

The navigation-failed event leaves a notification in opened instead of navigation-error.

Notification interfaces◈ Members↗
FA-35031

Notification target opening feedback: retry-navigation from navigation-error · case 01

The retry-navigation event leaves a notification in opened instead of navigating.

Notification interfaces● Open access↗
FA-35032

Notification target opening feedback: retry-navigation from navigation-error · case 02

The retry-navigation event leaves a notification in opened instead of navigating.

Notification interfaces◈ Members↗
FA-35033

Notification target opening feedback: retry-navigation from navigation-error · case 03

The retry-navigation event leaves a notification in opened instead of navigating.

Notification interfaces◈ Members↗
FA-35034

Notification target opening feedback: retry-navigation from navigation-error · case 04

The retry-navigation event leaves a notification in opened instead of navigating.

Notification interfaces◈ Members↗
FA-35035

Notification target opening feedback: retry-navigation from navigation-error · case 05

The retry-navigation event leaves a notification in opened instead of navigating.

Notification interfaces◈ Members↗
FA-35036

Notification target opening feedback: cancel-open from resolving · case 01

The cancel-open event leaves a notification in opened instead of actionable.

Notification interfaces● Open access↗
FA-35037

Notification target opening feedback: cancel-open from resolving · case 02

The cancel-open event leaves a notification in opened instead of actionable.

Notification interfaces◈ Members↗
FA-35038

Notification target opening feedback: cancel-open from resolving · case 03

The cancel-open event leaves a notification in opened instead of actionable.

Notification interfaces◈ Members↗
FA-35039

Notification target opening feedback: cancel-open from resolving · case 04

The cancel-open event leaves a notification in opened instead of actionable.

Notification interfaces◈ Members↗
FA-35040

Notification target opening feedback: cancel-open from resolving · case 05

The cancel-open event leaves a notification in opened instead of actionable.

Notification interfaces◈ Members↗
FA-35041

Temporary notification mute feedback: mute-for-session from audible-channel · case 01

The mute-for-session event leaves a notification in muted instead of mute-pending.

Notification interfaces● Open access↗
FA-35042

Temporary notification mute feedback: mute-for-session from audible-channel · case 02

The mute-for-session event leaves a notification in muted instead of mute-pending.

Notification interfaces◈ Members↗
FA-35043

Temporary notification mute feedback: mute-for-session from audible-channel · case 03

The mute-for-session event leaves a notification in muted instead of mute-pending.

Notification interfaces◈ Members↗
FA-35044

Temporary notification mute feedback: mute-for-session from audible-channel · case 04

The mute-for-session event leaves a notification in muted instead of mute-pending.

Notification interfaces◈ Members↗
FA-35045

Temporary notification mute feedback: mute-for-session from audible-channel · case 05

The mute-for-session event leaves a notification in muted instead of mute-pending.

Notification interfaces◈ Members↗
FA-35046

Temporary notification mute feedback: mute-confirmed from mute-pending · case 01

The mute-confirmed event leaves a notification in audible-channel instead of muted.

Notification interfaces● Open access↗
FA-35047

Temporary notification mute feedback: mute-confirmed from mute-pending · case 02

The mute-confirmed event leaves a notification in audible-channel instead of muted.

Notification interfaces◈ Members↗
FA-35048

Temporary notification mute feedback: mute-confirmed from mute-pending · case 03

The mute-confirmed event leaves a notification in audible-channel instead of muted.

Notification interfaces◈ Members↗
FA-35049

Temporary notification mute feedback: mute-confirmed from mute-pending · case 04

The mute-confirmed event leaves a notification in audible-channel instead of muted.

Notification interfaces◈ Members↗
FA-35050

Temporary notification mute feedback: mute-confirmed from mute-pending · case 05

The mute-confirmed event leaves a notification in audible-channel instead of muted.

Notification interfaces◈ Members↗
FA-35051

Temporary notification mute feedback: mute-rejected from mute-pending · case 01

The mute-rejected event leaves a notification in muted instead of mute-error.

Notification interfaces● Open access↗
FA-35052

Temporary notification mute feedback: mute-rejected from mute-pending · case 02

The mute-rejected event leaves a notification in muted instead of mute-error.

Notification interfaces◈ Members↗
FA-35053

Temporary notification mute feedback: mute-rejected from mute-pending · case 03

The mute-rejected event leaves a notification in muted instead of mute-error.

Notification interfaces◈ Members↗
FA-35054

Temporary notification mute feedback: mute-rejected from mute-pending · case 04

The mute-rejected event leaves a notification in muted instead of mute-error.

Notification interfaces◈ Members↗
FA-35055

Temporary notification mute feedback: mute-rejected from mute-pending · case 05

The mute-rejected event leaves a notification in muted instead of mute-error.

Notification interfaces◈ Members↗
FA-35056

Temporary notification mute feedback: mute-window-ended from muted · case 01

The mute-window-ended event leaves a notification in audible-channel instead of unmute-pending.

Notification interfaces● Open access↗
FA-35057

Temporary notification mute feedback: mute-window-ended from muted · case 02

The mute-window-ended event leaves a notification in audible-channel instead of unmute-pending.

Notification interfaces◈ Members↗
FA-35058

Temporary notification mute feedback: mute-window-ended from muted · case 03

The mute-window-ended event leaves a notification in audible-channel instead of unmute-pending.

Notification interfaces◈ Members↗
FA-35059

Temporary notification mute feedback: mute-window-ended from muted · case 04

The mute-window-ended event leaves a notification in audible-channel instead of unmute-pending.

Notification interfaces◈ Members↗
FA-35060

Temporary notification mute feedback: mute-window-ended from muted · case 05

The mute-window-ended event leaves a notification in audible-channel instead of unmute-pending.

Notification interfaces◈ Members↗
FA-35061

Temporary notification mute feedback: unmute-confirmed from unmute-pending · case 01

The unmute-confirmed event leaves a notification in muted instead of audible-channel.

Notification interfaces● Open access↗
FA-35062

Temporary notification mute feedback: unmute-confirmed from unmute-pending · case 02

The unmute-confirmed event leaves a notification in muted instead of audible-channel.

Notification interfaces◈ Members↗
FA-35063

Temporary notification mute feedback: unmute-confirmed from unmute-pending · case 03

The unmute-confirmed event leaves a notification in muted instead of audible-channel.

Notification interfaces◈ Members↗
FA-35064

Temporary notification mute feedback: unmute-confirmed from unmute-pending · case 04

The unmute-confirmed event leaves a notification in muted instead of audible-channel.

Notification interfaces◈ Members↗
FA-35065

Temporary notification mute feedback: unmute-confirmed from unmute-pending · case 05

The unmute-confirmed event leaves a notification in muted instead of audible-channel.

Notification interfaces◈ Members↗
FA-35066

Temporary notification mute feedback: unmute-rejected from unmute-pending · case 01

The unmute-rejected event leaves a notification in audible-channel instead of unmute-error.

Notification interfaces● Open access↗
FA-35067

Temporary notification mute feedback: unmute-rejected from unmute-pending · case 02

The unmute-rejected event leaves a notification in audible-channel instead of unmute-error.

Notification interfaces◈ Members↗
FA-35068

Temporary notification mute feedback: unmute-rejected from unmute-pending · case 03

The unmute-rejected event leaves a notification in audible-channel instead of unmute-error.

Notification interfaces◈ Members↗
FA-35069

Temporary notification mute feedback: unmute-rejected from unmute-pending · case 04

The unmute-rejected event leaves a notification in audible-channel instead of unmute-error.

Notification interfaces◈ Members↗
FA-35070

Temporary notification mute feedback: unmute-rejected from unmute-pending · case 05

The unmute-rejected event leaves a notification in audible-channel instead of unmute-error.

Notification interfaces◈ Members↗
FA-35071

Temporary notification mute feedback: extend-mute from muted · case 01

The extend-mute event leaves a notification in audible-channel instead of extend-pending.

Notification interfaces● Open access↗
FA-35072

Temporary notification mute feedback: extend-mute from muted · case 02

The extend-mute event leaves a notification in audible-channel instead of extend-pending.

Notification interfaces◈ Members↗
FA-35073

Temporary notification mute feedback: extend-mute from muted · case 03

The extend-mute event leaves a notification in audible-channel instead of extend-pending.

Notification interfaces◈ Members↗
FA-35074

Temporary notification mute feedback: extend-mute from muted · case 04

The extend-mute event leaves a notification in audible-channel instead of extend-pending.

Notification interfaces◈ Members↗
FA-35075

Temporary notification mute feedback: extend-mute from muted · case 05

The extend-mute event leaves a notification in audible-channel instead of extend-pending.

Notification interfaces◈ Members↗
FA-35076

Temporary notification mute feedback: extension-confirmed from extend-pending · case 01

The extension-confirmed event leaves a notification in muted instead of muted-extended.

Notification interfaces● Open access↗
FA-35077

Temporary notification mute feedback: extension-confirmed from extend-pending · case 02

The extension-confirmed event leaves a notification in muted instead of muted-extended.

Notification interfaces◈ Members↗
FA-35078

Temporary notification mute feedback: extension-confirmed from extend-pending · case 03

The extension-confirmed event leaves a notification in muted instead of muted-extended.

Notification interfaces◈ Members↗
FA-35079

Temporary notification mute feedback: extension-confirmed from extend-pending · case 04

The extension-confirmed event leaves a notification in muted instead of muted-extended.

Notification interfaces◈ Members↗
FA-35080

Temporary notification mute feedback: extension-confirmed from extend-pending · case 05

The extension-confirmed event leaves a notification in muted instead of muted-extended.

Notification interfaces◈ Members↗
FA-35081

Temporary notification mute feedback: old-window-ended from muted-extended · case 01

The old-window-ended event leaves a notification in unmute-pending instead of muted-extended.

Notification interfaces● Open access↗
FA-35082

Temporary notification mute feedback: old-window-ended from muted-extended · case 02

The old-window-ended event leaves a notification in unmute-pending instead of muted-extended.

Notification interfaces◈ Members↗
FA-35083

Temporary notification mute feedback: old-window-ended from muted-extended · case 03

The old-window-ended event leaves a notification in unmute-pending instead of muted-extended.

Notification interfaces◈ Members↗
FA-35084

Temporary notification mute feedback: old-window-ended from muted-extended · case 04

The old-window-ended event leaves a notification in unmute-pending instead of muted-extended.

Notification interfaces◈ Members↗
FA-35085

Temporary notification mute feedback: old-window-ended from muted-extended · case 05

The old-window-ended event leaves a notification in unmute-pending instead of muted-extended.

Notification interfaces◈ Members↗
FA-35086

Temporary notification mute feedback: cancel-mute-intent from mute-error · case 01

The cancel-mute-intent event leaves a notification in muted instead of audible-channel.

Notification interfaces● Open access↗
FA-35087

Temporary notification mute feedback: cancel-mute-intent from mute-error · case 02

The cancel-mute-intent event leaves a notification in muted instead of audible-channel.

Notification interfaces◈ Members↗
FA-35088

Temporary notification mute feedback: cancel-mute-intent from mute-error · case 03

The cancel-mute-intent event leaves a notification in muted instead of audible-channel.

Notification interfaces◈ Members↗
FA-35089

Temporary notification mute feedback: cancel-mute-intent from mute-error · case 04

The cancel-mute-intent event leaves a notification in muted instead of audible-channel.

Notification interfaces◈ Members↗
FA-35090

Temporary notification mute feedback: cancel-mute-intent from mute-error · case 05

The cancel-mute-intent event leaves a notification in muted instead of audible-channel.

Notification interfaces◈ Members↗
FA-35091

Time-limited notification content expiry: deadline-near from valid · case 01

The deadline-near event leaves a notification in expired instead of expiring.

Notification interfaces● Open access↗
FA-35092

Time-limited notification content expiry: deadline-near from valid · case 02

The deadline-near event leaves a notification in expired instead of expiring.

Notification interfaces◈ Members↗
FA-35093

Time-limited notification content expiry: deadline-near from valid · case 03

The deadline-near event leaves a notification in expired instead of expiring.

Notification interfaces◈ Members↗
FA-35094

Time-limited notification content expiry: deadline-near from valid · case 04

The deadline-near event leaves a notification in expired instead of expiring.

Notification interfaces◈ Members↗
FA-35095

Time-limited notification content expiry: deadline-near from valid · case 05

The deadline-near event leaves a notification in expired instead of expiring.

Notification interfaces◈ Members↗
FA-35096

Time-limited notification content expiry: deadline-reached from expiring · case 01

The deadline-reached event leaves a notification in valid instead of expired.

Notification interfaces● Open access↗
FA-35097

Time-limited notification content expiry: deadline-reached from expiring · case 02

The deadline-reached event leaves a notification in valid instead of expired.

Notification interfaces◈ Members↗
FA-35098

Time-limited notification content expiry: deadline-reached from expiring · case 03

The deadline-reached event leaves a notification in valid instead of expired.

Notification interfaces◈ Members↗
FA-35099

Time-limited notification content expiry: deadline-reached from expiring · case 04

The deadline-reached event leaves a notification in valid instead of expired.

Notification interfaces◈ Members↗
FA-35100

Time-limited notification content expiry: deadline-reached from expiring · case 05

The deadline-reached event leaves a notification in valid instead of expired.

Notification interfaces◈ Members↗

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 ↗