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-38301

Table column schema migration: migration order dedupe · case 01

The table migration order dedupe result violates the stipulated table column schema migration contract.

Table interactions● Open access↗
FA-38302

Table column schema migration: migration order dedupe · case 02

The table migration order dedupe result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38303

Table column schema migration: migration order dedupe · case 03

The table migration order dedupe result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38304

Table column schema migration: migration order dedupe · case 04

The table migration order dedupe result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38305

Table column schema migration: migration order dedupe · case 05

The table migration order dedupe result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38306

Table column schema migration: new column append · case 01

The table new column append result violates the stipulated table column schema migration contract.

Table interactions● Open access↗
FA-38307

Table column schema migration: new column append · case 02

The table new column append result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38308

Table column schema migration: new column append · case 03

The table new column append result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38309

Table column schema migration: new column append · case 04

The table new column append result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38310

Table column schema migration: new column append · case 05

The table new column append result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38311

Table column schema migration: direct width precedence · case 01

The table direct width precedence result violates the stipulated table column schema migration contract.

Table interactions● Open access↗
FA-38312

Table column schema migration: direct width precedence · case 02

The table direct width precedence result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38313

Table column schema migration: direct width precedence · case 03

The table direct width precedence result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38314

Table column schema migration: direct width precedence · case 04

The table direct width precedence result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38315

Table column schema migration: direct width precedence · case 05

The table direct width precedence result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38316

Table column schema migration: required migrated visibility · case 01

The table required migrated visibility result violates the stipulated table column schema migration contract.

Table interactions● Open access↗
FA-38317

Table column schema migration: required migrated visibility · case 02

The table required migrated visibility result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38318

Table column schema migration: required migrated visibility · case 03

The table required migrated visibility result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38319

Table column schema migration: required migrated visibility · case 04

The table required migrated visibility result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38320

Table column schema migration: required migrated visibility · case 05

The table required migrated visibility result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38321

Table column schema migration: draft type compatibility · case 01

The table draft type compatibility result violates the stipulated table column schema migration contract.

Table interactions● Open access↗
FA-38322

Table column schema migration: draft type compatibility · case 02

The table draft type compatibility result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38323

Table column schema migration: draft type compatibility · case 03

The table draft type compatibility result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38324

Table column schema migration: draft type compatibility · case 04

The table draft type compatibility result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38325

Table column schema migration: draft type compatibility · case 05

The table draft type compatibility result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38326

Table column schema migration: draft renamed coordinate · case 01

The table draft renamed coordinate result violates the stipulated table column schema migration contract.

Table interactions● Open access↗
FA-38327

Table column schema migration: draft renamed coordinate · case 02

The table draft renamed coordinate result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38328

Table column schema migration: draft renamed coordinate · case 03

The table draft renamed coordinate result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38329

Table column schema migration: draft renamed coordinate · case 04

The table draft renamed coordinate result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38330

Table column schema migration: draft renamed coordinate · case 05

The table draft renamed coordinate result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38331

Table column schema migration: selection migration dedupe · case 01

The table selection migration dedupe result violates the stipulated table column schema migration contract.

Table interactions● Open access↗
FA-38332

Table column schema migration: selection migration dedupe · case 02

The table selection migration dedupe result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38333

Table column schema migration: selection migration dedupe · case 03

The table selection migration dedupe result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38334

Table column schema migration: selection migration dedupe · case 04

The table selection migration dedupe result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38335

Table column schema migration: selection migration dedupe · case 05

The table selection migration dedupe result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38336

Table column schema migration: removed anchor clearing · case 01

The table removed anchor clearing result violates the stipulated table column schema migration contract.

Table interactions● Open access↗
FA-38337

Table column schema migration: removed anchor clearing · case 02

The table removed anchor clearing result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38338

Table column schema migration: removed anchor clearing · case 03

The table removed anchor clearing result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38339

Table column schema migration: removed anchor clearing · case 04

The table removed anchor clearing result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38340

Table column schema migration: removed anchor clearing · case 05

The table removed anchor clearing result violates the stipulated table column schema migration contract.

Table interactions◈ Members↗
FA-38341

Visible tree range selection: Hidden range anchor loses its focused fallback · case 01

Hidden range anchor loses its focused fallback produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38342

Visible tree range selection: Hidden range anchor loses its focused fallback · case 02

Hidden range anchor loses its focused fallback produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38343

Visible tree range selection: Hidden range anchor loses its focused fallback · case 03

Hidden range anchor loses its focused fallback produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38344

Visible tree range selection: Hidden range anchor loses its focused fallback · case 04

Hidden range anchor loses its focused fallback produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38345

Visible tree range selection: Hidden range anchor loses its focused fallback · case 05

Hidden range anchor loses its focused fallback produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38346

Visible tree range selection: Reverse range start is not normalized · case 01

Reverse range start is not normalized produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38347

Visible tree range selection: Reverse range start is not normalized · case 02

Reverse range start is not normalized produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38348

Visible tree range selection: Reverse range start is not normalized · case 03

Reverse range start is not normalized produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38349

Visible tree range selection: Reverse range start is not normalized · case 04

Reverse range start is not normalized produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38350

Visible tree range selection: Reverse range start is not normalized · case 05

Reverse range start is not normalized produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38351

Visible tree range selection: Inclusive target is dropped · case 01

Inclusive target is dropped produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38352

Visible tree range selection: Inclusive target is dropped · case 02

Inclusive target is dropped produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38353

Visible tree range selection: Inclusive target is dropped · case 03

