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

Valence is taken from incident face count plus one · case 01

Interior vertices of closed meshes are over-counted by one each.

Mesh topology invariants● Open access↗
FA-88802

Valence is taken from incident face count plus one · case 02

Interior vertices of closed meshes are over-counted by one each.

Mesh topology invariants◈ Members↗
FA-88803

Valence is taken from incident face count plus one · case 03

Interior vertices of closed meshes are over-counted by one each.

Mesh topology invariants◈ Members↗
FA-88804

Valence is taken from incident face count plus one · case 04

Interior vertices of closed meshes are over-counted by one each.

Mesh topology invariants◈ Members↗
FA-88805

Valence is taken from incident face count plus one · case 05

Interior vertices of closed meshes are over-counted by one each.

Mesh topology invariants◈ Members↗
FA-88806

Triangle boundary vertices are held to the interior valence · case 01

Open triangle meshes fail the index identity.

Mesh topology invariants● Open access↗
FA-88807

Triangle boundary vertices are held to the interior valence · case 02

Open triangle meshes fail the index identity.

Mesh topology invariants◈ Members↗
FA-88808

Triangle boundary vertices are held to the interior valence · case 03

Open triangle meshes fail the index identity.

Mesh topology invariants◈ Members↗
FA-88809

Triangle boundary vertices are held to the interior valence · case 04

Open triangle meshes fail the index identity.

Mesh topology invariants◈ Members↗
FA-88810

Triangle boundary vertices are held to the interior valence · case 05

Open triangle meshes fail the index identity.

Mesh topology invariants◈ Members↗
FA-88811

Index identity derives the edge count from corner uses · case 01

Open meshes get a wrong Euler characteristic, so the index identity fails.

Mesh topology invariants● Open access↗
FA-88812

Index identity derives the edge count from corner uses · case 02

Open meshes get a wrong Euler characteristic, so the index identity fails.

Mesh topology invariants◈ Members↗
FA-88813

Index identity derives the edge count from corner uses · case 03

Open meshes get a wrong Euler characteristic, so the index identity fails.

Mesh topology invariants◈ Members↗
FA-88814

Index identity derives the edge count from corner uses · case 04

Open meshes get a wrong Euler characteristic, so the index identity fails.

Mesh topology invariants◈ Members↗
FA-88815

Index identity derives the edge count from corner uses · case 05

Open meshes get a wrong Euler characteristic, so the index identity fails.

Mesh topology invariants◈ Members↗
FA-88816

Index identity uses the triangle multiplier for every mesh kind · case 01

Quad meshes report a failed identity.

Mesh topology invariants● Open access↗
FA-88817

Index identity uses the triangle multiplier for every mesh kind · case 02

Quad meshes report a failed identity.

Mesh topology invariants◈ Members↗
FA-88818

Index identity uses the triangle multiplier for every mesh kind · case 03

Quad meshes report a failed identity.

Mesh topology invariants◈ Members↗
FA-88819

Index identity uses the triangle multiplier for every mesh kind · case 04

Quad meshes report a failed identity.

Mesh topology invariants◈ Members↗
FA-88820

Index identity uses the triangle multiplier for every mesh kind · case 05

Quad meshes report a failed identity.

Mesh topology invariants◈ Members↗
FA-88821

Face adjacency counts a neighbour once per shared edge · case 01

Faces sharing two edges report degree 2 for one neighbour.

Mesh topology invariants● Open access↗
FA-88822

Face adjacency counts a neighbour once per shared edge · case 02

Faces sharing two edges report degree 2 for one neighbour.

Mesh topology invariants◈ Members↗
FA-88823

Face adjacency counts a neighbour once per shared edge · case 03

Faces sharing two edges report degree 2 for one neighbour.

Mesh topology invariants◈ Members↗
FA-88824

Face adjacency counts a neighbour once per shared edge · case 04

Faces sharing two edges report degree 2 for one neighbour.

Mesh topology invariants◈ Members↗
FA-88825

Face adjacency counts a neighbour once per shared edge · case 05

Faces sharing two edges report degree 2 for one neighbour.

Mesh topology invariants◈ Members↗
FA-88826

