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

Bounded accessible branch expansion eviction: Budget eviction drops user pin or requested branch · case 01

Budget eviction drops user pin or requested branch produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-39802

Bounded accessible branch expansion eviction: Budget eviction drops user pin or requested branch · case 02

Budget eviction drops user pin or requested branch produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39803

Bounded accessible branch expansion eviction: Budget eviction drops user pin or requested branch · case 03

Budget eviction drops user pin or requested branch produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39804

Bounded accessible branch expansion eviction: Budget eviction drops user pin or requested branch · case 04

Budget eviction drops user pin or requested branch produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39805

Bounded accessible branch expansion eviction: Budget eviction drops user pin or requested branch · case 05

Budget eviction drops user pin or requested branch produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39806

Bounded accessible branch expansion eviction: Eviction chooses lexicographic or most-recent branch · case 01

Eviction chooses lexicographic or most-recent branch produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-39807

Bounded accessible branch expansion eviction: Eviction chooses lexicographic or most-recent branch · case 02

Eviction chooses lexicographic or most-recent branch produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39808

Bounded accessible branch expansion eviction: Eviction chooses lexicographic or most-recent branch · case 03

Eviction chooses lexicographic or most-recent branch produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39809

Bounded accessible branch expansion eviction: Eviction chooses lexicographic or most-recent branch · case 04

Eviction chooses lexicographic or most-recent branch produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39810

Bounded accessible branch expansion eviction: Eviction chooses lexicographic or most-recent branch · case 05

Eviction chooses lexicographic or most-recent branch produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39811

Bounded accessible branch expansion eviction: Expansion budget stop compares count instead of weights or misses equality · case 01

Expansion budget stop compares count instead of weights or misses equality produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-39812

Bounded accessible branch expansion eviction: Expansion budget stop compares count instead of weights or misses equality · case 02

Expansion budget stop compares count instead of weights or misses equality produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39813

Bounded accessible branch expansion eviction: Expansion budget stop compares count instead of weights or misses equality · case 03

Expansion budget stop compares count instead of weights or misses equality produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39814

Bounded accessible branch expansion eviction: Expansion budget stop compares count instead of weights or misses equality · case 04

Expansion budget stop compares count instead of weights or misses equality produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39815

Bounded accessible branch expansion eviction: Expansion budget stop compares count instead of weights or misses equality · case 05

Expansion budget stop compares count instead of weights or misses equality produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39816

Bounded accessible branch expansion eviction: Eviction retains expanded descendants or branch root · case 01

Eviction retains expanded descendants or branch root produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-39817

Bounded accessible branch expansion eviction: Eviction retains expanded descendants or branch root · case 02

Eviction retains expanded descendants or branch root produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39818

Bounded accessible branch expansion eviction: Eviction retains expanded descendants or branch root · case 03

Eviction retains expanded descendants or branch root produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39819

Bounded accessible branch expansion eviction: Eviction retains expanded descendants or branch root · case 04

Eviction retains expanded descendants or branch root produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39820

Bounded accessible branch expansion eviction: Eviction retains expanded descendants or branch root · case 05

Eviction retains expanded descendants or branch root produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39821

Bounded accessible branch expansion eviction: Eviction ignores pinned descendant inside candidate subtree · case 01

Eviction ignores pinned descendant inside candidate subtree produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-39822

Bounded accessible branch expansion eviction: Eviction ignores pinned descendant inside candidate subtree · case 02

Eviction ignores pinned descendant inside candidate subtree produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39823

Bounded accessible branch expansion eviction: Eviction ignores pinned descendant inside candidate subtree · case 03

Eviction ignores pinned descendant inside candidate subtree produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39824

Bounded accessible branch expansion eviction: Eviction ignores pinned descendant inside candidate subtree · case 04

Eviction ignores pinned descendant inside candidate subtree produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39825

Bounded accessible branch expansion eviction: Eviction ignores pinned descendant inside candidate subtree · case 05

Eviction ignores pinned descendant inside candidate subtree produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39826

Bounded accessible branch expansion eviction: Oversized required path is accepted or invalid request succeeds · case 01

Oversized required path is accepted or invalid request succeeds produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-39827

