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

Lot partition: child sale activation · case 01

Unaccepted child lots are offered before their partition exists.

Auction allocation rules● Open access↗
FA-57102

Lot partition: child sale activation · case 02

Unaccepted child lots are offered before their partition exists.

Auction allocation rules◈ Members↗
FA-57103

Lot partition: child sale activation · case 03

Unaccepted child lots are offered before their partition exists.

Auction allocation rules◈ Members↗
FA-57104

Lot partition: child sale activation · case 04

Unaccepted child lots are offered before their partition exists.

Auction allocation rules◈ Members↗
FA-57105

Lot partition: child sale activation · case 05

Unaccepted child lots are offered before their partition exists.

Auction allocation rules◈ Members↗
FA-57106

Lot partition: reservation inheritance · case 01

Parent encumbrance is lost or inherited from an unrelated child reservation.

Auction allocation rules● Open access↗
FA-57107

Lot partition: reservation inheritance · case 02

Parent encumbrance is lost or inherited from an unrelated child reservation.

Auction allocation rules◈ Members↗
FA-57108

Lot partition: reservation inheritance · case 03

Parent encumbrance is lost or inherited from an unrelated child reservation.

Auction allocation rules◈ Members↗
FA-57109

Lot partition: reservation inheritance · case 04

Parent encumbrance is lost or inherited from an unrelated child reservation.

Auction allocation rules◈ Members↗
FA-57110

Lot partition: reservation inheritance · case 05

Parent encumbrance is lost or inherited from an unrelated child reservation.

Auction allocation rules◈ Members↗
FA-57111

Lot partition: sold parent partition block · case 01

Partition changes an already sold parent or child schedule.

Auction allocation rules● Open access↗
FA-57112

Lot partition: sold parent partition block · case 02

Partition changes an already sold parent or child schedule.

Auction allocation rules◈ Members↗
FA-57113

Lot partition: sold parent partition block · case 03

Partition changes an already sold parent or child schedule.

Auction allocation rules◈ Members↗
FA-57114

Lot partition: sold parent partition block · case 04

Partition changes an already sold parent or child schedule.

Auction allocation rules◈ Members↗
FA-57115

Lot partition: sold parent partition block · case 05

Partition changes an already sold parent or child schedule.

Auction allocation rules◈ Members↗
FA-57116

Lot partition: serial disjointness · case 01

The same physical serial is sold through two different children.

Auction allocation rules● Open access↗
FA-57117

Lot partition: serial disjointness · case 02

The same physical serial is sold through two different children.

Auction allocation rules◈ Members↗
FA-57118

Lot partition: serial disjointness · case 03

The same physical serial is sold through two different children.

Auction allocation rules◈ Members↗
FA-57119

Lot partition: serial disjointness · case 04

The same physical serial is sold through two different children.

Auction allocation rules◈ Members↗
FA-57120

Lot partition: serial disjointness · case 05

The same physical serial is sold through two different children.

Auction allocation rules◈ Members↗
FA-57121

Lot partition: serial coverage · case 01

A partition omits parent serials from every child.

Auction allocation rules● Open access↗
FA-57122

Lot partition: serial coverage · case 02

A partition omits parent serials from every child.

Auction allocation rules◈ Members↗
FA-57123

Lot partition: serial coverage · case 03

A partition omits parent serials from every child.

Auction allocation rules◈ Members↗
FA-57124

Lot partition: serial coverage · case 04

A partition omits parent serials from every child.

Auction allocation rules◈ Members↗
FA-57125

Lot partition: serial coverage · case 05

A partition omits parent serials from every child.

Auction allocation rules◈ Members↗
FA-57126

Lot partition: child certificates · case 01

Parent certification is treated as an issued certificate for every child.

Auction allocation rules● Open access↗
FA-57127

Lot partition: child certificates · case 02

Parent certification is treated as an issued certificate for every child.