Face is counted as its own neighbour · case 01

Every face degree is one too high.

Mesh topology invariants● Open access↗
FA-88827

Face is counted as its own neighbour · case 02

Every face degree is one too high.

Mesh topology invariants◈ Members↗
FA-88828

Face is counted as its own neighbour · case 03

Every face degree is one too high.

Mesh topology invariants◈ Members↗
FA-88829

Face is counted as its own neighbour · case 04

Every face degree is one too high.

Mesh topology invariants◈ Members↗
FA-88830

Face is counted as its own neighbour · case 05

Every face degree is one too high.

Mesh topology invariants◈ Members↗
FA-88831

Face adjacency is keyed by directed edges · case 01

Consistently oriented neighbours are not found; only flipped ones are.

Mesh topology invariants● Open access↗
FA-88832

Face adjacency is keyed by directed edges · case 02

Consistently oriented neighbours are not found; only flipped ones are.

Mesh topology invariants◈ Members↗
FA-88833

Face adjacency is keyed by directed edges · case 03

Consistently oriented neighbours are not found; only flipped ones are.

Mesh topology invariants◈ Members↗
FA-88834

Face adjacency is keyed by directed edges · case 04

Consistently oriented neighbours are not found; only flipped ones are.

Mesh topology invariants◈ Members↗
FA-88835

Face adjacency is keyed by directed edges · case 05

Consistently oriented neighbours are not found; only flipped ones are.

Mesh topology invariants◈ Members↗
FA-88836

Adjacent pair count uses interior edges · case 01

Face pairs sharing two edges or fins are miscounted.

Mesh topology invariants● Open access↗
FA-88837

Adjacent pair count uses interior edges · case 02

Face pairs sharing two edges or fins are miscounted.

Mesh topology invariants◈ Members↗
FA-88838

Adjacent pair count uses interior edges · case 03

Face pairs sharing two edges or fins are miscounted.

Mesh topology invariants◈ Members↗
FA-88839

Adjacent pair count uses interior edges · case 04

Face pairs sharing two edges or fins are miscounted.

Mesh topology invariants◈ Members↗
FA-88840

Adjacent pair count uses interior edges · case 05

Face pairs sharing two edges or fins are miscounted.

Mesh topology invariants◈ Members↗
FA-88841

Unknown input overrides a controlling zero on an AND gate · case 01

An AND gate with a 0 input and an unknown input reports x instead of the definite 0.

Digital logic simulation● Open access↗
FA-88842

Unknown input overrides a controlling zero on an AND gate · case 02

An AND gate with a 0 input and an unknown input reports x instead of the definite 0.

Digital logic simulation◈ Members↗
FA-88843

Unknown input overrides a controlling zero on an AND gate · case 03

An AND gate with a 0 input and an unknown input reports x instead of the definite 0.

Digital logic simulation◈ Members↗
FA-88844

Unknown input overrides a controlling zero on an AND gate · case 04

An AND gate with a 0 input and an unknown input reports x instead of the definite 0.

Digital logic simulation◈ Members↗
FA-88845

Unknown input overrides a controlling zero on an AND gate · case 05

An AND gate with a 0 input and an unknown input reports x instead of the definite 0.

Digital logic simulation◈ Members↗
FA-88846

Floating gate input is evaluated as a literal z · case 01

A buffer driven by a floating net outputs 'z' and an XOR with a floating pin produces a definite parity.

Digital logic simulation● Open access↗
FA-88847

Floating gate input is evaluated as a literal z · case 02

A buffer driven by a floating net outputs 'z' and an XOR with a floating pin produces a definite parity.

Digital logic simulation◈ Members↗
FA-88848

Floating gate input is evaluated as a literal z · case 03

A buffer driven by a floating net outputs 'z' and an XOR with a floating pin produces a definite parity.

Digital logic simulation◈ Members↗
FA-88849

Floating gate input is evaluated as a literal z · case 04

A buffer driven by a floating net outputs 'z' and an XOR with a floating pin produces a definite parity.

Digital logic simulation◈ Members↗
FA-88850

Floating gate input is evaluated as a literal z · case 05