Inclusive target is dropped produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38354

Visible tree range selection: Inclusive target is dropped · case 04

Inclusive target is dropped produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38355

Visible tree range selection: Inclusive target is dropped · case 05

Inclusive target is dropped produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38356

Visible tree range selection: Disabled rows enter a range · case 01

Disabled rows enter a range produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38357

Visible tree range selection: Disabled rows enter a range · case 02

Disabled rows enter a range produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38358

Visible tree range selection: Disabled rows enter a range · case 03

Disabled rows enter a range produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38359

Visible tree range selection: Disabled rows enter a range · case 04

Disabled rows enter a range produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38360

Visible tree range selection: Disabled rows enter a range · case 05

Disabled rows enter a range produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38361

Visible tree range selection: Additive selection replaces unrelated selected branches · case 01

Additive selection replaces unrelated selected branches produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38362

Visible tree range selection: Additive selection replaces unrelated selected branches · case 02

Additive selection replaces unrelated selected branches produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38363

Visible tree range selection: Additive selection replaces unrelated selected branches · case 03

Additive selection replaces unrelated selected branches produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38364

Visible tree range selection: Additive selection replaces unrelated selected branches · case 04

Additive selection replaces unrelated selected branches produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38365

Visible tree range selection: Additive selection replaces unrelated selected branches · case 05

Additive selection replaces unrelated selected branches produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38366

Visible tree range selection: Range union toggles previously selected descendants · case 01

Range union toggles previously selected descendants produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38367

Visible tree range selection: Range union toggles previously selected descendants · case 02

Range union toggles previously selected descendants produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38368

Visible tree range selection: Range union toggles previously selected descendants · case 03

Range union toggles previously selected descendants produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38369

Visible tree range selection: Range union toggles previously selected descendants · case 04

Range union toggles previously selected descendants produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38370

Visible tree range selection: Range union toggles previously selected descendants · case 05

Range union toggles previously selected descendants produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38371

Visible tree range selection: Selection output loses visible preorder · case 01

Selection output loses visible preorder produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38372

Visible tree range selection: Selection output loses visible preorder · case 02

Selection output loses visible preorder produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38373

Visible tree range selection: Selection output loses visible preorder · case 03

Selection output loses visible preorder produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38374

Visible tree range selection: Selection output loses visible preorder · case 04

Selection output loses visible preorder produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38375

Visible tree range selection: Selection output loses visible preorder · case 05

Selection output loses visible preorder produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38376

Visible tree range selection: Range selection leaves focus at the anchor · case 01

Range selection leaves focus at the anchor produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38377

Visible tree range selection: Range selection leaves focus at the anchor · case 02

Range selection leaves focus at the anchor produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38378

Visible tree range selection: Range selection leaves focus at the anchor · case 03

Range selection leaves focus at the anchor produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38379

Visible tree range selection: Range selection leaves focus at the anchor · case 04

Range selection leaves focus at the anchor produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38380

Visible tree range selection: Range selection leaves focus at the anchor · case 05

Range selection leaves focus at the anchor produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38381

Visible tree range selection: Extending a range moves its stable anchor · case 01

Extending a range moves its stable anchor produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38382

Visible tree range selection: Extending a range moves its stable anchor · case 02

Extending a range moves its stable anchor produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38383

Visible tree range selection: Extending a range moves its stable anchor · case 03

Extending a range moves its stable anchor produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38384

Visible tree range selection: Extending a range moves its stable anchor · case 04

Extending a range moves its stable anchor produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38385

Visible tree range selection: Extending a range moves its stable anchor · case 05

Extending a range moves its stable anchor produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38386

Visible tree range selection: Empty or partially selected branch is marked covered · case 01

Empty or partially selected branch is marked covered produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38387

Visible tree range selection: Empty or partially selected branch is marked covered · case 02

Empty or partially selected branch is marked covered produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38388

Visible tree range selection: Empty or partially selected branch is marked covered · case 03

Empty or partially selected branch is marked covered produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38389

Visible tree range selection: Empty or partially selected branch is marked covered · case 04

Empty or partially selected branch is marked covered produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38390

Visible tree range selection: Empty or partially selected branch is marked covered · case 05

Empty or partially selected branch is marked covered produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38391

Hierarchical checkbox cascade: Disabled descendants become writable · case 01

Disabled descendants become writable produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38392

Hierarchical checkbox cascade: Disabled descendants become writable · case 02

Disabled descendants become writable produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38393

Hierarchical checkbox cascade: Disabled descendants become writable · case 03

Disabled descendants become writable produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38394

Hierarchical checkbox cascade: Disabled descendants become writable · case 04

Disabled descendants become writable produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38395

Hierarchical checkbox cascade: Disabled descendants become writable · case 05

Disabled descendants become writable produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38396

Hierarchical checkbox cascade: Partial branch toggles toward unchecked · case 01

Partial branch toggles toward unchecked produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38397

Hierarchical checkbox cascade: Partial branch toggles toward unchecked · case 02

Partial branch toggles toward unchecked produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38398

Hierarchical checkbox cascade: Partial branch toggles toward unchecked · case 03

Partial branch toggles toward unchecked produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38399

Hierarchical checkbox cascade: Partial branch toggles toward unchecked · case 04

Partial branch toggles toward unchecked produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38400

Hierarchical checkbox cascade: Partial branch toggles toward unchecked · case 05

Partial branch toggles toward unchecked produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ 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 ↗