Bounded accessible branch expansion eviction: Oversized required path is accepted or invalid request succeeds · case 02

Oversized required path is accepted or invalid request succeeds produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39828

Bounded accessible branch expansion eviction: Oversized required path is accepted or invalid request succeeds · case 03

Oversized required path is accepted or invalid request succeeds produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39829

Bounded accessible branch expansion eviction: Oversized required path is accepted or invalid request succeeds · case 04

Oversized required path is accepted or invalid request succeeds produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39830

Bounded accessible branch expansion eviction: Oversized required path is accepted or invalid request succeeds · case 05

Oversized required path is accepted or invalid request succeeds produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39831

Bounded accessible branch expansion eviction: Rejected expansion leaks partial eviction changes · case 01

Rejected expansion leaks partial eviction changes produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-39832

Bounded accessible branch expansion eviction: Rejected expansion leaks partial eviction changes · case 02

Rejected expansion leaks partial eviction changes produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39833

Bounded accessible branch expansion eviction: Rejected expansion leaks partial eviction changes · case 03

Rejected expansion leaks partial eviction changes produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39834

Bounded accessible branch expansion eviction: Rejected expansion leaks partial eviction changes · case 04

Rejected expansion leaks partial eviction changes produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39835

Bounded accessible branch expansion eviction: Rejected expansion leaks partial eviction changes · case 05

Rejected expansion leaks partial eviction changes produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39836

Bounded accessible branch expansion eviction: Rejected request or wrong timestamp corrupts branch recency · case 01

Rejected request or wrong timestamp corrupts branch recency produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-39837

Bounded accessible branch expansion eviction: Rejected request or wrong timestamp corrupts branch recency · case 02

Rejected request or wrong timestamp corrupts branch recency produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39838

Bounded accessible branch expansion eviction: Rejected request or wrong timestamp corrupts branch recency · case 03

Rejected request or wrong timestamp corrupts branch recency produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39839

Bounded accessible branch expansion eviction: Rejected request or wrong timestamp corrupts branch recency · case 04

Rejected request or wrong timestamp corrupts branch recency produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39840

Bounded accessible branch expansion eviction: Rejected request or wrong timestamp corrupts branch recency · case 05

Rejected request or wrong timestamp corrupts branch recency produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39841

Binomial root list is ordered by key instead of rank · case 01

The bounded binomial forest certificate reports an incorrect canonical.

Heap invariants● Open access↗
FA-39842

Binomial root list is ordered by key instead of rank · case 02

The bounded binomial forest certificate reports an incorrect canonical.

Heap invariants◈ Members↗
FA-39843

Binomial root list is ordered by key instead of rank · case 03

The bounded binomial forest certificate reports an incorrect canonical.

Heap invariants◈ Members↗
FA-39844

Binomial root list is ordered by key instead of rank · case 04

The bounded binomial forest certificate reports an incorrect canonical.

Heap invariants◈ Members↗
FA-39845

Binomial root list is ordered by key instead of rank · case 05

The bounded binomial forest certificate reports an incorrect canonical.

Heap invariants◈ Members↗
FA-39846

Binomial consolidation misses equal-rank roots separated in the list · case 01

The bounded binomial forest certificate reports an incorrect collisions.

Heap invariants● Open access↗
FA-39847

Binomial consolidation misses equal-rank roots separated in the list · case 02

The bounded binomial forest certificate reports an incorrect collisions.

Heap invariants◈ Members↗
FA-39848

Binomial consolidation misses equal-rank roots separated in the list · case 03

The bounded binomial forest certificate reports an incorrect collisions.

Heap invariants◈ Members↗
FA-39849

Binomial consolidation misses equal-rank roots separated in the list · case 04

The bounded binomial forest certificate reports an incorrect collisions.

Heap invariants◈ Members↗
FA-39850

Binomial consolidation misses equal-rank roots separated in the list · case 05

The bounded binomial forest certificate reports an incorrect collisions.

Heap invariants◈ Members↗
FA-39851

Binomial minimum pointer is chosen by tree rank · case 01

The bounded binomial forest certificate reports an incorrect minimum.

Heap invariants● Open access↗
FA-39852

Binomial minimum pointer is chosen by tree rank · case 02