A buffer driven by a floating net outputs 'z' and an XOR with a floating pin produces a definite parity.

Digital logic simulation◈ Members↗
FA-88851

XOR parity ignores unknown inputs · case 01

An XOR gate with an unknown input returns a definite parity bit.

Digital logic simulation● Open access↗
FA-88852

XOR parity ignores unknown inputs · case 02

An XOR gate with an unknown input returns a definite parity bit.

Digital logic simulation◈ Members↗
FA-88853

XOR parity ignores unknown inputs · case 03

An XOR gate with an unknown input returns a definite parity bit.

Digital logic simulation◈ Members↗
FA-88854

XOR parity ignores unknown inputs · case 04

An XOR gate with an unknown input returns a definite parity bit.

Digital logic simulation◈ Members↗
FA-88855

XOR parity ignores unknown inputs · case 05

An XOR gate with an unknown input returns a definite parity bit.

Digital logic simulation◈ Members↗
FA-88856

XNOR output is not inverted · case 01

An XNOR gate returns the same value as XOR.

Digital logic simulation● Open access↗
FA-88857

XNOR output is not inverted · case 02

An XNOR gate returns the same value as XOR.

Digital logic simulation◈ Members↗
FA-88858

XNOR output is not inverted · case 03

An XNOR gate returns the same value as XOR.

Digital logic simulation◈ Members↗
FA-88859

XNOR output is not inverted · case 04

An XNOR gate returns the same value as XOR.

Digital logic simulation◈ Members↗
FA-88860

XNOR output is not inverted · case 05

An XNOR gate returns the same value as XOR.

Digital logic simulation◈ Members↗
FA-88861

Unknown enable on a tri-state buffer releases the net · case 01

A bufif1 with an unknown enable drives 'z' instead of an unknown value.

Digital logic simulation● Open access↗
FA-88862

Unknown enable on a tri-state buffer releases the net · case 02

A bufif1 with an unknown enable drives 'z' instead of an unknown value.

Digital logic simulation◈ Members↗
FA-88863

Unknown enable on a tri-state buffer releases the net · case 03

A bufif1 with an unknown enable drives 'z' instead of an unknown value.

Digital logic simulation◈ Members↗
FA-88864

Unknown enable on a tri-state buffer releases the net · case 04

A bufif1 with an unknown enable drives 'z' instead of an unknown value.

Digital logic simulation◈ Members↗
FA-88865

Unknown enable on a tri-state buffer releases the net · case 05

A bufif1 with an unknown enable drives 'z' instead of an unknown value.

Digital logic simulation◈ Members↗
FA-88866

Gate delay behaves as transport delay · case 01

A pulse narrower than the gate delay appears on the output instead of being swallowed.

Digital logic simulation● Open access↗
FA-88867

Gate delay behaves as transport delay · case 02

A pulse narrower than the gate delay appears on the output instead of being swallowed.

Digital logic simulation◈ Members↗
FA-88868

Gate delay behaves as transport delay · case 03

A pulse narrower than the gate delay appears on the output instead of being swallowed.

Digital logic simulation◈ Members↗
FA-88869

Gate delay behaves as transport delay · case 04

A pulse narrower than the gate delay appears on the output instead of being swallowed.

Digital logic simulation◈ Members↗
FA-88870

Gate delay behaves as transport delay · case 05

A pulse narrower than the gate delay appears on the output instead of being swallowed.

Digital logic simulation◈ Members↗
FA-88871

Rise or fall delay chosen from the input edge · case 01

An inverter output falls after the rise delay and rises after the fall delay.

Digital logic simulation● Open access↗
FA-88872

Rise or fall delay chosen from the input edge · case 02

An inverter output falls after the rise delay and rises after the fall delay.

Digital logic simulation◈ Members↗
FA-88873

Rise or fall delay chosen from the input edge · case 03

An inverter output falls after the rise delay and rises after the fall delay.

Digital logic simulation◈ Members↗
FA-88874

Rise or fall delay chosen from the input edge · case 04

An inverter output falls after the rise delay and rises after the fall delay.

Digital logic simulation◈ Members↗
FA-88875

