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 ↗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
Pallet build: partial top layer not counted · case 01
Height is reported one layer short when the top layer is partial.
Pallet build: partial top layer not counted · case 02
Height is reported one layer short when the top layer is partial.
Pallet build: partial top layer not counted · case 03
Height is reported one layer short when the top layer is partial.
Pallet build: partial top layer not counted · case 04
Height is reported one layer short when the top layer is partial.
Pallet build: partial top layer not counted · case 05
Height is reported one layer short when the top layer is partial.
Pallet build: weight limit not applied · case 01
Dense cases are stacked to the height limit and the pallet exceeds its gross weight rating.
Pallet build: weight limit not applied · case 02
Dense cases are stacked to the height limit and the pallet exceeds its gross weight rating.
Pallet build: weight limit not applied · case 03
Dense cases are stacked to the height limit and the pallet exceeds its gross weight rating.
Pallet build: weight limit not applied · case 04
Dense cases are stacked to the height limit and the pallet exceeds its gross weight rating.
Pallet build: weight limit not applied · case 05
Dense cases are stacked to the height limit and the pallet exceeds its gross weight rating.
Hazmat audit: class rules ignore divisions · case 01
A rule written for a whole hazard class misses products labelled with a division of that class.
Hazmat audit: class rules ignore divisions · case 02
A rule written for a whole hazard class misses products labelled with a division of that class.
Hazmat audit: class rules ignore divisions · case 03
A rule written for a whole hazard class misses products labelled with a division of that class.
Hazmat audit: class rules ignore divisions · case 04
A rule written for a whole hazard class misses products labelled with a division of that class.
Hazmat audit: class rules ignore divisions · case 05
A rule written for a whole hazard class misses products labelled with a division of that class.
Hazmat audit: rule applied in one order only · case 01
An incompatible pair is reported or missed depending on which product appears first in the placement list.
Hazmat audit: rule applied in one order only · case 02
An incompatible pair is reported or missed depending on which product appears first in the placement list.
Hazmat audit: rule applied in one order only · case 03
An incompatible pair is reported or missed depending on which product appears first in the placement list.
Hazmat audit: rule applied in one order only · case 04
An incompatible pair is reported or missed depending on which product appears first in the placement list.
Hazmat audit: rule applied in one order only · case 05
An incompatible pair is reported or missed depending on which product appears first in the placement list.
Hazmat audit: required separation treated as violation · case 01
Products separated by exactly the required number of bays are flagged.
Hazmat audit: required separation treated as violation · case 02
Products separated by exactly the required number of bays are flagged.
Hazmat audit: required separation treated as violation · case 03
Products separated by exactly the required number of bays are flagged.
Hazmat audit: required separation treated as violation · case 04
Products separated by exactly the required number of bays are flagged.
Hazmat audit: required separation treated as violation · case 05
Products separated by exactly the required number of bays are flagged.
Hazmat audit: bays compared across aisles · case 01
Products in different aisles with the same bay number are reported as too close.
Hazmat audit: bays compared across aisles · case 02
Products in different aisles with the same bay number are reported as too close.
Hazmat audit: bays compared across aisles · case 03
Products in different aisles with the same bay number are reported as too close.
Hazmat audit: bays compared across aisles · case 04
Products in different aisles with the same bay number are reported as too close.
Hazmat audit: bays compared across aisles · case 05
Products in different aisles with the same bay number are reported as too close.
Hazmat audit: SKU flagged against itself · case 01
A SKU stored in two slots is reported as incompatible with itself.
Hazmat audit: SKU flagged against itself · case 02
A SKU stored in two slots is reported as incompatible with itself.
Hazmat audit: SKU flagged against itself · case 03
A SKU stored in two slots is reported as incompatible with itself.
Hazmat audit: SKU flagged against itself · case 04
A SKU stored in two slots is reported as incompatible with itself.
Hazmat audit: SKU flagged against itself · case 05
A SKU stored in two slots is reported as incompatible with itself.
Hazmat audit: violation pairs not canonical · case 01
The same violation appears in either orientation and the report is not stably ordered.
Hazmat audit: violation pairs not canonical · case 02
The same violation appears in either orientation and the report is not stably ordered.
Hazmat audit: violation pairs not canonical · case 03
The same violation appears in either orientation and the report is not stably ordered.
Hazmat audit: violation pairs not canonical · case 04
The same violation appears in either orientation and the report is not stably ordered.
Hazmat audit: violation pairs not canonical · case 05
The same violation appears in either orientation and the report is not stably ordered.
FEFO putaway: exact remaining room rejected · case 01
A receipt that would fill a bin exactly is sent to a fresh bin, fragmenting the lot.
FEFO putaway: exact remaining room rejected · case 02
A receipt that would fill a bin exactly is sent to a fresh bin, fragmenting the lot.
FEFO putaway: exact remaining room rejected · case 03
A receipt that would fill a bin exactly is sent to a fresh bin, fragmenting the lot.
FEFO putaway: exact remaining room rejected · case 04
A receipt that would fill a bin exactly is sent to a fresh bin, fragmenting the lot.
FEFO putaway: exact remaining room rejected · case 05
A receipt that would fill a bin exactly is sent to a fresh bin, fragmenting the lot.
FEFO putaway: 30-day window made exclusive · case 01
A lot expiring exactly 30 days from the resident lot is refused a shared bin.
FEFO putaway: 30-day window made exclusive · case 02
A lot expiring exactly 30 days from the resident lot is refused a shared bin.
FEFO putaway: 30-day window made exclusive · case 03
A lot expiring exactly 30 days from the resident lot is refused a shared bin.
FEFO putaway: 30-day window made exclusive · case 04
A lot expiring exactly 30 days from the resident lot is refused a shared bin.
FEFO putaway: 30-day window made exclusive · case 05
A lot expiring exactly 30 days from the resident lot is refused a shared bin.
FEFO putaway: mixed lot bin chosen by distance only · case 01
The receipt joins a nearby bin with a distant expiry while a bin with a matching expiry is available.
FEFO putaway: mixed lot bin chosen by distance only · case 02
The receipt joins a nearby bin with a distant expiry while a bin with a matching expiry is available.
FEFO putaway: mixed lot bin chosen by distance only · case 03
The receipt joins a nearby bin with a distant expiry while a bin with a matching expiry is available.
FEFO putaway: mixed lot bin chosen by distance only · case 04
The receipt joins a nearby bin with a distant expiry while a bin with a matching expiry is available.
FEFO putaway: mixed lot bin chosen by distance only · case 05
The receipt joins a nearby bin with a distant expiry while a bin with a matching expiry is available.
FEFO putaway: largest empty bin chosen · case 01
Small receipts consume the largest empty bins far from the pick face.
FEFO putaway: largest empty bin chosen · case 02
Small receipts consume the largest empty bins far from the pick face.
FEFO putaway: largest empty bin chosen · case 03
Small receipts consume the largest empty bins far from the pick face.
FEFO putaway: largest empty bin chosen · case 04
Small receipts consume the largest empty bins far from the pick face.
FEFO putaway: largest empty bin chosen · case 05
Small receipts consume the largest empty bins far from the pick face.
FEFO putaway: zero-quantity labelled bin not empty · case 01
Bins that still carry a stale SKU label after being emptied are never reused.
FEFO putaway: zero-quantity labelled bin not empty · case 02
Bins that still carry a stale SKU label after being emptied are never reused.
FEFO putaway: zero-quantity labelled bin not empty · case 03
Bins that still carry a stale SKU label after being emptied are never reused.
FEFO putaway: zero-quantity labelled bin not empty · case 04
Bins that still carry a stale SKU label after being emptied are never reused.
FEFO putaway: zero-quantity labelled bin not empty · case 05
Bins that still carry a stale SKU label after being emptied are never reused.
FEFO putaway: lot code matched across SKUs · case 01
A receipt is put into a bin of a different SKU that happens to share the lot code.
FEFO putaway: lot code matched across SKUs · case 02
A receipt is put into a bin of a different SKU that happens to share the lot code.
FEFO putaway: lot code matched across SKUs · case 03
A receipt is put into a bin of a different SKU that happens to share the lot code.
FEFO putaway: lot code matched across SKUs · case 04
A receipt is put into a bin of a different SKU that happens to share the lot code.
FEFO putaway: lot code matched across SKUs · case 05
A receipt is put into a bin of a different SKU that happens to share the lot code.
Slot fit: stacking limit ignored · case 01
Crushable cartons are stacked to the full slot height.
Slot fit: stacking limit ignored · case 02
Crushable cartons are stacked to the full slot height.
Slot fit: stacking limit ignored · case 03
Crushable cartons are stacked to the full slot height.
Slot fit: stacking limit ignored · case 04
Crushable cartons are stacked to the full slot height.
Slot fit: stacking limit ignored · case 05
Crushable cartons are stacked to the full slot height.
Slot fit: this-side-up units laid down · case 01
Units marked upright-only are counted in lying-down orientations.
Slot fit: this-side-up units laid down · case 02
Units marked upright-only are counted in lying-down orientations.
Slot fit: this-side-up units laid down · case 03
Units marked upright-only are counted in lying-down orientations.
Slot fit: this-side-up units laid down · case 04
Units marked upright-only are counted in lying-down orientations.
Slot fit: this-side-up units laid down · case 05
Units marked upright-only are counted in lying-down orientations.
Slot fit: utilization rounded instead of floored · case 01
Cube utilization is overstated by one basis point on fractional values.
Slot fit: utilization rounded instead of floored · case 02
Cube utilization is overstated by one basis point on fractional values.
Slot fit: utilization rounded instead of floored · case 03
Cube utilization is overstated by one basis point on fractional values.
Slot fit: utilization rounded instead of floored · case 04
Cube utilization is overstated by one basis point on fractional values.
Slot fit: utilization rounded instead of floored · case 05
Cube utilization is overstated by one basis point on fractional values.
Slot fit: first orientation taken · case 01
Slot capacity is understated when a rotated orientation packs more units.
Slot fit: first orientation taken · case 02
Slot capacity is understated when a rotated orientation packs more units.
Slot fit: first orientation taken · case 03
Slot capacity is understated when a rotated orientation packs more units.
Slot fit: first orientation taken · case 04
Slot capacity is understated when a rotated orientation packs more units.
Slot fit: first orientation taken · case 05
Slot capacity is understated when a rotated orientation packs more units.
Slot fit: zero stack limit means none · case 01
Slots for units with no stacking limit report zero capacity.
Slot fit: zero stack limit means none · case 02
Slots for units with no stacking limit report zero capacity.
Slot fit: zero stack limit means none · case 03
Slots for units with no stacking limit report zero capacity.
Slot fit: zero stack limit means none · case 04
Slots for units with no stacking limit report zero capacity.
Slot fit: zero stack limit means none · case 05
Slots for units with no stacking limit report zero capacity.
Reserve allocation: exact-fit pallet not cleaned out · case 01
A pallet holding exactly the remaining need is picked partially instead of moved whole.
Reserve allocation: exact-fit pallet not cleaned out · case 02
A pallet holding exactly the remaining need is picked partially instead of moved whole.
Reserve allocation: exact-fit pallet not cleaned out · case 03
A pallet holding exactly the remaining need is picked partially instead of moved whole.
Reserve allocation: exact-fit pallet not cleaned out · case 04
A pallet holding exactly the remaining need is picked partially instead of moved whole.
Reserve allocation: exact-fit pallet not cleaned out · case 05
A pallet holding exactly the remaining need is picked partially instead of moved whole.
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 ↗