Auction allocation rules◈ Members↗
FA-57128

Lot partition: child certificates · case 03

Parent certification is treated as an issued certificate for every child.

Auction allocation rules◈ Members↗
FA-57129

Lot partition: child certificates · case 04

Parent certification is treated as an issued certificate for every child.

Auction allocation rules◈ Members↗
FA-57130

Lot partition: child certificates · case 05

Parent certification is treated as an issued certificate for every child.

Auction allocation rules◈ Members↗
FA-57131

Lot partition: merge retires children · case 01

Merged or withdrawn child identifiers remain independently saleable.

Auction allocation rules● Open access↗
FA-57132

Lot partition: merge retires children · case 02

Merged or withdrawn child identifiers remain independently saleable.

Auction allocation rules◈ Members↗
FA-57133

Lot partition: merge retires children · case 03

Merged or withdrawn child identifiers remain independently saleable.

Auction allocation rules◈ Members↗
FA-57134

Lot partition: merge retires children · case 04

Merged or withdrawn child identifiers remain independently saleable.

Auction allocation rules◈ Members↗
FA-57135

Lot partition: merge retires children · case 05

Merged or withdrawn child identifiers remain independently saleable.

Auction allocation rules◈ Members↗
FA-57136

Lot partition: minimum child size · case 01

Parent total size hides an undersized child lot.

Auction allocation rules● Open access↗
FA-57137

Lot partition: minimum child size · case 02

Parent total size hides an undersized child lot.

Auction allocation rules◈ Members↗
FA-57138

Lot partition: minimum child size · case 03

Parent total size hides an undersized child lot.

Auction allocation rules◈ Members↗
FA-57139

Lot partition: minimum child size · case 04

Parent total size hides an undersized child lot.

Auction allocation rules◈ Members↗
FA-57140

Lot partition: minimum child size · case 05

Parent total size hides an undersized child lot.

Auction allocation rules◈ Members↗
FA-57141

Delivery slot awards: consecutive slot package · case 01

A multi-slot award contains a delivery gap.

Auction allocation rules● Open access↗
FA-57142

Delivery slot awards: consecutive slot package · case 02

A multi-slot award contains a delivery gap.

Auction allocation rules◈ Members↗
FA-57143

Delivery slot awards: consecutive slot package · case 03

A multi-slot award contains a delivery gap.

Auction allocation rules◈ Members↗
FA-57144

Delivery slot awards: consecutive slot package · case 04

A multi-slot award contains a delivery gap.

Auction allocation rules◈ Members↗
FA-57145

Delivery slot awards: consecutive slot package · case 05

A multi-slot award contains a delivery gap.

Auction allocation rules◈ Members↗
FA-57146

Delivery slot awards: occupied slot conflict · case 01

A slot package overlaps one committed slot but differs as a whole.

Auction allocation rules● Open access↗
FA-57147

Delivery slot awards: occupied slot conflict · case 02

A slot package overlaps one committed slot but differs as a whole.

Auction allocation rules◈ Members↗
FA-57148

Delivery slot awards: occupied slot conflict · case 03

A slot package overlaps one committed slot but differs as a whole.

Auction allocation rules◈ Members↗
FA-57149

Delivery slot awards: occupied slot conflict · case 04

A slot package overlaps one committed slot but differs as a whole.

Auction allocation rules◈ Members↗
FA-57150

Delivery slot awards: occupied slot conflict · case 05

A slot package overlaps one committed slot but differs as a whole.

Auction allocation rules◈ Members↗
FA-57151

Delivery slot awards: maintenance exclusion · case 01

Maintenance blocks either no requested slot or every auction slot.

Auction allocation rules● Open access↗
FA-57152

Delivery slot awards: maintenance exclusion · case 02

Maintenance blocks either no requested slot or every auction slot.

Auction allocation rules◈ Members↗
FA-57153

Delivery slot awards: maintenance exclusion · case 03

