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

Heap handle liveness is independent of payload truthiness · case 01

The bounded handle generation certificate reports an incorrect live.

Heap invariants● Open access↗
FA-40302

Heap handle liveness is independent of payload truthiness · case 02

The bounded handle generation certificate reports an incorrect live.

Heap invariants◈ Members↗
FA-40303

Heap handle liveness is independent of payload truthiness · case 03

The bounded handle generation certificate reports an incorrect live.

Heap invariants◈ Members↗
FA-40304

Heap handle liveness is independent of payload truthiness · case 04

The bounded handle generation certificate reports an incorrect live.

Heap invariants◈ Members↗
FA-40305

Heap handle liveness is independent of payload truthiness · case 05

The bounded handle generation certificate reports an incorrect live.

Heap invariants◈ Members↗
FA-40306

Heap recycled-slot generation must match exactly · case 01

The bounded handle generation certificate reports an incorrect generation.

Heap invariants● Open access↗
FA-40307

Heap recycled-slot generation must match exactly · case 02

The bounded handle generation certificate reports an incorrect generation.

Heap invariants◈ Members↗
FA-40308

Heap recycled-slot generation must match exactly · case 03

The bounded handle generation certificate reports an incorrect generation.

Heap invariants◈ Members↗
FA-40309

Heap recycled-slot generation must match exactly · case 04

The bounded handle generation certificate reports an incorrect generation.

Heap invariants◈ Members↗
FA-40310

Heap recycled-slot generation must match exactly · case 05

The bounded handle generation certificate reports an incorrect generation.

Heap invariants◈ Members↗
FA-40311

Heap resolution combines owner and generation checks to prevent ABA aliasing · case 01

The bounded handle generation certificate reports an incorrect resolved.

Heap invariants● Open access↗
FA-40312

Heap resolution combines owner and generation checks to prevent ABA aliasing · case 02

The bounded handle generation certificate reports an incorrect resolved.

Heap invariants◈ Members↗
FA-40313

Heap resolution combines owner and generation checks to prevent ABA aliasing · case 03

The bounded handle generation certificate reports an incorrect resolved.

Heap invariants◈ Members↗
FA-40314

Heap resolution combines owner and generation checks to prevent ABA aliasing · case 04

The bounded handle generation certificate reports an incorrect resolved.

Heap invariants◈ Members↗
FA-40315

Heap resolution combines owner and generation checks to prevent ABA aliasing · case 05

The bounded handle generation certificate reports an incorrect resolved.

Heap invariants◈ Members↗
FA-40316

Heap slot recycling increments the existing generation rather than resetting it · case 01

The bounded handle generation certificate reports an incorrect recycle.

Heap invariants● Open access↗
FA-40317

Heap slot recycling increments the existing generation rather than resetting it · case 02

The bounded handle generation certificate reports an incorrect recycle.

Heap invariants◈ Members↗
FA-40318

Heap slot recycling increments the existing generation rather than resetting it · case 03

The bounded handle generation certificate reports an incorrect recycle.

Heap invariants◈ Members↗
FA-40319

Heap slot recycling increments the existing generation rather than resetting it · case 04

The bounded handle generation certificate reports an incorrect recycle.

Heap invariants◈ Members↗
FA-40320

Heap slot recycling increments the existing generation rather than resetting it · case 05

The bounded handle generation certificate reports an incorrect recycle.

Heap invariants◈ Members↗
FA-40321

Lazy heap pop rejects obsolete versions even when the handle remains live · case 01

The bounded lazy pop certificate reports an incorrect selected.

Heap invariants● Open access↗
FA-40322

Lazy heap pop rejects obsolete versions even when the handle remains live · case 02

The bounded lazy pop certificate reports an incorrect selected.

Heap invariants◈ Members↗
FA-40323

Lazy heap pop rejects obsolete versions even when the handle remains live · case 03

The bounded lazy pop certificate reports an incorrect selected.

Heap invariants◈ Members↗
FA-40324

Lazy heap pop rejects obsolete versions even when the handle remains live · case 04

The bounded lazy pop certificate reports an incorrect selected.

Heap invariants◈ Members↗
FA-40325

Lazy heap pop rejects obsolete versions even when the handle remains live · case 05

The bounded lazy pop certificate reports an incorrect selected.

Heap invariants◈ Members↗
FA-40326

Lazy heap returns the current payload instead of internal handle or version · case 01

The bounded lazy pop certificate reports an incorrect payload.

