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

Welding compares faces without canonical rotation · case 01

The same face listed from a different start corner is kept twice.

Mesh topology invariants● Open access↗
FA-88602

Welding compares faces without canonical rotation · case 02

The same face listed from a different start corner is kept twice.

Mesh topology invariants◈ Members↗
FA-88603

Welding compares faces without canonical rotation · case 03

The same face listed from a different start corner is kept twice.

Mesh topology invariants◈ Members↗
FA-88604

Welding compares faces without canonical rotation · case 04

The same face listed from a different start corner is kept twice.

Mesh topology invariants◈ Members↗
FA-88605

Welding compares faces without canonical rotation · case 05

The same face listed from a different start corner is kept twice.

Mesh topology invariants◈ Members↗
FA-88606

Welding judges collapse on the original face size · case 01

Faces that weld down to one or two corners are kept.

Mesh topology invariants● Open access↗
FA-88607

Welding judges collapse on the original face size · case 02

Faces that weld down to one or two corners are kept.

Mesh topology invariants◈ Members↗
FA-88608

Welding judges collapse on the original face size · case 03

Faces that weld down to one or two corners are kept.

Mesh topology invariants◈ Members↗
FA-88609

Welding judges collapse on the original face size · case 04

Faces that weld down to one or two corners are kept.

Mesh topology invariants◈ Members↗
FA-88610

Welding judges collapse on the original face size · case 05

Faces that weld down to one or two corners are kept.

Mesh topology invariants◈ Members↗
FA-88611

Fan triangulation reverses triangle winding · case 01

Every generated triangle faces the opposite way from its polygon.

Mesh topology invariants● Open access↗
FA-88612

Fan triangulation reverses triangle winding · case 02

Every generated triangle faces the opposite way from its polygon.

Mesh topology invariants◈ Members↗
FA-88613

Fan triangulation reverses triangle winding · case 03

Every generated triangle faces the opposite way from its polygon.

Mesh topology invariants◈ Members↗
FA-88614

Fan triangulation reverses triangle winding · case 04

Every generated triangle faces the opposite way from its polygon.

Mesh topology invariants◈ Members↗
FA-88615

Fan triangulation reverses triangle winding · case 05

Every generated triangle faces the opposite way from its polygon.

Mesh topology invariants◈ Members↗
FA-88616

Fan triangulation drops the last triangle of each polygon · case 01

Quads become single triangles and polygons leave a hole.

Mesh topology invariants● Open access↗
FA-88617

Fan triangulation drops the last triangle of each polygon · case 02

Quads become single triangles and polygons leave a hole.

Mesh topology invariants◈ Members↗
FA-88618

Fan triangulation drops the last triangle of each polygon · case 03

Quads become single triangles and polygons leave a hole.

Mesh topology invariants◈ Members↗
FA-88619

Fan triangulation drops the last triangle of each polygon · case 04

Quads become single triangles and polygons leave a hole.

Mesh topology invariants◈ Members↗
FA-88620

Fan triangulation drops the last triangle of each polygon · case 05

Quads become single triangles and polygons leave a hole.

Mesh topology invariants◈ Members↗
FA-88621

Fan triangulation counts triangles as diagonals · case 01

Reported diagonals are one higher per polygon.

Mesh topology invariants● Open access↗
FA-88622

Fan triangulation counts triangles as diagonals · case 02

Reported diagonals are one higher per polygon.

Mesh topology invariants◈ Members↗
FA-88623

Fan triangulation counts triangles as diagonals · case 03

Reported diagonals are one higher per polygon.

Mesh topology invariants◈ Members↗
FA-88624

Fan triangulation counts triangles as diagonals · case 04

Reported diagonals are one higher per polygon.

Mesh topology invariants◈ Members↗
FA-88625

Fan triangulation counts triangles as diagonals · case 05

Reported diagonals are one higher per polygon.

Mesh topology invariants◈ Members↗
FA-88626

Fan triangulation silently skips two-corner faces · case 01

Invalid faces vanish instead of being reported.

Mesh topology invariants● Open access↗
FA-88627

Fan triangulation silently skips two-corner faces · case 02

Invalid faces vanish instead of being reported.

Mesh topology invariants◈ Members↗
FA-88628