Maintenance blocks either no requested slot or every auction slot.

Auction allocation rules◈ Members↗
FA-57154

Delivery slot awards: maintenance exclusion · case 04

Maintenance blocks either no requested slot or every auction slot.

Auction allocation rules◈ Members↗
FA-57155

Delivery slot awards: maintenance exclusion · case 05

Maintenance blocks either no requested slot or every auction slot.

Auction allocation rules◈ Members↗
FA-57156

Delivery slot awards: repeated slot demand · case 01

A package containing several simultaneous deliveries collapses multiplicity at one slot.

Auction allocation rules● Open access↗
FA-57157

Delivery slot awards: repeated slot demand · case 02

A package containing several simultaneous deliveries collapses multiplicity at one slot.

Auction allocation rules◈ Members↗
FA-57158

Delivery slot awards: repeated slot demand · case 03

A package containing several simultaneous deliveries collapses multiplicity at one slot.

Auction allocation rules◈ Members↗
FA-57159

Delivery slot awards: repeated slot demand · case 04

A package containing several simultaneous deliveries collapses multiplicity at one slot.

Auction allocation rules◈ Members↗
FA-57160

Delivery slot awards: repeated slot demand · case 05

A package containing several simultaneous deliveries collapses multiplicity at one slot.

Auction allocation rules◈ Members↗
FA-57161

Delivery slot awards: per slot capacity · case 01

Aggregate spare capacity hides an oversold delivery slot.

Auction allocation rules● Open access↗
FA-57162

Delivery slot awards: per slot capacity · case 02

Aggregate spare capacity hides an oversold delivery slot.

Auction allocation rules◈ Members↗
FA-57163

Delivery slot awards: per slot capacity · case 03

Aggregate spare capacity hides an oversold delivery slot.

Auction allocation rules◈ Members↗
FA-57164

Delivery slot awards: per slot capacity · case 04

Aggregate spare capacity hides an oversold delivery slot.

Auction allocation rules◈ Members↗
FA-57165

Delivery slot awards: per slot capacity · case 05

Aggregate spare capacity hides an oversold delivery slot.

Auction allocation rules◈ Members↗
FA-57166

Delivery slot awards: setup footprint · case 01

Setup capacity is omitted or reserved after delivery starts.

Auction allocation rules● Open access↗
FA-57167

Delivery slot awards: setup footprint · case 02

Setup capacity is omitted or reserved after delivery starts.

Auction allocation rules◈ Members↗
FA-57168

Delivery slot awards: setup footprint · case 03

Setup capacity is omitted or reserved after delivery starts.

Auction allocation rules◈ Members↗
FA-57169

Delivery slot awards: setup footprint · case 04

Setup capacity is omitted or reserved after delivery starts.

Auction allocation rules◈ Members↗
FA-57170

Delivery slot awards: setup footprint · case 05

Setup capacity is omitted or reserved after delivery starts.

Auction allocation rules◈ Members↗
FA-57171

Delivery slot awards: cleanup footprint · case 01

Cleanup is reserved inside the award instead of after it.

Auction allocation rules● Open access↗
FA-57172

Delivery slot awards: cleanup footprint · case 02

Cleanup is reserved inside the award instead of after it.

Auction allocation rules◈ Members↗
FA-57173

Delivery slot awards: cleanup footprint · case 03

Cleanup is reserved inside the award instead of after it.

Auction allocation rules◈ Members↗
FA-57174

Delivery slot awards: cleanup footprint · case 04

Cleanup is reserved inside the award instead of after it.

Auction allocation rules◈ Members↗
FA-57175

Delivery slot awards: cleanup footprint · case 05

Cleanup is reserved inside the award instead of after it.

Auction allocation rules◈ Members↗
FA-57176

Delivery slot awards: transfer release before check · case 01

Award slot transfer fails to remove legitimately released capacity.

