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

Loser tree exhausted sentinels cannot win on their stale key · case 01

The bounded loser match certificate reports an incorrect winner.

Heap invariants● Open access↗
FA-40502

Loser tree exhausted sentinels cannot win on their stale key · case 02

The bounded loser match certificate reports an incorrect winner.

Heap invariants◈ Members↗
FA-40503

Loser tree exhausted sentinels cannot win on their stale key · case 03

The bounded loser match certificate reports an incorrect winner.

Heap invariants◈ Members↗
FA-40504

Loser tree exhausted sentinels cannot win on their stale key · case 04

The bounded loser match certificate reports an incorrect winner.

Heap invariants◈ Members↗
FA-40505

Loser tree exhausted sentinels cannot win on their stale key · case 05

The bounded loser match certificate reports an incorrect winner.

Heap invariants◈ Members↗
FA-40506

Loser tree internal node stores the losing run rather than the winner · case 01

The bounded loser match certificate reports an incorrect stored loser.

Heap invariants● Open access↗
FA-40507

Loser tree internal node stores the losing run rather than the winner · case 02

The bounded loser match certificate reports an incorrect stored loser.

Heap invariants◈ Members↗
FA-40508

Loser tree internal node stores the losing run rather than the winner · case 03

The bounded loser match certificate reports an incorrect stored loser.

Heap invariants◈ Members↗
FA-40509

Loser tree internal node stores the losing run rather than the winner · case 04

The bounded loser match certificate reports an incorrect stored loser.

Heap invariants◈ Members↗
FA-40510

Loser tree internal node stores the losing run rather than the winner · case 05

The bounded loser match certificate reports an incorrect stored loser.

Heap invariants◈ Members↗
FA-40511

Loser tree counts a key comparison only when both runs are active · case 01

The bounded loser match certificate reports an incorrect comparisons.

Heap invariants● Open access↗
FA-40512

Loser tree counts a key comparison only when both runs are active · case 02

The bounded loser match certificate reports an incorrect comparisons.

Heap invariants◈ Members↗
FA-40513

Loser tree counts a key comparison only when both runs are active · case 03

The bounded loser match certificate reports an incorrect comparisons.

Heap invariants◈ Members↗
FA-40514

Loser tree counts a key comparison only when both runs are active · case 04

The bounded loser match certificate reports an incorrect comparisons.

Heap invariants◈ Members↗
FA-40515

Loser tree counts a key comparison only when both runs are active · case 05

The bounded loser match certificate reports an incorrect comparisons.

Heap invariants◈ Members↗
FA-40516

Loser tree exhaustion is explicit and independent of legitimate zero keys · case 01

The bounded loser match certificate reports an incorrect exhausted.

Heap invariants● Open access↗
FA-40517

Loser tree exhaustion is explicit and independent of legitimate zero keys · case 02

The bounded loser match certificate reports an incorrect exhausted.

Heap invariants◈ Members↗
FA-40518

Loser tree exhaustion is explicit and independent of legitimate zero keys · case 03

The bounded loser match certificate reports an incorrect exhausted.

Heap invariants◈ Members↗
FA-40519

Loser tree exhaustion is explicit and independent of legitimate zero keys · case 04

The bounded loser match certificate reports an incorrect exhausted.

Heap invariants◈ Members↗
FA-40520

Loser tree exhaustion is explicit and independent of legitimate zero keys · case 05

The bounded loser match certificate reports an incorrect exhausted.

Heap invariants◈ Members↗
FA-40521

Loser tree output key belongs to the active winner · case 01

The bounded loser match certificate reports an incorrect key.

Heap invariants● Open access↗
FA-40522

Loser tree output key belongs to the active winner · case 02

The bounded loser match certificate reports an incorrect key.

Heap invariants◈ Members↗
FA-40523

Loser tree output key belongs to the active winner · case 03

The bounded loser match certificate reports an incorrect key.

Heap invariants◈ Members↗
FA-40524

Loser tree output key belongs to the active winner · case 04

The bounded loser match certificate reports an incorrect key.

Heap invariants◈ Members↗
FA-40525

Loser tree output key belongs to the active winner · case 05

The bounded loser match certificate reports an incorrect key.

Heap invariants◈ Members↗
FA-40526

Loser tree propagates the winner to the next match rather than the stored loser · case 01

The bounded loser match certificate reports an incorrect continuation.

Heap invariants● Open access↗
FA-40527

