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

A delete-vector scan also removes surviving null-valued rows · case 01

A delete-vector scan also removes surviving null-valued rows.

Data systems● Open access↗
FA-45502

A delete-vector scan also removes surviving null-valued rows · case 02

A delete-vector scan also removes surviving null-valued rows.

Data systems◈ Members↗
FA-45503

A delete-vector scan also removes surviving null-valued rows · case 03

A delete-vector scan also removes surviving null-valued rows.

Data systems◈ Members↗
FA-45504

A delete-vector scan also removes surviving null-valued rows · case 04

A delete-vector scan also removes surviving null-valued rows.

Data systems◈ Members↗
FA-45505

A delete-vector scan also removes surviving null-valued rows · case 05

A delete-vector scan also removes surviving null-valued rows.

Data systems◈ Members↗
FA-45506

Delete-vector scanning sorts fragments by physical filename · case 01

Delete-vector scanning sorts fragments by physical filename.

Data systems● Open access↗
FA-45507

Delete-vector scanning sorts fragments by physical filename · case 02

Delete-vector scanning sorts fragments by physical filename.

Data systems◈ Members↗
FA-45508

Delete-vector scanning sorts fragments by physical filename · case 03

Delete-vector scanning sorts fragments by physical filename.

Data systems◈ Members↗
FA-45509

Delete-vector scanning sorts fragments by physical filename · case 04

Delete-vector scanning sorts fragments by physical filename.

Data systems◈ Members↗
FA-45510

Delete-vector scanning sorts fragments by physical filename · case 05

Delete-vector scanning sorts fragments by physical filename.

Data systems◈ Members↗
FA-45511

Transaction coalescing replaces the original before-image on every update · case 01

Transaction coalescing replaces the original before-image on every update.

Data systems● Open access↗
FA-45512

Transaction coalescing replaces the original before-image on every update · case 02

Transaction coalescing replaces the original before-image on every update.

Data systems◈ Members↗
FA-45513

Transaction coalescing replaces the original before-image on every update · case 03

Transaction coalescing replaces the original before-image on every update.

Data systems◈ Members↗
FA-45514

Transaction coalescing replaces the original before-image on every update · case 04

Transaction coalescing replaces the original before-image on every update.

Data systems◈ Members↗
FA-45515

Transaction coalescing replaces the original before-image on every update · case 05

Transaction coalescing replaces the original before-image on every update.

Data systems◈ Members↗
FA-45516

Transaction coalescing retains the first after-image · case 01

Transaction coalescing retains the first after-image.

Data systems● Open access↗
FA-45517

Transaction coalescing retains the first after-image · case 02

Transaction coalescing retains the first after-image.

Data systems◈ Members↗
FA-45518

Transaction coalescing retains the first after-image · case 03

Transaction coalescing retains the first after-image.

Data systems◈ Members↗
FA-45519

Transaction coalescing retains the first after-image · case 04

Transaction coalescing retains the first after-image.

Data systems◈ Members↗
FA-45520

Transaction coalescing retains the first after-image · case 05

Transaction coalescing retains the first after-image.

Data systems◈ Members↗
FA-45521

Transaction coalescing emits identities whose net state is unchanged · case 01

Transaction coalescing emits identities whose net state is unchanged.

Data systems● Open access↗
FA-45522

Transaction coalescing emits identities whose net state is unchanged · case 02

Transaction coalescing emits identities whose net state is unchanged.

Data systems◈ Members↗
FA-45523

Transaction coalescing emits identities whose net state is unchanged · case 03

Transaction coalescing emits identities whose net state is unchanged.

Data systems◈ Members↗
FA-45524

Transaction coalescing emits identities whose net state is unchanged · case 04

Transaction coalescing emits identities whose net state is unchanged.

Data systems◈ Members↗
FA-45525

Transaction coalescing emits identities whose net state is unchanged · case 05

Transaction coalescing emits identities whose net state is unchanged.

Data systems◈ Members↗
FA-45526

Transaction coalescing sorts IDs instead of preserving first-touch order · case 01

Transaction coalescing sorts IDs instead of preserving first-touch order.

Data systems● Open access↗
FA-45527

Transaction coalescing sorts IDs instead of preserving first-touch order · case 02

Transaction coalescing sorts IDs instead of preserving first-touch order.

Data systems◈ Members↗
FA-45528

Transaction coalescing sorts IDs instead of preserving first-touch order · case 03

Transaction coalescing sorts IDs instead of preserving first-touch order.

Data systems◈ Members↗
FA-45529

Transaction coalescing sorts IDs instead of preserving first-touch order · case 04

Transaction coalescing sorts IDs instead of preserving first-touch order.

Data systems◈ Members↗
FA-45530

Transaction coalescing sorts IDs instead of preserving first-touch order · case 05

Transaction coalescing sorts IDs instead of preserving first-touch order.

Data systems◈ Members↗
FA-45531

Transaction coalescing initializes each identity as an insertion · case 01

Transaction coalescing initializes each identity as an insertion.

Data systems● Open access↗
FA-45532

Transaction coalescing initializes each identity as an insertion · case 02