Heap invariants● Open access↗
FA-40327

Lazy heap returns the current payload instead of internal handle or version · case 02

The bounded lazy pop certificate reports an incorrect payload.

Heap invariants◈ Members↗
FA-40328

Lazy heap returns the current payload instead of internal handle or version · case 03

The bounded lazy pop certificate reports an incorrect payload.

Heap invariants◈ Members↗
FA-40329

Lazy heap returns the current payload instead of internal handle or version · case 04

The bounded lazy pop certificate reports an incorrect payload.

Heap invariants◈ Members↗
FA-40330

Lazy heap returns the current payload instead of internal handle or version · case 05

The bounded lazy pop certificate reports an incorrect payload.

Heap invariants◈ Members↗
FA-40331

Lazy heap stale-discard accounting excludes the delivered live record · case 01

The bounded lazy pop certificate reports an incorrect discarded.

Heap invariants● Open access↗
FA-40332

Lazy heap stale-discard accounting excludes the delivered live record · case 02

The bounded lazy pop certificate reports an incorrect discarded.

Heap invariants◈ Members↗
FA-40333

Lazy heap stale-discard accounting excludes the delivered live record · case 03

The bounded lazy pop certificate reports an incorrect discarded.

Heap invariants◈ Members↗
FA-40334

Lazy heap stale-discard accounting excludes the delivered live record · case 04

The bounded lazy pop certificate reports an incorrect discarded.

Heap invariants◈ Members↗
FA-40335

Lazy heap stale-discard accounting excludes the delivered live record · case 05

The bounded lazy pop certificate reports an incorrect discarded.

Heap invariants◈ Members↗
FA-40336

Lazy heap pop removes only the stale prefix and selected current record · case 01

The bounded lazy pop certificate reports an incorrect suffix.

Heap invariants● Open access↗
FA-40337

Lazy heap pop removes only the stale prefix and selected current record · case 02

The bounded lazy pop certificate reports an incorrect suffix.

Heap invariants◈ Members↗
FA-40338

Lazy heap pop removes only the stale prefix and selected current record · case 03

The bounded lazy pop certificate reports an incorrect suffix.

Heap invariants◈ Members↗
FA-40339

Lazy heap pop removes only the stale prefix and selected current record · case 04

The bounded lazy pop certificate reports an incorrect suffix.

Heap invariants◈ Members↗
FA-40340

Lazy heap pop removes only the stale prefix and selected current record · case 05

The bounded lazy pop certificate reports an incorrect suffix.

Heap invariants◈ Members↗
FA-40341

Lazy heap pop invalidates the delivered handle while retaining other live entries · case 01

The bounded lazy pop certificate reports an incorrect live after.

Heap invariants● Open access↗
FA-40342

Lazy heap pop invalidates the delivered handle while retaining other live entries · case 02

The bounded lazy pop certificate reports an incorrect live after.

Heap invariants◈ Members↗
FA-40343

Lazy heap pop invalidates the delivered handle while retaining other live entries · case 03

The bounded lazy pop certificate reports an incorrect live after.

Heap invariants◈ Members↗
FA-40344

Lazy heap pop invalidates the delivered handle while retaining other live entries · case 04

The bounded lazy pop certificate reports an incorrect live after.

Heap invariants◈ Members↗
FA-40345

Lazy heap pop invalidates the delivered handle while retaining other live entries · case 05

The bounded lazy pop certificate reports an incorrect live after.

Heap invariants◈ Members↗
FA-40346

Lazy heap logical emptiness follows the presence of a current physical record · case 01

The bounded lazy pop certificate reports an incorrect empty.

Heap invariants● Open access↗
FA-40347

Lazy heap logical emptiness follows the presence of a current physical record · case 02

The bounded lazy pop certificate reports an incorrect empty.

Heap invariants◈ Members↗
FA-40348

Lazy heap logical emptiness follows the presence of a current physical record · case 03

The bounded lazy pop certificate reports an incorrect empty.

Heap invariants◈ Members↗
FA-40349

Lazy heap logical emptiness follows the presence of a current physical record · case 04

The bounded lazy pop certificate reports an incorrect empty.

Heap invariants◈ Members↗
FA-40350

Lazy heap logical emptiness follows the presence of a current physical record · case 05

The bounded lazy pop certificate reports an incorrect empty.

Heap invariants◈ Members↗
FA-40351

Lazy compaction filters by current version and restores priority order · case 01

The bounded lazy compaction certificate reports an incorrect kept.