Fan triangulation silently skips two-corner faces · case 03

Invalid faces vanish instead of being reported.

Mesh topology invariants◈ Members↗
FA-88629

Fan triangulation silently skips two-corner faces · case 04

Invalid faces vanish instead of being reported.

Mesh topology invariants◈ Members↗
FA-88630

Fan triangulation silently skips two-corner faces · case 05

Invalid faces vanish instead of being reported.

Mesh topology invariants◈ Members↗
FA-88631

Triangulated edge set is keyed by direction · case 01

Edge growth counts each shared triangle edge twice.

Mesh topology invariants● Open access↗
FA-88632

Triangulated edge set is keyed by direction · case 02

Edge growth counts each shared triangle edge twice.

Mesh topology invariants◈ Members↗
FA-88633

Triangulated edge set is keyed by direction · case 03

Edge growth counts each shared triangle edge twice.

Mesh topology invariants◈ Members↗
FA-88634

Triangulated edge set is keyed by direction · case 04

Edge growth counts each shared triangle edge twice.

Mesh topology invariants◈ Members↗
FA-88635

Triangulated edge set is keyed by direction · case 05

Edge growth counts each shared triangle edge twice.

Mesh topology invariants◈ Members↗
FA-88636

Edge flip emits triangles with reversed winding · case 01

After a flip both new triangles face inward, breaking orientation consistency.

Mesh topology invariants● Open access↗
FA-88637

Edge flip emits triangles with reversed winding · case 02

After a flip both new triangles face inward, breaking orientation consistency.

Mesh topology invariants◈ Members↗
FA-88638

Edge flip emits triangles with reversed winding · case 03

After a flip both new triangles face inward, breaking orientation consistency.

Mesh topology invariants◈ Members↗
FA-88639

Edge flip emits triangles with reversed winding · case 04

After a flip both new triangles face inward, breaking orientation consistency.

Mesh topology invariants◈ Members↗
FA-88640

Edge flip emits triangles with reversed winding · case 05

After a flip both new triangles face inward, breaking orientation consistency.

Mesh topology invariants◈ Members↗
FA-88641

Edge flip misses an existing diagonal stored in the opposite direction · case 01

A flip that duplicates an edge already present elsewhere is accepted.

Mesh topology invariants● Open access↗
FA-88642

Edge flip misses an existing diagonal stored in the opposite direction · case 02

A flip that duplicates an edge already present elsewhere is accepted.

Mesh topology invariants◈ Members↗
FA-88643

Edge flip misses an existing diagonal stored in the opposite direction · case 03

A flip that duplicates an edge already present elsewhere is accepted.

Mesh topology invariants◈ Members↗
FA-88644

Edge flip misses an existing diagonal stored in the opposite direction · case 04

A flip that duplicates an edge already present elsewhere is accepted.

Mesh topology invariants◈ Members↗
FA-88645

Edge flip misses an existing diagonal stored in the opposite direction · case 05

A flip that duplicates an edge already present elsewhere is accepted.

Mesh topology invariants◈ Members↗
FA-88646

Edge flip accepts two triangles with the same apex · case 01

A folded pair is flipped into triangles that repeat a vertex.

Mesh topology invariants● Open access↗
FA-88647

Edge flip accepts two triangles with the same apex · case 02

A folded pair is flipped into triangles that repeat a vertex.

Mesh topology invariants◈ Members↗
FA-88648

Edge flip accepts two triangles with the same apex · case 03

A folded pair is flipped into triangles that repeat a vertex.

Mesh topology invariants◈ Members↗
FA-88649

Edge flip accepts two triangles with the same apex · case 04

A folded pair is flipped into triangles that repeat a vertex.

Mesh topology invariants◈ Members↗
FA-88650

Edge flip accepts two triangles with the same apex · case 05

A folded pair is flipped into triangles that repeat a vertex.

Mesh topology invariants◈ Members↗
FA-88651

Edge flip swaps which face slot receives which new triangle · case 01

Face indices referenced elsewhere now point at the other triangle.

Mesh topology invariants● Open access↗
FA-88652

Edge flip swaps which face slot receives which new triangle · case 02

Face indices referenced elsewhere now point at the other triangle.

