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

A buy order matches its own owner · case 01

A buy order matches its own owner.

Auction allocation rules● Open access↗
FA-12702

A buy order matches its own owner · case 02

A buy order matches its own owner.

Auction allocation rules◈ Members↗
FA-12703

A buy order matches its own owner · case 03

A buy order matches its own owner.

Auction allocation rules◈ Members↗
FA-12704

A buy order matches its own owner · case 04

A buy order matches its own owner.

Auction allocation rules◈ Members↗
FA-12705

A buy order matches its own owner · case 05

A buy order matches its own owner.

Auction allocation rules◈ Members↗
FA-12706

A block request receives a forbidden partial allocation · case 01

A block request receives a forbidden partial allocation.

Auction allocation rules● Open access↗
FA-12707

A block request receives a forbidden partial allocation · case 02

A block request receives a forbidden partial allocation.

Auction allocation rules◈ Members↗
FA-12708

A block request receives a forbidden partial allocation · case 03

A block request receives a forbidden partial allocation.

Auction allocation rules◈ Members↗
FA-12709

A block request receives a forbidden partial allocation · case 04

A block request receives a forbidden partial allocation.

Auction allocation rules◈ Members↗
FA-12710

A block request receives a forbidden partial allocation · case 05

A block request receives a forbidden partial allocation.

Auction allocation rules◈ Members↗
FA-12711

Pay-as-bid settlement treats every fill as one unit · case 01

Pay-as-bid settlement treats every fill as one unit.

Auction allocation rules● Open access↗
FA-12712

Pay-as-bid settlement treats every fill as one unit · case 02

Pay-as-bid settlement treats every fill as one unit.

Auction allocation rules◈ Members↗
FA-12713

Pay-as-bid settlement treats every fill as one unit · case 03

Pay-as-bid settlement treats every fill as one unit.

Auction allocation rules◈ Members↗
FA-12714

Pay-as-bid settlement treats every fill as one unit · case 04

Pay-as-bid settlement treats every fill as one unit.

Auction allocation rules◈ Members↗
FA-12715

Pay-as-bid settlement treats every fill as one unit · case 05

Pay-as-bid settlement treats every fill as one unit.

Auction allocation rules◈ Members↗
FA-12716

One bidder wins two mutually exclusive package offers · case 01

One bidder wins two mutually exclusive package offers.

Auction allocation rules● Open access↗
FA-12717

One bidder wins two mutually exclusive package offers · case 02

One bidder wins two mutually exclusive package offers.

Auction allocation rules◈ Members↗
FA-12718

One bidder wins two mutually exclusive package offers · case 03

One bidder wins two mutually exclusive package offers.

Auction allocation rules◈ Members↗
FA-12719

One bidder wins two mutually exclusive package offers · case 04

One bidder wins two mutually exclusive package offers.

Auction allocation rules◈ Members↗
FA-12720

One bidder wins two mutually exclusive package offers · case 05

One bidder wins two mutually exclusive package offers.

Auction allocation rules◈ Members↗
FA-12721

Equal-price buy and sell limits fail to cross · case 01

Equal-price buy and sell limits fail to cross.

Auction allocation rules● Open access↗
FA-12722

Equal-price buy and sell limits fail to cross · case 02

Equal-price buy and sell limits fail to cross.

Auction allocation rules◈ Members↗
FA-12723

Equal-price buy and sell limits fail to cross · case 03

Equal-price buy and sell limits fail to cross.

Auction allocation rules◈ Members↗
FA-12724

Equal-price buy and sell limits fail to cross · case 04

Equal-price buy and sell limits fail to cross.

Auction allocation rules◈ Members↗
FA-12725

Equal-price buy and sell limits fail to cross · case 05

Equal-price buy and sell limits fail to cross.

Auction allocation rules◈ Members↗
FA-12726

Marginal pro-rata allocation loses residual units · case 01

Marginal pro-rata allocation loses residual units.

Auction allocation rules● Open access↗
FA-12727

Marginal pro-rata allocation loses residual units · case 02