Loser tree propagates the winner to the next match rather than the stored loser · case 02

The bounded loser match certificate reports an incorrect continuation.

Heap invariants◈ Members↗
FA-40528

Loser tree propagates the winner to the next match rather than the stored loser · case 03

The bounded loser match certificate reports an incorrect continuation.

Heap invariants◈ Members↗
FA-40529

Loser tree propagates the winner to the next match rather than the stored loser · case 04

The bounded loser match certificate reports an incorrect continuation.

Heap invariants◈ Members↗
FA-40530

Loser tree propagates the winner to the next match rather than the stored loser · case 05

The bounded loser match certificate reports an incorrect continuation.

Heap invariants◈ Members↗
FA-40531

Weak heap distinguished ancestor can be above the ordinary parent · case 01

The bounded weak ancestor certificate reports an incorrect ancestor.

Heap invariants● Open access↗
FA-40532

Weak heap distinguished ancestor can be above the ordinary parent · case 02

The bounded weak ancestor certificate reports an incorrect ancestor.

Heap invariants◈ Members↗
FA-40533

Weak heap distinguished ancestor can be above the ordinary parent · case 03

The bounded weak ancestor certificate reports an incorrect ancestor.

Heap invariants◈ Members↗
FA-40534

Weak heap distinguished ancestor can be above the ordinary parent · case 04

The bounded weak ancestor certificate reports an incorrect ancestor.

Heap invariants◈ Members↗
FA-40535

Weak heap distinguished ancestor can be above the ordinary parent · case 05

The bounded weak ancestor certificate reports an incorrect ancestor.

Heap invariants◈ Members↗
FA-40536

Weak heap ancestor search records climbed nodes from descendant upward · case 01

The bounded weak ancestor certificate reports an incorrect path.

Heap invariants● Open access↗
FA-40537

Weak heap ancestor search records climbed nodes from descendant upward · case 02

The bounded weak ancestor certificate reports an incorrect path.

Heap invariants◈ Members↗
FA-40538

Weak heap ancestor search records climbed nodes from descendant upward · case 03

The bounded weak ancestor certificate reports an incorrect path.

Heap invariants◈ Members↗
FA-40539

Weak heap ancestor search records climbed nodes from descendant upward · case 04

The bounded weak ancestor certificate reports an incorrect path.

Heap invariants◈ Members↗
FA-40540

Weak heap ancestor search records climbed nodes from descendant upward · case 05

The bounded weak ancestor certificate reports an incorrect path.

Heap invariants◈ Members↗
FA-40541

Weak heap ancestor cost counts only orientation-driven climbs · case 01

The bounded weak ancestor certificate reports an incorrect cost.

Heap invariants● Open access↗
FA-40542

Weak heap ancestor cost counts only orientation-driven climbs · case 02

The bounded weak ancestor certificate reports an incorrect cost.

Heap invariants◈ Members↗
FA-40543

Weak heap ancestor cost counts only orientation-driven climbs · case 03

The bounded weak ancestor certificate reports an incorrect cost.

Heap invariants◈ Members↗
FA-40544

Weak heap ancestor cost counts only orientation-driven climbs · case 04

The bounded weak ancestor certificate reports an incorrect cost.

Heap invariants◈ Members↗
FA-40545

Weak heap ancestor cost counts only orientation-driven climbs · case 05

The bounded weak ancestor certificate reports an incorrect cost.

Heap invariants◈ Members↗
FA-40546

Weak heap distinguished-ancestor search retains the stopping child separately · case 01

The bounded weak ancestor certificate reports an incorrect stop.

Heap invariants● Open access↗
FA-40547

Weak heap distinguished-ancestor search retains the stopping child separately · case 02

The bounded weak ancestor certificate reports an incorrect stop.

Heap invariants◈ Members↗
FA-40548

Weak heap distinguished-ancestor search retains the stopping child separately · case 03

The bounded weak ancestor certificate reports an incorrect stop.

Heap invariants◈ Members↗
FA-40549

Weak heap distinguished-ancestor search retains the stopping child separately · case 04

The bounded weak ancestor certificate reports an incorrect stop.

Heap invariants◈ Members↗
FA-40550

Weak heap distinguished-ancestor search retains the stopping child separately · case 05

The bounded weak ancestor certificate reports an incorrect stop.

Heap invariants◈ Members↗
FA-40551