Mesh topology invariants◈ Members↗
FA-88653

Edge flip swaps which face slot receives which new triangle · case 03

Face indices referenced elsewhere now point at the other triangle.

Mesh topology invariants◈ Members↗
FA-88654

Edge flip swaps which face slot receives which new triangle · case 04

Face indices referenced elsewhere now point at the other triangle.

Mesh topology invariants◈ Members↗
FA-88655

Edge flip swaps which face slot receives which new triangle · case 05

Face indices referenced elsewhere now point at the other triangle.

Mesh topology invariants◈ Members↗
FA-88656

Edge flip reads the second apex from the wrong corner · case 01

The second apex is an endpoint of the flipped edge, so valid flips are refused as "edge-exists".

Mesh topology invariants● Open access↗
FA-88657

Edge flip reads the second apex from the wrong corner · case 02

The second apex is an endpoint of the flipped edge, so valid flips are refused as "edge-exists".

Mesh topology invariants◈ Members↗
FA-88658

Edge flip reads the second apex from the wrong corner · case 03

The second apex is an endpoint of the flipped edge, so valid flips are refused as "edge-exists".

Mesh topology invariants◈ Members↗
FA-88659

Edge flip reads the second apex from the wrong corner · case 04

The second apex is an endpoint of the flipped edge, so valid flips are refused as "edge-exists".

Mesh topology invariants◈ Members↗
FA-88660

Edge flip reads the second apex from the wrong corner · case 05

The second apex is an endpoint of the flipped edge, so valid flips are refused as "edge-exists".

Mesh topology invariants◈ Members↗
FA-88661

One-ring is walked clockwise · case 01

Neighbour rings come out in reverse angular order.

Mesh topology invariants● Open access↗
FA-88662

One-ring is walked clockwise · case 02

Neighbour rings come out in reverse angular order.

Mesh topology invariants◈ Members↗
FA-88663

One-ring is walked clockwise · case 03

Neighbour rings come out in reverse angular order.

Mesh topology invariants◈ Members↗
FA-88664

One-ring is walked clockwise · case 04

Neighbour rings come out in reverse angular order.

Mesh topology invariants◈ Members↗
FA-88665

One-ring is walked clockwise · case 05

Neighbour rings come out in reverse angular order.

Mesh topology invariants◈ Members↗
FA-88666

Boundary one-ring starts in the middle of the fan · case 01

Boundary vertices whose smallest neighbour is not the fan start are reported non-manifold.

Mesh topology invariants● Open access↗
FA-88667

Boundary one-ring starts in the middle of the fan · case 02

Boundary vertices whose smallest neighbour is not the fan start are reported non-manifold.

Mesh topology invariants◈ Members↗
FA-88668

Boundary one-ring starts in the middle of the fan · case 03

Boundary vertices whose smallest neighbour is not the fan start are reported non-manifold.

Mesh topology invariants◈ Members↗
FA-88669

Boundary one-ring starts in the middle of the fan · case 04

Boundary vertices whose smallest neighbour is not the fan start are reported non-manifold.

Mesh topology invariants◈ Members↗
FA-88670

Boundary one-ring starts in the middle of the fan · case 05

Boundary vertices whose smallest neighbour is not the fan start are reported non-manifold.

Mesh topology invariants◈ Members↗
FA-88671

One-ring completeness is measured against the successor count · case 01

Every boundary vertex is reported non-manifold.

Mesh topology invariants● Open access↗
FA-88672

One-ring completeness is measured against the successor count · case 02

Every boundary vertex is reported non-manifold.

Mesh topology invariants◈ Members↗
FA-88673

One-ring completeness is measured against the successor count · case 03

Every boundary vertex is reported non-manifold.

Mesh topology invariants◈ Members↗
FA-88674

One-ring completeness is measured against the successor count · case 04

Every boundary vertex is reported non-manifold.

Mesh topology invariants◈ Members↗
FA-88675

One-ring completeness is measured against the successor count · case 05

Every boundary vertex is reported non-manifold.

Mesh topology invariants◈ Members↗
FA-88676

One-ring overwrites a repeated spoke · case 01

Two faces leaving v along the same edge (a flipped neighbour) are merged into a plausible ring.