Marginal pro-rata allocation loses residual units.

Auction allocation rules◈ Members↗
FA-12728

Marginal pro-rata allocation loses residual units · case 03

Marginal pro-rata allocation loses residual units.

Auction allocation rules◈ Members↗
FA-12729

Marginal pro-rata allocation loses residual units · case 04

Marginal pro-rata allocation loses residual units.

Auction allocation rules◈ Members↗
FA-12730

Marginal pro-rata allocation loses residual units · case 05

Marginal pro-rata allocation loses residual units.

Auction allocation rules◈ Members↗
FA-12731

Call clearing chooses peak demand instead of executable volume · case 01

Call clearing chooses peak demand instead of executable volume.

Auction allocation rules● Open access↗
FA-12732

Call clearing chooses peak demand instead of executable volume · case 02

Call clearing chooses peak demand instead of executable volume.

Auction allocation rules◈ Members↗
FA-12733

Call clearing chooses peak demand instead of executable volume · case 03

Call clearing chooses peak demand instead of executable volume.

Auction allocation rules◈ Members↗
FA-12734

Call clearing chooses peak demand instead of executable volume · case 04

Call clearing chooses peak demand instead of executable volume.

Auction allocation rules◈ Members↗
FA-12735

Call clearing chooses peak demand instead of executable volume · case 05

Call clearing chooses peak demand instead of executable volume.

Auction allocation rules◈ Members↗
FA-12736

A minimum-fill order is rejected despite sufficient aggregate counterparties · case 01

A minimum-fill order is rejected despite sufficient aggregate counterparties.

Auction allocation rules● Open access↗
FA-12737

A minimum-fill order is rejected despite sufficient aggregate counterparties · case 02

A minimum-fill order is rejected despite sufficient aggregate counterparties.

Auction allocation rules◈ Members↗
FA-12738

A minimum-fill order is rejected despite sufficient aggregate counterparties · case 03

A minimum-fill order is rejected despite sufficient aggregate counterparties.

Auction allocation rules◈ Members↗
FA-12739

A minimum-fill order is rejected despite sufficient aggregate counterparties · case 04

A minimum-fill order is rejected despite sufficient aggregate counterparties.

Auction allocation rules◈ Members↗
FA-12740

A minimum-fill order is rejected despite sufficient aggregate counterparties · case 05

A minimum-fill order is rejected despite sufficient aggregate counterparties.

Auction allocation rules◈ Members↗
FA-12741

Truncated rankings change the Borda point scale · case 01

Truncated rankings change the Borda point scale.

Voting rule computation● Open access↗
FA-12742

Truncated rankings change the Borda point scale · case 02

Truncated rankings change the Borda point scale.

Voting rule computation◈ Members↗
FA-12743

Truncated rankings change the Borda point scale · case 03

Truncated rankings change the Borda point scale.

Voting rule computation◈ Members↗
FA-12744

Truncated rankings change the Borda point scale · case 04

Truncated rankings change the Borda point scale.

Voting rule computation◈ Members↗
FA-12745

Truncated rankings change the Borda point scale · case 05

Truncated rankings change the Borda point scale.

Voting rule computation◈ Members↗
FA-12746

Two omitted candidates acquire a fictitious pairwise preference · case 01

Two omitted candidates acquire a fictitious pairwise preference.

Voting rule computation● Open access↗
FA-12747

Two omitted candidates acquire a fictitious pairwise preference · case 02

Two omitted candidates acquire a fictitious pairwise preference.

Voting rule computation◈ Members↗
FA-12748

Two omitted candidates acquire a fictitious pairwise preference · case 03

Two omitted candidates acquire a fictitious pairwise preference.

Voting rule computation◈ Members↗
FA-12749

Two omitted candidates acquire a fictitious pairwise preference · case 04

Two omitted candidates acquire a fictitious pairwise preference.

Voting rule computation◈ Members↗
FA-12750

Two omitted candidates acquire a fictitious pairwise preference · case 05