Auction allocation rules● Open access↗
FA-57177

Delivery slot awards: transfer release before check · case 02

Award slot transfer fails to remove legitimately released capacity.

Auction allocation rules◈ Members↗
FA-57178

Delivery slot awards: transfer release before check · case 03

Award slot transfer fails to remove legitimately released capacity.

Auction allocation rules◈ Members↗
FA-57179

Delivery slot awards: transfer release before check · case 04

Award slot transfer fails to remove legitimately released capacity.

Auction allocation rules◈ Members↗
FA-57180

Delivery slot awards: transfer release before check · case 05

Award slot transfer fails to remove legitimately released capacity.

Auction allocation rules◈ Members↗
FA-57181

Delivery slot awards: duration certificate · case 01

A fixed-duration winning slot package has the wrong number of slots.

Auction allocation rules● Open access↗
FA-57182

Delivery slot awards: duration certificate · case 02

A fixed-duration winning slot package has the wrong number of slots.

Auction allocation rules◈ Members↗
FA-57183

Delivery slot awards: duration certificate · case 03

A fixed-duration winning slot package has the wrong number of slots.

Auction allocation rules◈ Members↗
FA-57184

Delivery slot awards: duration certificate · case 04

A fixed-duration winning slot package has the wrong number of slots.

Auction allocation rules◈ Members↗
FA-57185

Delivery slot awards: duration certificate · case 05

A fixed-duration winning slot package has the wrong number of slots.

Auction allocation rules◈ Members↗
FA-57186

Delivery slot awards: end exclusive reservation · case 01

A delivery award reserves its neighbor closing slot or loses its opening slot.

Auction allocation rules● Open access↗
FA-57187

Delivery slot awards: end exclusive reservation · case 02

A delivery award reserves its neighbor closing slot or loses its opening slot.

Auction allocation rules◈ Members↗
FA-57188

Delivery slot awards: end exclusive reservation · case 03

A delivery award reserves its neighbor closing slot or loses its opening slot.

Auction allocation rules◈ Members↗
FA-57189

Delivery slot awards: end exclusive reservation · case 04

A delivery award reserves its neighbor closing slot or loses its opening slot.

Auction allocation rules◈ Members↗
FA-57190

Delivery slot awards: end exclusive reservation · case 05

A delivery award reserves its neighbor closing slot or loses its opening slot.

Auction allocation rules◈ Members↗
FA-57191

Bilateral confirmation: both party confirmation · case 01

A one-sided confirmation finalizes a matched award.

Auction allocation rules● Open access↗
FA-57192

Bilateral confirmation: both party confirmation · case 02

A one-sided confirmation finalizes a matched award.

Auction allocation rules◈ Members↗
FA-57193

Bilateral confirmation: both party confirmation · case 03

A one-sided confirmation finalizes a matched award.

Auction allocation rules◈ Members↗
FA-57194

Bilateral confirmation: both party confirmation · case 04

A one-sided confirmation finalizes a matched award.

Auction allocation rules◈ Members↗
FA-57195

Bilateral confirmation: both party confirmation · case 05

A one-sided confirmation finalizes a matched award.

Auction allocation rules◈ Members↗
FA-57196

Bilateral confirmation: same proposal version · case 01

Confirmations from different trade proposals are combined.

Auction allocation rules● Open access↗
FA-57197

Bilateral confirmation: same proposal version · case 02

Confirmations from different trade proposals are combined.

Auction allocation rules◈ Members↗
FA-57198

Bilateral confirmation: same proposal version · case 03

Confirmations from different trade proposals are combined.

Auction allocation rules◈ Members↗
FA-57199

Bilateral confirmation: same proposal version · case 04

Confirmations from different trade proposals are combined.

Auction allocation rules◈ Members↗
FA-57200

Bilateral confirmation: same proposal version · case 05

Confirmations from different trade proposals are combined.

Auction allocation 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 ↗