Mesh topology invariants● Open access↗
FA-88677

One-ring overwrites a repeated spoke · case 02

Two faces leaving v along the same edge (a flipped neighbour) are merged into a plausible ring.

Mesh topology invariants◈ Members↗
FA-88678

One-ring overwrites a repeated spoke · case 03

Two faces leaving v along the same edge (a flipped neighbour) are merged into a plausible ring.

Mesh topology invariants◈ Members↗
FA-88679

One-ring overwrites a repeated spoke · case 04

Two faces leaving v along the same edge (a flipped neighbour) are merged into a plausible ring.

Mesh topology invariants◈ Members↗
FA-88680

One-ring overwrites a repeated spoke · case 05

Two faces leaving v along the same edge (a flipped neighbour) are merged into a plausible ring.

Mesh topology invariants◈ Members↗
FA-88681

One-ring walk stops before leaving the start · case 01

Every ring collapses to its start vertex and is reported non-manifold.

Mesh topology invariants● Open access↗
FA-88682

One-ring walk stops before leaving the start · case 02

Every ring collapses to its start vertex and is reported non-manifold.

Mesh topology invariants◈ Members↗
FA-88683

One-ring walk stops before leaving the start · case 03

Every ring collapses to its start vertex and is reported non-manifold.

Mesh topology invariants◈ Members↗
FA-88684

One-ring walk stops before leaving the start · case 04

Every ring collapses to its start vertex and is reported non-manifold.

Mesh topology invariants◈ Members↗
FA-88685

One-ring walk stops before leaving the start · case 05

Every ring collapses to its start vertex and is reported non-manifold.

Mesh topology invariants◈ Members↗
FA-88686

Make-edge-face does not add the new face loop · case 01

Every face-closing operation reports a broken invariant or too few loops.

Mesh topology invariants● Open access↗
FA-88687

Make-edge-face does not add the new face loop · case 02

Every face-closing operation reports a broken invariant or too few loops.

Mesh topology invariants◈ Members↗
FA-88688

Make-edge-face does not add the new face loop · case 03

Every face-closing operation reports a broken invariant or too few loops.

Mesh topology invariants◈ Members↗
FA-88689

Make-edge-face does not add the new face loop · case 04

Every face-closing operation reports a broken invariant or too few loops.

Mesh topology invariants◈ Members↗
FA-88690

Make-edge-face does not add the new face loop · case 05

Every face-closing operation reports a broken invariant or too few loops.

Mesh topology invariants◈ Members↗
FA-88691

Kill-edge-make-ring removes a loop instead of adding one · case 01

Creating an inner ring breaks the Euler-Poincare relation.

Mesh topology invariants● Open access↗
FA-88692

Kill-edge-make-ring removes a loop instead of adding one · case 02

Creating an inner ring breaks the Euler-Poincare relation.

Mesh topology invariants◈ Members↗
FA-88693

Kill-edge-make-ring removes a loop instead of adding one · case 03

Creating an inner ring breaks the Euler-Poincare relation.

Mesh topology invariants◈ Members↗
FA-88694

Kill-edge-make-ring removes a loop instead of adding one · case 04

Creating an inner ring breaks the Euler-Poincare relation.

Mesh topology invariants◈ Members↗
FA-88695

Kill-edge-make-ring removes a loop instead of adding one · case 05

Creating an inner ring breaks the Euler-Poincare relation.

Mesh topology invariants◈ Members↗
FA-88696

Kill-face-make-ring-hole forgets the new handle · case 01

Through-holes are rejected as broken invariants.

Mesh topology invariants● Open access↗
FA-88697

Kill-face-make-ring-hole forgets the new handle · case 02

Through-holes are rejected as broken invariants.

Mesh topology invariants◈ Members↗
FA-88698

Kill-face-make-ring-hole forgets the new handle · case 03

Through-holes are rejected as broken invariants.

Mesh topology invariants◈ Members↗
FA-88699

Kill-face-make-ring-hole forgets the new handle · case 04

Through-holes are rejected as broken invariants.

Mesh topology invariants◈ Members↗
FA-88700

Kill-face-make-ring-hole forgets the new handle · case 05

Through-holes are rejected as broken invariants.

Mesh topology 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 ↗