Heap invariants● Open access↗
FA-40352

Lazy compaction filters by current version and restores priority order · case 02

The bounded lazy compaction certificate reports an incorrect kept.

Heap invariants◈ Members↗
FA-40353

Lazy compaction filters by current version and restores priority order · case 03

The bounded lazy compaction certificate reports an incorrect kept.

Heap invariants◈ Members↗
FA-40354

Lazy compaction filters by current version and restores priority order · case 04

The bounded lazy compaction certificate reports an incorrect kept.

Heap invariants◈ Members↗
FA-40355

Lazy compaction filters by current version and restores priority order · case 05

The bounded lazy compaction certificate reports an incorrect kept.

Heap invariants◈ Members↗
FA-40356

Lazy compaction counts obsolete physical records rather than logical size difference · case 01

The bounded lazy compaction certificate reports an incorrect stale.

Heap invariants● Open access↗
FA-40357

Lazy compaction counts obsolete physical records rather than logical size difference · case 02

The bounded lazy compaction certificate reports an incorrect stale.

Heap invariants◈ Members↗
FA-40358

Lazy compaction counts obsolete physical records rather than logical size difference · case 03

The bounded lazy compaction certificate reports an incorrect stale.

Heap invariants◈ Members↗
FA-40359

Lazy compaction counts obsolete physical records rather than logical size difference · case 04

The bounded lazy compaction certificate reports an incorrect stale.

Heap invariants◈ Members↗
FA-40360

Lazy compaction counts obsolete physical records rather than logical size difference · case 05

The bounded lazy compaction certificate reports an incorrect stale.

Heap invariants◈ Members↗
FA-40361

Lazy compaction detects duplicate current entries without confusing obsolete versions · case 01

The bounded lazy compaction certificate reports an incorrect duplicate current.

Heap invariants● Open access↗
FA-40362

Lazy compaction detects duplicate current entries without confusing obsolete versions · case 02

The bounded lazy compaction certificate reports an incorrect duplicate current.

Heap invariants◈ Members↗
FA-40363

Lazy compaction detects duplicate current entries without confusing obsolete versions · case 03

The bounded lazy compaction certificate reports an incorrect duplicate current.

Heap invariants◈ Members↗
FA-40364

Lazy compaction detects duplicate current entries without confusing obsolete versions · case 04

The bounded lazy compaction certificate reports an incorrect duplicate current.

Heap invariants◈ Members↗
FA-40365

Lazy compaction detects duplicate current entries without confusing obsolete versions · case 05

The bounded lazy compaction certificate reports an incorrect duplicate current.

Heap invariants◈ Members↗
FA-40366

Lazy compaction coverage requires a current physical representative · case 01

The bounded lazy compaction certificate reports an incorrect missing.

Heap invariants● Open access↗
FA-40367

Lazy compaction coverage requires a current physical representative · case 02

The bounded lazy compaction certificate reports an incorrect missing.

Heap invariants◈ Members↗
FA-40368

Lazy compaction coverage requires a current physical representative · case 03

The bounded lazy compaction certificate reports an incorrect missing.

Heap invariants◈ Members↗
FA-40369

Lazy compaction coverage requires a current physical representative · case 04

The bounded lazy compaction certificate reports an incorrect missing.

Heap invariants◈ Members↗
FA-40370

Lazy compaction coverage requires a current physical representative · case 05

The bounded lazy compaction certificate reports an incorrect missing.

Heap invariants◈ Members↗
FA-40371

Lazy compaction reports physical current-entry count including corruption duplicates · case 01

The bounded lazy compaction certificate reports an incorrect post size.

Heap invariants● Open access↗
FA-40372

Lazy compaction reports physical current-entry count including corruption duplicates · case 02

The bounded lazy compaction certificate reports an incorrect post size.

Heap invariants◈ Members↗
FA-40373

Lazy compaction reports physical current-entry count including corruption duplicates · case 03

The bounded lazy compaction certificate reports an incorrect post size.

Heap invariants◈ Members↗
FA-40374

Lazy compaction reports physical current-entry count including corruption duplicates · case 04

The bounded lazy compaction certificate reports an incorrect post size.

Heap invariants◈ Members↗
FA-40375

Lazy compaction reports physical current-entry count including corruption duplicates · case 05

The bounded lazy compaction certificate reports an incorrect post size.

Heap invariants◈ Members↗
FA-40376

Lazy heap compaction threshold adds slack after doubling logical occupancy · case 01