Transaction coalescing initializes each identity as an insertion.

Data systems◈ Members↗
FA-45533

Transaction coalescing initializes each identity as an insertion · case 03

Transaction coalescing initializes each identity as an insertion.

Data systems◈ Members↗
FA-45534

Transaction coalescing initializes each identity as an insertion · case 04

Transaction coalescing initializes each identity as an insertion.

Data systems◈ Members↗
FA-45535

Transaction coalescing initializes each identity as an insertion · case 05

Transaction coalescing initializes each identity as an insertion.

Data systems◈ Members↗
FA-45536

Transaction coalescing appends an output identity on every update · case 01

Transaction coalescing appends an output identity on every update.

Data systems● Open access↗
FA-45537

Transaction coalescing appends an output identity on every update · case 02

Transaction coalescing appends an output identity on every update.

Data systems◈ Members↗
FA-45538

Transaction coalescing appends an output identity on every update · case 03

Transaction coalescing appends an output identity on every update.

Data systems◈ Members↗
FA-45539

Transaction coalescing appends an output identity on every update · case 04

Transaction coalescing appends an output identity on every update.

Data systems◈ Members↗
FA-45540

Transaction coalescing appends an output identity on every update · case 05

Transaction coalescing appends an output identity on every update.

Data systems◈ Members↗
FA-45541

Membership maintenance overwrites repeated right-key deltas · case 01

Membership maintenance overwrites repeated right-key deltas.

Data systems● Open access↗
FA-45542

Membership maintenance overwrites repeated right-key deltas · case 02

Membership maintenance overwrites repeated right-key deltas.

Data systems◈ Members↗
FA-45543

Membership maintenance overwrites repeated right-key deltas · case 03

Membership maintenance overwrites repeated right-key deltas.

Data systems◈ Members↗
FA-45544

Membership maintenance overwrites repeated right-key deltas · case 04

Membership maintenance overwrites repeated right-key deltas.

Data systems◈ Members↗
FA-45545

Membership maintenance overwrites repeated right-key deltas · case 05

Membership maintenance overwrites repeated right-key deltas.

Data systems◈ Members↗
FA-45546

Membership crossings emit one row regardless of left multiplicity · case 01

Membership crossings emit one row regardless of left multiplicity.

Data systems● Open access↗
FA-45547

Membership crossings emit one row regardless of left multiplicity · case 02

Membership crossings emit one row regardless of left multiplicity.

Data systems◈ Members↗
FA-45548

Membership crossings emit one row regardless of left multiplicity · case 03

Membership crossings emit one row regardless of left multiplicity.

Data systems◈ Members↗
FA-45549

Membership crossings emit one row regardless of left multiplicity · case 04

Membership crossings emit one row regardless of left multiplicity.

Data systems◈ Members↗
FA-45550

Membership crossings emit one row regardless of left multiplicity · case 05

Membership crossings emit one row regardless of left multiplicity.

Data systems◈ Members↗
FA-45551

Membership maintenance forwards right count changes into left weights · case 01

Membership maintenance forwards right count changes into left weights.

Data systems● Open access↗
FA-45552

Membership maintenance forwards right count changes into left weights · case 02

Membership maintenance forwards right count changes into left weights.

Data systems◈ Members↗
FA-45553

Membership maintenance forwards right count changes into left weights · case 03

Membership maintenance forwards right count changes into left weights.

Data systems◈ Members↗
FA-45554

Membership maintenance forwards right count changes into left weights · case 04

Membership maintenance forwards right count changes into left weights.

Data systems◈ Members↗
FA-45555

Membership maintenance forwards right count changes into left weights · case 05

Membership maintenance forwards right count changes into left weights.

Data systems◈ Members↗
FA-45556

Membership maintenance matches null keys against right counts · case 01

Membership maintenance matches null keys against right counts.

Data systems● Open access↗
FA-45557

Membership maintenance matches null keys against right counts · case 02

Membership maintenance matches null keys against right counts.

Data systems◈ Members↗
FA-45558

Membership maintenance matches null keys against right counts · case 03

Membership maintenance matches null keys against right counts.

Data systems◈ Members↗
FA-45559

Membership maintenance matches null keys against right counts · case 04

Membership maintenance matches null keys against right counts.

Data systems◈ Members↗
FA-45560

Membership maintenance matches null keys against right counts · case 05

Membership maintenance matches null keys against right counts.

Data systems◈ Members↗
FA-45561

Membership maintenance uses whole-right emptiness for every left key · case 01

Membership maintenance uses whole-right emptiness for every left key.

Data systems● Open access↗
FA-45562

Membership maintenance uses whole-right emptiness for every left key · case 02

Membership maintenance uses whole-right emptiness for every left key.

Data systems◈ Members↗
FA-45563

Membership maintenance uses whole-right emptiness for every left key · case 03

Membership maintenance uses whole-right emptiness for every left key.

Data systems◈ Members↗
FA-45564

Membership maintenance uses whole-right emptiness for every left key · case 04

Membership maintenance uses whole-right emptiness for every left key.

Data systems◈ Members↗
FA-45565

Membership maintenance uses whole-right emptiness for every left key · case 05