Two omitted candidates acquire a fictitious pairwise preference.

Voting rule computation◈ Members↗
FA-12751

Exhausted ballots prevent a continuing-ballot majority · case 01

Exhausted ballots prevent a continuing-ballot majority.

Voting rule computation● Open access↗
FA-12752

Exhausted ballots prevent a continuing-ballot majority · case 02

Exhausted ballots prevent a continuing-ballot majority.

Voting rule computation◈ Members↗
FA-12753

Exhausted ballots prevent a continuing-ballot majority · case 03

Exhausted ballots prevent a continuing-ballot majority.

Voting rule computation◈ Members↗
FA-12754

Exhausted ballots prevent a continuing-ballot majority · case 04

Exhausted ballots prevent a continuing-ballot majority.

Voting rule computation◈ Members↗
FA-12755

Exhausted ballots prevent a continuing-ballot majority · case 05

Exhausted ballots prevent a continuing-ballot majority.

Voting rule computation◈ Members↗
FA-12756

A transferred ranking stops at another eliminated candidate · case 01

A transferred ranking stops at another eliminated candidate.

Voting rule computation● Open access↗
FA-12757

A transferred ranking stops at another eliminated candidate · case 02

A transferred ranking stops at another eliminated candidate.

Voting rule computation◈ Members↗
FA-12758

A transferred ranking stops at another eliminated candidate · case 03

A transferred ranking stops at another eliminated candidate.

Voting rule computation◈ Members↗
FA-12759

A transferred ranking stops at another eliminated candidate · case 04

A transferred ranking stops at another eliminated candidate.

Voting rule computation◈ Members↗
FA-12760

A transferred ranking stops at another eliminated candidate · case 05

A transferred ranking stops at another eliminated candidate.

Voting rule computation◈ Members↗
FA-12761

An exact quotient omits the final quota increment · case 01

An exact quotient omits the final quota increment.

Voting rule computation● Open access↗
FA-12762

An exact quotient omits the final quota increment · case 02

An exact quotient omits the final quota increment.

Voting rule computation◈ Members↗
FA-12763

An exact quotient omits the final quota increment · case 03

An exact quotient omits the final quota increment.

Voting rule computation◈ Members↗
FA-12764

An exact quotient omits the final quota increment · case 04

An exact quotient omits the final quota increment.

Voting rule computation◈ Members↗
FA-12765

An exact quotient omits the final quota increment · case 05

An exact quotient omits the final quota increment.

Voting rule computation◈ Members↗
FA-12766

Surplus transfer uses ballot count instead of ballot value · case 01

Surplus transfer uses ballot count instead of ballot value.

Voting rule computation● Open access↗
FA-12767

Surplus transfer uses ballot count instead of ballot value · case 02

Surplus transfer uses ballot count instead of ballot value.

Voting rule computation◈ Members↗
FA-12768

Surplus transfer uses ballot count instead of ballot value · case 03

Surplus transfer uses ballot count instead of ballot value.

Voting rule computation◈ Members↗
FA-12769

Surplus transfer uses ballot count instead of ballot value · case 04

Surplus transfer uses ballot count instead of ballot value.

Voting rule computation◈ Members↗
FA-12770

Surplus transfer uses ballot count instead of ballot value · case 05

Surplus transfer uses ballot count instead of ballot value.

Voting rule computation◈ Members↗
FA-12771

Sequential divisor allocation reuses initial priorities · case 01

Sequential divisor allocation reuses initial priorities.

Voting rule computation● Open access↗
FA-12772

Sequential divisor allocation reuses initial priorities · case 02

Sequential divisor allocation reuses initial priorities.

Voting rule computation◈ Members↗
FA-12773

Sequential divisor allocation reuses initial priorities · case 03

Sequential divisor allocation reuses initial priorities.

Voting rule computation◈ Members↗
FA-12774

Sequential divisor allocation reuses initial priorities · case 04

Sequential divisor allocation reuses initial priorities.

Voting rule computation◈ Members↗
FA-12775

Sequential divisor allocation reuses initial priorities · case 05