The bounded lazy compaction certificate reports an incorrect trigger.

Heap invariants● Open access↗
FA-40377

Lazy heap compaction threshold adds slack after doubling logical occupancy · case 02

The bounded lazy compaction certificate reports an incorrect trigger.

Heap invariants◈ Members↗
FA-40378

Lazy heap compaction threshold adds slack after doubling logical occupancy · case 03

The bounded lazy compaction certificate reports an incorrect trigger.

Heap invariants◈ Members↗
FA-40379

Lazy heap compaction threshold adds slack after doubling logical occupancy · case 04

The bounded lazy compaction certificate reports an incorrect trigger.

Heap invariants◈ Members↗
FA-40380

Lazy heap compaction threshold adds slack after doubling logical occupancy · case 05

The bounded lazy compaction certificate reports an incorrect trigger.

Heap invariants◈ Members↗
FA-40381

Min-max heap level parity comes from tree depth rather than array parity · case 01

The bounded minmax levels certificate reports an incorrect parity.

Heap invariants● Open access↗
FA-40382

Min-max heap level parity comes from tree depth rather than array parity · case 02

The bounded minmax levels certificate reports an incorrect parity.

Heap invariants◈ Members↗
FA-40383

Min-max heap level parity comes from tree depth rather than array parity · case 03

The bounded minmax levels certificate reports an incorrect parity.

Heap invariants◈ Members↗
FA-40384

Min-max heap level parity comes from tree depth rather than array parity · case 04

The bounded minmax levels certificate reports an incorrect parity.

Heap invariants◈ Members↗
FA-40385

Min-max heap level parity comes from tree depth rather than array parity · case 05

The bounded minmax levels certificate reports an incorrect parity.

Heap invariants◈ Members↗
FA-40386

Min-max heap grandparent skips two binary levels · case 01

The bounded minmax levels certificate reports an incorrect grandparents.

Heap invariants● Open access↗
FA-40387

Min-max heap grandparent skips two binary levels · case 02

The bounded minmax levels certificate reports an incorrect grandparents.

Heap invariants◈ Members↗
FA-40388

Min-max heap grandparent skips two binary levels · case 03

The bounded minmax levels certificate reports an incorrect grandparents.

Heap invariants◈ Members↗
FA-40389

Min-max heap grandparent skips two binary levels · case 04

The bounded minmax levels certificate reports an incorrect grandparents.

Heap invariants◈ Members↗
FA-40390

Min-max heap grandparent skips two binary levels · case 05

The bounded minmax levels certificate reports an incorrect grandparents.

Heap invariants◈ Members↗
FA-40391

Min-level bubbling compares grandchildren and allows equal priorities · case 01

The bounded minmax levels certificate reports an incorrect min violations.

Heap invariants● Open access↗
FA-40392

Min-level bubbling compares grandchildren and allows equal priorities · case 02

The bounded minmax levels certificate reports an incorrect min violations.

Heap invariants◈ Members↗
FA-40393

Min-level bubbling compares grandchildren and allows equal priorities · case 03

The bounded minmax levels certificate reports an incorrect min violations.

Heap invariants◈ Members↗
FA-40394

Min-level bubbling compares grandchildren and allows equal priorities · case 04

The bounded minmax levels certificate reports an incorrect min violations.

Heap invariants◈ Members↗
FA-40395

Min-level bubbling compares grandchildren and allows equal priorities · case 05

The bounded minmax levels certificate reports an incorrect min violations.

Heap invariants◈ Members↗
FA-40396

Max-level bubbling reverses the grandchild comparison while allowing ties · case 01

The bounded minmax levels certificate reports an incorrect max violations.

Heap invariants● Open access↗
FA-40397

Max-level bubbling reverses the grandchild comparison while allowing ties · case 02

The bounded minmax levels certificate reports an incorrect max violations.

Heap invariants◈ Members↗
FA-40398

Max-level bubbling reverses the grandchild comparison while allowing ties · case 03

The bounded minmax levels certificate reports an incorrect max violations.

Heap invariants◈ Members↗
FA-40399

Max-level bubbling reverses the grandchild comparison while allowing ties · case 04

The bounded minmax levels certificate reports an incorrect max violations.

Heap invariants◈ Members↗
FA-40400

Max-level bubbling reverses the grandchild comparison while allowing ties · case 05

The bounded minmax levels certificate reports an incorrect max violations.

Heap invariants◈ 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 ↗