The bounded binomial forest certificate reports an incorrect minimum.

Heap invariants◈ Members↗
FA-39853

Binomial minimum pointer is chosen by tree rank · case 03

The bounded binomial forest certificate reports an incorrect minimum.

Heap invariants◈ Members↗
FA-39854

Binomial minimum pointer is chosen by tree rank · case 04

The bounded binomial forest certificate reports an incorrect minimum.

Heap invariants◈ Members↗
FA-39855

Binomial minimum pointer is chosen by tree rank · case 05

The bounded binomial forest certificate reports an incorrect minimum.

Heap invariants◈ Members↗
FA-39856

Binomial forest size sums roots instead of tree populations · case 01

The bounded binomial forest certificate reports an incorrect population.

Heap invariants● Open access↗
FA-39857

Binomial forest size sums roots instead of tree populations · case 02

The bounded binomial forest certificate reports an incorrect population.

Heap invariants◈ Members↗
FA-39858

Binomial forest size sums roots instead of tree populations · case 03

The bounded binomial forest certificate reports an incorrect population.

Heap invariants◈ Members↗
FA-39859

Binomial forest size sums roots instead of tree populations · case 04

The bounded binomial forest certificate reports an incorrect population.

Heap invariants◈ Members↗
FA-39860

Binomial forest size sums roots instead of tree populations · case 05

The bounded binomial forest certificate reports an incorrect population.

Heap invariants◈ Members↗
FA-39861

Binomial rank cardinality treats the exponent as a linear count · case 01

The bounded binomial forest certificate reports an incorrect cardinality.

Heap invariants● Open access↗
FA-39862

Binomial rank cardinality treats the exponent as a linear count · case 02

The bounded binomial forest certificate reports an incorrect cardinality.

Heap invariants◈ Members↗
FA-39863

Binomial rank cardinality treats the exponent as a linear count · case 03

The bounded binomial forest certificate reports an incorrect cardinality.

Heap invariants◈ Members↗
FA-39864

Binomial rank cardinality treats the exponent as a linear count · case 04

The bounded binomial forest certificate reports an incorrect cardinality.

Heap invariants◈ Members↗
FA-39865

Binomial rank cardinality treats the exponent as a linear count · case 05

The bounded binomial forest certificate reports an incorrect cardinality.

Heap invariants◈ Members↗
FA-39866

Binomial child rank chain accepts ascending children · case 01

The bounded binomial forest certificate reports an incorrect children.

Heap invariants● Open access↗
FA-39867

Binomial child rank chain accepts ascending children · case 02

The bounded binomial forest certificate reports an incorrect children.

Heap invariants◈ Members↗
FA-39868

Binomial child rank chain accepts ascending children · case 03

The bounded binomial forest certificate reports an incorrect children.

Heap invariants◈ Members↗
FA-39869

Binomial child rank chain accepts ascending children · case 04

The bounded binomial forest certificate reports an incorrect children.

Heap invariants◈ Members↗
FA-39870

Binomial child rank chain accepts ascending children · case 05

The bounded binomial forest certificate reports an incorrect children.

Heap invariants◈ Members↗
FA-39871

Fibonacci ring traversal verifies only one reciprocal link · case 01

The bounded fibonacci rings certificate reports an incorrect reciprocity.

Heap invariants● Open access↗
FA-39872

Fibonacci ring traversal verifies only one reciprocal link · case 02

The bounded fibonacci rings certificate reports an incorrect reciprocity.

Heap invariants◈ Members↗
FA-39873

Fibonacci ring traversal verifies only one reciprocal link · case 03

The bounded fibonacci rings certificate reports an incorrect reciprocity.

Heap invariants◈ Members↗
FA-39874

Fibonacci ring traversal verifies only one reciprocal link · case 04

The bounded fibonacci rings certificate reports an incorrect reciprocity.

Heap invariants◈ Members↗
FA-39875

Fibonacci ring traversal verifies only one reciprocal link · case 05

The bounded fibonacci rings certificate reports an incorrect reciprocity.

Heap invariants◈ Members↗
FA-39876

Fibonacci child ownership is checked against the grandparent · case 01

The bounded fibonacci rings certificate reports an incorrect backlinks.

Heap invariants● Open access↗
FA-39877