Sequential divisor allocation reuses initial priorities.

Voting rule computation◈ Members↗
FA-12776

A tied rank consumes only one scoring position · case 01

A tied rank consumes only one scoring position.

Voting rule computation● Open access↗
FA-12777

A tied rank consumes only one scoring position · case 02

A tied rank consumes only one scoring position.

Voting rule computation◈ Members↗
FA-12778

A tied rank consumes only one scoring position · case 03

A tied rank consumes only one scoring position.

Voting rule computation◈ Members↗
FA-12779

A tied rank consumes only one scoring position · case 04

A tied rank consumes only one scoring position.

Voting rule computation◈ Members↗
FA-12780

A tied rank consumes only one scoring position · case 05

A tied rank consumes only one scoring position.

Voting rule computation◈ Members↗
FA-12781

A plurality of pairwise victories is mistaken for beating every opponent · case 01

A plurality of pairwise victories is mistaken for beating every opponent.

Voting rule computation● Open access↗
FA-12782

A plurality of pairwise victories is mistaken for beating every opponent · case 02

A plurality of pairwise victories is mistaken for beating every opponent.

Voting rule computation◈ Members↗
FA-12783

A plurality of pairwise victories is mistaken for beating every opponent · case 03

A plurality of pairwise victories is mistaken for beating every opponent.

Voting rule computation◈ Members↗
FA-12784

A plurality of pairwise victories is mistaken for beating every opponent · case 04

A plurality of pairwise victories is mistaken for beating every opponent.

Voting rule computation◈ Members↗
FA-12785

A plurality of pairwise victories is mistaken for beating every opponent · case 05

A plurality of pairwise victories is mistaken for beating every opponent.

Voting rule computation◈ Members↗
FA-12786

Locking a ranked pair closes an indirect preference cycle · case 01

Locking a ranked pair closes an indirect preference cycle.

Voting rule computation● Open access↗
FA-12787

Locking a ranked pair closes an indirect preference cycle · case 02

Locking a ranked pair closes an indirect preference cycle.

Voting rule computation◈ Members↗
FA-12788

Locking a ranked pair closes an indirect preference cycle · case 03

Locking a ranked pair closes an indirect preference cycle.

Voting rule computation◈ Members↗
FA-12789

Locking a ranked pair closes an indirect preference cycle · case 04

Locking a ranked pair closes an indirect preference cycle.

Voting rule computation◈ Members↗
FA-12790

Locking a ranked pair closes an indirect preference cycle · case 05

Locking a ranked pair closes an indirect preference cycle.

Voting rule computation◈ Members↗
FA-12791

Bye selection ignores prior byes · case 01

Bye selection ignores prior byes.

Tournament pairing rules● Open access↗
FA-12792

Bye selection ignores prior byes · case 02

Bye selection ignores prior byes.

Tournament pairing rules◈ Members↗
FA-12793

Bye selection ignores prior byes · case 03

Bye selection ignores prior byes.

Tournament pairing rules◈ Members↗
FA-12794

Bye selection ignores prior byes · case 04

Bye selection ignores prior byes.

Tournament pairing rules◈ Members↗
FA-12795

Bye selection ignores prior byes · case 05

Bye selection ignores prior byes.

Tournament pairing rules◈ Members↗
FA-12796

Greedy pairing strands the final entrants · case 01

Greedy pairing strands the final entrants.

Tournament pairing rules● Open access↗
FA-12797

Greedy pairing strands the final entrants · case 02

Greedy pairing strands the final entrants.

Tournament pairing rules◈ Members↗
FA-12798

Greedy pairing strands the final entrants · case 03

Greedy pairing strands the final entrants.

Tournament pairing rules◈ Members↗
FA-12799

Greedy pairing strands the final entrants · case 04

Greedy pairing strands the final entrants.

Tournament pairing rules◈ Members↗
FA-12800

Greedy pairing strands the final entrants · case 05

Greedy pairing strands the final entrants.

Tournament pairing rules◈ 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 ↗