Weak heap stopping orientation belongs to the distinguished ancestor · case 01

The bounded weak ancestor certificate reports an incorrect orientation.

Heap invariants● Open access↗
FA-40552

Weak heap stopping orientation belongs to the distinguished ancestor · case 02

The bounded weak ancestor certificate reports an incorrect orientation.

Heap invariants◈ Members↗
FA-40553

Weak heap stopping orientation belongs to the distinguished ancestor · case 03

The bounded weak ancestor certificate reports an incorrect orientation.

Heap invariants◈ Members↗
FA-40554

Weak heap stopping orientation belongs to the distinguished ancestor · case 04

The bounded weak ancestor certificate reports an incorrect orientation.

Heap invariants◈ Members↗
FA-40555

Weak heap stopping orientation belongs to the distinguished ancestor · case 05

The bounded weak ancestor certificate reports an incorrect orientation.

Heap invariants◈ Members↗
FA-40556

Weak heap direct ancestry depends on reversal bits as well as index parity · case 01

The bounded weak ancestor certificate reports an incorrect direct.

Heap invariants● Open access↗
FA-40557

Weak heap direct ancestry depends on reversal bits as well as index parity · case 02

The bounded weak ancestor certificate reports an incorrect direct.

Heap invariants◈ Members↗
FA-40558

Weak heap direct ancestry depends on reversal bits as well as index parity · case 03

The bounded weak ancestor certificate reports an incorrect direct.

Heap invariants◈ Members↗
FA-40559

Weak heap direct ancestry depends on reversal bits as well as index parity · case 04

The bounded weak ancestor certificate reports an incorrect direct.

Heap invariants◈ Members↗
FA-40560

Weak heap direct ancestry depends on reversal bits as well as index parity · case 05

The bounded weak ancestor certificate reports an incorrect direct.

Heap invariants◈ Members↗
FA-40561

Weak join preserves both exchanged keys instead of overwriting the ancestor · case 01

The bounded weak join certificate reports an incorrect keys.

Heap invariants● Open access↗
FA-40562

Weak join preserves both exchanged keys instead of overwriting the ancestor · case 02

The bounded weak join certificate reports an incorrect keys.

Heap invariants◈ Members↗
FA-40563

Weak join preserves both exchanged keys instead of overwriting the ancestor · case 03

The bounded weak join certificate reports an incorrect keys.

Heap invariants◈ Members↗
FA-40564

Weak join preserves both exchanged keys instead of overwriting the ancestor · case 04

The bounded weak join certificate reports an incorrect keys.

Heap invariants◈ Members↗
FA-40565

Weak join preserves both exchanged keys instead of overwriting the ancestor · case 05

The bounded weak join certificate reports an incorrect keys.

Heap invariants◈ Members↗
FA-40566

Weak join flips only the descendant reversal bit · case 01

The bounded weak join certificate reports an incorrect bits.

Heap invariants● Open access↗
FA-40567

Weak join flips only the descendant reversal bit · case 02

The bounded weak join certificate reports an incorrect bits.

Heap invariants◈ Members↗
FA-40568

Weak join flips only the descendant reversal bit · case 03

The bounded weak join certificate reports an incorrect bits.

Heap invariants◈ Members↗
FA-40569

Weak join flips only the descendant reversal bit · case 04

The bounded weak join certificate reports an incorrect bits.

Heap invariants◈ Members↗
FA-40570

Weak join flips only the descendant reversal bit · case 05

The bounded weak join certificate reports an incorrect bits.

Heap invariants◈ Members↗
FA-40571

Weak join performs a strict improvement swap without reversing equal keys · case 01

The bounded weak join certificate reports an incorrect swapped.

Heap invariants● Open access↗
FA-40572

Weak join performs a strict improvement swap without reversing equal keys · case 02

The bounded weak join certificate reports an incorrect swapped.

Heap invariants◈ Members↗
FA-40573

Weak join performs a strict improvement swap without reversing equal keys · case 03

The bounded weak join certificate reports an incorrect swapped.

Heap invariants◈ Members↗
FA-40574

Weak join performs a strict improvement swap without reversing equal keys · case 04

The bounded weak join certificate reports an incorrect swapped.

Heap invariants◈ Members↗
FA-40575

Weak join performs a strict improvement swap without reversing equal keys · case 05

The bounded weak join certificate reports an incorrect swapped.

Heap invariants◈ Members↗
FA-40576