Rise or fall delay chosen from the input edge · case 05

An inverter output falls after the rise delay and rises after the fall delay.

Digital logic simulation◈ Members↗
FA-88876

Redundant output events are reported as edges · case 01

The waveform lists a transition to the value the output already holds.

Digital logic simulation● Open access↗
FA-88877

Redundant output events are reported as edges · case 02

The waveform lists a transition to the value the output already holds.

Digital logic simulation◈ Members↗
FA-88878

Redundant output events are reported as edges · case 03

The waveform lists a transition to the value the output already holds.

Digital logic simulation◈ Members↗
FA-88879

Redundant output events are reported as edges · case 04

The waveform lists a transition to the value the output already holds.

Digital logic simulation◈ Members↗
FA-88880

Redundant output events are reported as edges · case 05

The waveform lists a transition to the value the output already holds.

Digital logic simulation◈ Members↗
FA-88881

Initial output ignores the gate function · case 01

An inverter whose input starts low is assumed to start low, so its first falling edge disappears.

Digital logic simulation● Open access↗
FA-88882

Initial output ignores the gate function · case 02

An inverter whose input starts low is assumed to start low, so its first falling edge disappears.

Digital logic simulation◈ Members↗
FA-88883

Initial output ignores the gate function · case 03

An inverter whose input starts low is assumed to start low, so its first falling edge disappears.

Digital logic simulation◈ Members↗
FA-88884

Initial output ignores the gate function · case 04

An inverter whose input starts low is assumed to start low, so its first falling edge disappears.

Digital logic simulation◈ Members↗
FA-88885

Initial output ignores the gate function · case 05

An inverter whose input starts low is assumed to start low, so its first falling edge disappears.

Digital logic simulation◈ Members↗
FA-88886

Output events pending after the last stimulus are lost · case 01

The final output transition is missing whenever it matures after the last input change.

Digital logic simulation● Open access↗
FA-88887

Output events pending after the last stimulus are lost · case 02

The final output transition is missing whenever it matures after the last input change.

Digital logic simulation◈ Members↗
FA-88888

Output events pending after the last stimulus are lost · case 03

The final output transition is missing whenever it matures after the last input change.

Digital logic simulation◈ Members↗
FA-88889

Output events pending after the last stimulus are lost · case 04

The final output transition is missing whenever it matures after the last input change.

Digital logic simulation◈ Members↗
FA-88890

Output events pending after the last stimulus are lost · case 05

The final output transition is missing whenever it matures after the last input change.

Digital logic simulation◈ Members↗
FA-88891

Gate level taken from the shallowest fanin · case 01

Reconvergent logic reports a smaller depth than its longest path.

Digital logic simulation● Open access↗
FA-88892

Gate level taken from the shallowest fanin · case 02

Reconvergent logic reports a smaller depth than its longest path.

Digital logic simulation◈ Members↗
FA-88893

Gate level taken from the shallowest fanin · case 03

Reconvergent logic reports a smaller depth than its longest path.

Digital logic simulation◈ Members↗
FA-88894

Gate level taken from the shallowest fanin · case 04

Reconvergent logic reports a smaller depth than its longest path.

Digital logic simulation◈ Members↗
FA-88895

Gate level taken from the shallowest fanin · case 05

Reconvergent logic reports a smaller depth than its longest path.

Digital logic simulation◈ Members↗
FA-88896

Constant tie cells counted as a logic level · case 01

A chain fed by a tie cell reports one extra level of depth.

Digital logic simulation● Open access↗
FA-88897

Constant tie cells counted as a logic level · case 02

A chain fed by a tie cell reports one extra level of depth.

Digital logic simulation◈ Members↗
FA-88898

Constant tie cells counted as a logic level · case 03

A chain fed by a tie cell reports one extra level of depth.

Digital logic simulation◈ Members↗
FA-88899

Constant tie cells counted as a logic level · case 04

A chain fed by a tie cell reports one extra level of depth.

Digital logic simulation◈ Members↗
FA-88900

Constant tie cells counted as a logic level · case 05

A chain fed by a tie cell reports one extra level of depth.

Digital logic simulation◈ 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 ↗