Membership maintenance uses whole-right emptiness for every left key.

Data systems◈ Members↗
FA-45566

Right membership disappearance produces positive left changes · case 01

Right membership disappearance produces positive left changes.

Data systems● Open access↗
FA-45567

Right membership disappearance produces positive left changes · case 02

Right membership disappearance produces positive left changes.

Data systems◈ Members↗
FA-45568

Right membership disappearance produces positive left changes · case 03

Right membership disappearance produces positive left changes.

Data systems◈ Members↗
FA-45569

Right membership disappearance produces positive left changes · case 04

Right membership disappearance produces positive left changes.

Data systems◈ Members↗
FA-45570

Right membership disappearance produces positive left changes · case 05

Right membership disappearance produces positive left changes.

Data systems◈ Members↗
FA-45571

Default materialization overwrites explicit null columns · case 01

Default materialization overwrites explicit null columns.

Data systems● Open access↗
FA-45572

Default materialization overwrites explicit null columns · case 02

Default materialization overwrites explicit null columns.

Data systems◈ Members↗
FA-45573

Default materialization overwrites explicit null columns · case 03

Default materialization overwrites explicit null columns.

Data systems◈ Members↗
FA-45574

Default materialization overwrites explicit null columns · case 04

Default materialization overwrites explicit null columns.

Data systems◈ Members↗
FA-45575

Default materialization overwrites explicit null columns · case 05

Default materialization overwrites explicit null columns.

Data systems◈ Members↗
FA-45576

Default evaluation discards rules whose dependencies appear later · case 01

Default evaluation discards rules whose dependencies appear later.

Data systems● Open access↗
FA-45577

Default evaluation discards rules whose dependencies appear later · case 02

Default evaluation discards rules whose dependencies appear later.

Data systems◈ Members↗
FA-45578

Default evaluation discards rules whose dependencies appear later · case 03

Default evaluation discards rules whose dependencies appear later.

Data systems◈ Members↗
FA-45579

Default evaluation discards rules whose dependencies appear later · case 04

Default evaluation discards rules whose dependencies appear later.

Data systems◈ Members↗
FA-45580

Default evaluation discards rules whose dependencies appear later · case 05

Default evaluation discards rules whose dependencies appear later.

Data systems◈ Members↗
FA-45581

Dependent defaults treat an explicit null source as zero · case 01

Dependent defaults treat an explicit null source as zero.

Data systems● Open access↗
FA-45582

Dependent defaults treat an explicit null source as zero · case 02

Dependent defaults treat an explicit null source as zero.

Data systems◈ Members↗
FA-45583

Dependent defaults treat an explicit null source as zero · case 03

Dependent defaults treat an explicit null source as zero.

Data systems◈ Members↗
FA-45584

Dependent defaults treat an explicit null source as zero · case 04

Dependent defaults treat an explicit null source as zero.

Data systems◈ Members↗
FA-45585

Dependent defaults treat an explicit null source as zero · case 05

Dependent defaults treat an explicit null source as zero.

Data systems◈ Members↗
FA-45586

A dependent default writes only its constant without reading the source · case 01

A dependent default writes only its constant without reading the source.

Data systems● Open access↗
FA-45587

A dependent default writes only its constant without reading the source · case 02

A dependent default writes only its constant without reading the source.

Data systems◈ Members↗
FA-45588

A dependent default writes only its constant without reading the source · case 03

A dependent default writes only its constant without reading the source.

Data systems◈ Members↗
FA-45589

A dependent default writes only its constant without reading the source · case 04

A dependent default writes only its constant without reading the source.

Data systems◈ Members↗
FA-45590

A dependent default writes only its constant without reading the source · case 05

A dependent default writes only its constant without reading the source.

Data systems◈ Members↗
FA-45591

Default dependency cycles silently return a partial row · case 01

Default dependency cycles silently return a partial row.

Data systems● Open access↗
FA-45592

Default dependency cycles silently return a partial row · case 02

Default dependency cycles silently return a partial row.

Data systems◈ Members↗
FA-45593

Default dependency cycles silently return a partial row · case 03

Default dependency cycles silently return a partial row.

Data systems◈ Members↗
FA-45594

Default dependency cycles silently return a partial row · case 04

Default dependency cycles silently return a partial row.

Data systems◈ Members↗
FA-45595

Default dependency cycles silently return a partial row · case 05

Default dependency cycles silently return a partial row.

Data systems◈ Members↗
FA-45596

Default materialization discards explicitly provided columns · case 01

Default materialization discards explicitly provided columns.

Data systems● Open access↗
FA-45597

Default materialization discards explicitly provided columns · case 02

Default materialization discards explicitly provided columns.

Data systems◈ Members↗
FA-45598

Default materialization discards explicitly provided columns · case 03

Default materialization discards explicitly provided columns.

Data systems◈ Members↗
FA-45599

Default materialization discards explicitly provided columns · case 04

Default materialization discards explicitly provided columns.

Data systems◈ Members↗
FA-45600

Default materialization discards explicitly provided columns · case 05

Default materialization discards explicitly provided columns.

Data systems◈ 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 ↗