Weak join winner is local to the two participating nodes · case 01

The bounded weak join certificate reports an incorrect winner key.

Heap invariants● Open access↗
FA-40577

Weak join winner is local to the two participating nodes · case 02

The bounded weak join certificate reports an incorrect winner key.

Heap invariants◈ Members↗
FA-40578

Weak join winner is local to the two participating nodes · case 03

The bounded weak join certificate reports an incorrect winner key.

Heap invariants◈ Members↗
FA-40579

Weak join winner is local to the two participating nodes · case 04

The bounded weak join certificate reports an incorrect winner key.

Heap invariants◈ Members↗
FA-40580

Weak join winner is local to the two participating nodes · case 05

The bounded weak join certificate reports an incorrect winner key.

Heap invariants◈ Members↗
FA-40581

Weak join reports no orientation mutation when no exchange occurs · case 01

The bounded weak join certificate reports an incorrect flipped.

Heap invariants● Open access↗
FA-40582

Weak join reports no orientation mutation when no exchange occurs · case 02

The bounded weak join certificate reports an incorrect flipped.

Heap invariants◈ Members↗
FA-40583

Weak join reports no orientation mutation when no exchange occurs · case 03

The bounded weak join certificate reports an incorrect flipped.

Heap invariants◈ Members↗
FA-40584

Weak join reports no orientation mutation when no exchange occurs · case 04

The bounded weak join certificate reports an incorrect flipped.

Heap invariants◈ Members↗
FA-40585

Weak join reports no orientation mutation when no exchange occurs · case 05

The bounded weak join certificate reports an incorrect flipped.

Heap invariants◈ Members↗
FA-40586

Weak join makes one comparison independently of distance and swap outcome · case 01

The bounded weak join certificate reports an incorrect comparisons.

Heap invariants● Open access↗
FA-40587

Weak join makes one comparison independently of distance and swap outcome · case 02

The bounded weak join certificate reports an incorrect comparisons.

Heap invariants◈ Members↗
FA-40588

Weak join makes one comparison independently of distance and swap outcome · case 03

The bounded weak join certificate reports an incorrect comparisons.

Heap invariants◈ Members↗
FA-40589

Weak join makes one comparison independently of distance and swap outcome · case 04

The bounded weak join certificate reports an incorrect comparisons.

Heap invariants◈ Members↗
FA-40590

Weak join makes one comparison independently of distance and swap outcome · case 05

The bounded weak join certificate reports an incorrect comparisons.

Heap invariants◈ Members↗
FA-40591

Bottom-up heap construction repairs descendants before their parents and excludes leaves · case 01

The bounded bottomup schedule certificate reports an incorrect schedule.

Heap invariants● Open access↗
FA-40592

Bottom-up heap construction repairs descendants before their parents and excludes leaves · case 02

The bounded bottomup schedule certificate reports an incorrect schedule.

Heap invariants◈ Members↗
FA-40593

Bottom-up heap construction repairs descendants before their parents and excludes leaves · case 03

The bounded bottomup schedule certificate reports an incorrect schedule.

Heap invariants◈ Members↗
FA-40594

Bottom-up heap construction repairs descendants before their parents and excludes leaves · case 04

The bounded bottomup schedule certificate reports an incorrect schedule.

Heap invariants◈ Members↗
FA-40595

Bottom-up heap construction repairs descendants before their parents and excludes leaves · case 05

The bounded bottomup schedule certificate reports an incorrect schedule.

Heap invariants◈ Members↗
FA-40596

Complete heap leaf boundary includes the middle node in an odd-size tree · case 01

The bounded bottomup schedule certificate reports an incorrect leaves.

Heap invariants● Open access↗
FA-40597

Complete heap leaf boundary includes the middle node in an odd-size tree · case 02

The bounded bottomup schedule certificate reports an incorrect leaves.

Heap invariants◈ Members↗
FA-40598

Complete heap leaf boundary includes the middle node in an odd-size tree · case 03

The bounded bottomup schedule certificate reports an incorrect leaves.

Heap invariants◈ Members↗
FA-40599

Complete heap leaf boundary includes the middle node in an odd-size tree · case 04

The bounded bottomup schedule certificate reports an incorrect leaves.

Heap invariants◈ Members↗
FA-40600

Complete heap leaf boundary includes the middle node in an odd-size tree · case 05

The bounded bottomup schedule certificate reports an incorrect leaves.

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 ↗