Fibonacci child ownership is checked against the grandparent · case 02

The bounded fibonacci rings certificate reports an incorrect backlinks.

Heap invariants◈ Members↗
FA-39878

Fibonacci child ownership is checked against the grandparent · case 03

The bounded fibonacci rings certificate reports an incorrect backlinks.

Heap invariants◈ Members↗
FA-39879

Fibonacci child ownership is checked against the grandparent · case 04

The bounded fibonacci rings certificate reports an incorrect backlinks.

Heap invariants◈ Members↗
FA-39880

Fibonacci child ownership is checked against the grandparent · case 05

The bounded fibonacci rings certificate reports an incorrect backlinks.

Heap invariants◈ Members↗
FA-39881

Fibonacci degree accepts hidden extra children · case 01

The bounded fibonacci rings certificate reports an incorrect degrees.

Heap invariants● Open access↗
FA-39882

Fibonacci degree accepts hidden extra children · case 02

The bounded fibonacci rings certificate reports an incorrect degrees.

Heap invariants◈ Members↗
FA-39883

Fibonacci degree accepts hidden extra children · case 03

The bounded fibonacci rings certificate reports an incorrect degrees.

Heap invariants◈ Members↗
FA-39884

Fibonacci degree accepts hidden extra children · case 04

The bounded fibonacci rings certificate reports an incorrect degrees.

Heap invariants◈ Members↗
FA-39885

Fibonacci degree accepts hidden extra children · case 05

The bounded fibonacci rings certificate reports an incorrect degrees.

Heap invariants◈ Members↗
FA-39886

Fibonacci promoted roots retain a loss mark · case 01

The bounded fibonacci rings certificate reports an incorrect root marks.

Heap invariants● Open access↗
FA-39887

Fibonacci promoted roots retain a loss mark · case 02

The bounded fibonacci rings certificate reports an incorrect root marks.

Heap invariants◈ Members↗
FA-39888

Fibonacci promoted roots retain a loss mark · case 03

The bounded fibonacci rings certificate reports an incorrect root marks.

Heap invariants◈ Members↗
FA-39889

Fibonacci promoted roots retain a loss mark · case 04

The bounded fibonacci rings certificate reports an incorrect root marks.

Heap invariants◈ Members↗
FA-39890

Fibonacci promoted roots retain a loss mark · case 05

The bounded fibonacci rings certificate reports an incorrect root marks.

Heap invariants◈ Members↗
FA-39891

Fibonacci root detection mistakes a self-ring for a root · case 01

The bounded fibonacci rings certificate reports an incorrect root ids.

Heap invariants● Open access↗
FA-39892

Fibonacci root detection mistakes a self-ring for a root · case 02

The bounded fibonacci rings certificate reports an incorrect root ids.

Heap invariants◈ Members↗
FA-39893

Fibonacci root detection mistakes a self-ring for a root · case 03

The bounded fibonacci rings certificate reports an incorrect root ids.

Heap invariants◈ Members↗
FA-39894

Fibonacci root detection mistakes a self-ring for a root · case 04

The bounded fibonacci rings certificate reports an incorrect root ids.

Heap invariants◈ Members↗
FA-39895

Fibonacci root detection mistakes a self-ring for a root · case 05

The bounded fibonacci rings certificate reports an incorrect root ids.

Heap invariants◈ Members↗
FA-39896

Fibonacci minimum certificate accepts a minimum-valued child · case 01

The bounded fibonacci rings certificate reports an incorrect minimum valid.

Heap invariants● Open access↗
FA-39897

Fibonacci minimum certificate accepts a minimum-valued child · case 02

The bounded fibonacci rings certificate reports an incorrect minimum valid.

Heap invariants◈ Members↗
FA-39898

Fibonacci minimum certificate accepts a minimum-valued child · case 03

The bounded fibonacci rings certificate reports an incorrect minimum valid.

Heap invariants◈ Members↗
FA-39899

Fibonacci minimum certificate accepts a minimum-valued child · case 04

The bounded fibonacci rings certificate reports an incorrect minimum valid.

Heap invariants◈ Members↗
FA-39900

Fibonacci minimum certificate accepts a minimum-valued child · case 05

The bounded fibonacci rings certificate reports an incorrect minimum valid.

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 ↗