FA-95039 / Warehouse slotting and bin packing / Member archive

Hazmat audit: violation pairs not canonical · case 04

The same violation appears in either orientation and the report is not stably ordered.

Member previewVariant 4 · 3 implementations · 8 checks per implementation

Case contract

placements [[sku, hazard class, aisle, bay]]; rules [[class_a, class_b, min_bay_gap]] apply in either order within the same aisle. A rule class matches a hazard class equal to it or a division of it ("4" matches "4.1"). A pair violates when |bay difference| < min_gap. Different SKUs only. Return sorted unique [sku_low, sku_high] pairs.

Why this case matters

Dangerous goods storage requires separation between incompatible hazard classes.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
reverse order	`[["O", "G"]]`	`[["G", "O"]]`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.