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
Renewal price with lock and increase cap: lock never raises price · case 01
When list prices drop below the locked price, locked customers pay more than new customers.
Renewal price with lock and increase cap: lock never raises price · case 02
When list prices drop below the locked price, locked customers pay more than new customers.
Renewal price with lock and increase cap: lock never raises price · case 03
When list prices drop below the locked price, locked customers pay more than new customers.
Renewal price with lock and increase cap: lock never raises price · case 04
When list prices drop below the locked price, locked customers pay more than new customers.
Renewal price with lock and increase cap: lock never raises price · case 05
When list prices drop below the locked price, locked customers pay more than new customers.
Renewal price with lock and increase cap: increase cap base · case 01
Renewal increases exceed the promised percentage cap.
Renewal price with lock and increase cap: increase cap base · case 02
Renewal increases exceed the promised percentage cap.
Renewal price with lock and increase cap: increase cap base · case 03
Renewal increases exceed the promised percentage cap.
Renewal price with lock and increase cap: increase cap base · case 04
Renewal increases exceed the promised percentage cap.
Renewal price with lock and increase cap: increase cap base · case 05
Renewal increases exceed the promised percentage cap.
Package pricing with milli-unit usage: unit rounding grain · case 01
Customers with many small events are billed for far more units than they used.
Package pricing with milli-unit usage: unit rounding grain · case 02
Customers with many small events are billed for far more units than they used.
Package pricing with milli-unit usage: unit rounding grain · case 03
Customers with many small events are billed for far more units than they used.
Package pricing with milli-unit usage: unit rounding grain · case 04
Customers with many small events are billed for far more units than they used.
Package pricing with milli-unit usage: unit rounding grain · case 05
Customers with many small events are billed for far more units than they used.
Package pricing with milli-unit usage: free units before packaging · case 01
The free allowance never reduces the bill.
Package pricing with milli-unit usage: free units before packaging · case 02
The free allowance never reduces the bill.
Package pricing with milli-unit usage: free units before packaging · case 03
The free allowance never reduces the bill.
Package pricing with milli-unit usage: free units before packaging · case 04
The free allowance never reduces the bill.
Package pricing with milli-unit usage: free units before packaging · case 05
The free allowance never reduces the bill.
Package pricing with milli-unit usage: round-up packaging · case 01
Exact package multiples and zero usage are billed an extra package.
Package pricing with milli-unit usage: round-up packaging · case 02
Exact package multiples and zero usage are billed an extra package.
Package pricing with milli-unit usage: round-up packaging · case 03
Exact package multiples and zero usage are billed an extra package.
Package pricing with milli-unit usage: round-up packaging · case 04
Exact package multiples and zero usage are billed an extra package.
Package pricing with milli-unit usage: round-up packaging · case 05
Exact package multiples and zero usage are billed an extra package.
Unused-time credit based on amount paid: credit basis · case 01
Customers who paid with a discount receive credits at the full list price.
Unused-time credit based on amount paid: credit basis · case 02
Customers who paid with a discount receive credits at the full list price.
Unused-time credit based on amount paid: credit basis · case 03
Customers who paid with a discount receive credits at the full list price.
Unused-time credit based on amount paid: credit basis · case 04
Customers who paid with a discount receive credits at the full list price.
Unused-time credit based on amount paid: credit basis · case 05
Customers who paid with a discount receive credits at the full list price.
Unused-time credit based on amount paid: partially paid invoices · case 01
Customers who paid part of an invoice get no credit for unused time.
Unused-time credit based on amount paid: partially paid invoices · case 02
Customers who paid part of an invoice get no credit for unused time.
Unused-time credit based on amount paid: partially paid invoices · case 03
Customers who paid part of an invoice get no credit for unused time.
Unused-time credit based on amount paid: partially paid invoices · case 04
Customers who paid part of an invoice get no credit for unused time.
Unused-time credit based on amount paid: partially paid invoices · case 05
Customers who paid part of an invoice get no credit for unused time.
Unused-time credit based on amount paid: refunded invoice exclusion · case 01
Customers whose payment was already refunded receive an unused-time credit on top of the refund.
Unused-time credit based on amount paid: refunded invoice exclusion · case 02
Customers whose payment was already refunded receive an unused-time credit on top of the refund.
Unused-time credit based on amount paid: refunded invoice exclusion · case 03
Customers whose payment was already refunded receive an unused-time credit on top of the refund.
Unused-time credit based on amount paid: refunded invoice exclusion · case 04
Customers whose payment was already refunded receive an unused-time credit on top of the refund.
Unused-time credit based on amount paid: refunded invoice exclusion · case 05
Customers whose payment was already refunded receive an unused-time credit on top of the refund.
FIFO perpetual issue: oldest layer selection · case 01
Issues are costed at the most recent receipt prices and the oldest layers linger on the balance sheet.
FIFO perpetual issue: oldest layer selection · case 02
Issues are costed at the most recent receipt prices and the oldest layers linger on the balance sheet.
FIFO perpetual issue: oldest layer selection · case 03
Issues are costed at the most recent receipt prices and the oldest layers linger on the balance sheet.
FIFO perpetual issue: oldest layer selection · case 04
Issues are costed at the most recent receipt prices and the oldest layers linger on the balance sheet.
FIFO perpetual issue: oldest layer selection · case 05
Issues are costed at the most recent receipt prices and the oldest layers linger on the balance sheet.
FIFO perpetual issue: stock sufficiency boundary · case 01
An issue that exactly empties the warehouse is rejected as short even though every unit is on hand.
FIFO perpetual issue: stock sufficiency boundary · case 02
An issue that exactly empties the warehouse is rejected as short even though every unit is on hand.
FIFO perpetual issue: stock sufficiency boundary · case 03
An issue that exactly empties the warehouse is rejected as short even though every unit is on hand.
FIFO perpetual issue: stock sufficiency boundary · case 04
An issue that exactly empties the warehouse is rejected as short even though every unit is on hand.
FIFO perpetual issue: stock sufficiency boundary · case 05
An issue that exactly empties the warehouse is rejected as short even though every unit is on hand.
FIFO perpetual issue: same-cost receipt merge · case 01
A receipt at a different price is folded into the previous layer, so later issues use the stale price.
FIFO perpetual issue: same-cost receipt merge · case 02
A receipt at a different price is folded into the previous layer, so later issues use the stale price.
FIFO perpetual issue: same-cost receipt merge · case 03
A receipt at a different price is folded into the previous layer, so later issues use the stale price.
FIFO perpetual issue: same-cost receipt merge · case 04
A receipt at a different price is folded into the previous layer, so later issues use the stale price.
FIFO perpetual issue: same-cost receipt merge · case 05
A receipt at a different price is folded into the previous layer, so later issues use the stale price.
FIFO perpetual issue: issue cost accumulation · case 01
An issue that spans several layers reports only the cost of the last layer touched.
FIFO perpetual issue: issue cost accumulation · case 02
An issue that spans several layers reports only the cost of the last layer touched.
FIFO perpetual issue: issue cost accumulation · case 03
An issue that spans several layers reports only the cost of the last layer touched.
FIFO perpetual issue: issue cost accumulation · case 04
An issue that spans several layers reports only the cost of the last layer touched.
FIFO perpetual issue: issue cost accumulation · case 05
An issue that spans several layers reports only the cost of the last layer touched.
FIFO perpetual issue: non-positive receipt filter · case 01
A zero-quantity receipt line creates an empty cost layer that shows up in the valuation report.
FIFO perpetual issue: non-positive receipt filter · case 02
A zero-quantity receipt line creates an empty cost layer that shows up in the valuation report.
FIFO perpetual issue: non-positive receipt filter · case 03
A zero-quantity receipt line creates an empty cost layer that shows up in the valuation report.
FIFO perpetual issue: non-positive receipt filter · case 04
A zero-quantity receipt line creates an empty cost layer that shows up in the valuation report.
FIFO perpetual issue: non-positive receipt filter · case 05
A zero-quantity receipt line creates an empty cost layer that shows up in the valuation report.
FIFO perpetual issue: depleted layer removal · case 01
Fully consumed layers remain in the layer list with zero quantity.
FIFO perpetual issue: depleted layer removal · case 02
Fully consumed layers remain in the layer list with zero quantity.
FIFO perpetual issue: depleted layer removal · case 03
Fully consumed layers remain in the layer list with zero quantity.
FIFO perpetual issue: depleted layer removal · case 04
Fully consumed layers remain in the layer list with zero quantity.
FIFO perpetual issue: depleted layer removal · case 05
Fully consumed layers remain in the layer list with zero quantity.
Periodic LIFO year-end layering: increment layer pricing order · case 01
The year-end LIFO increment is valued at the latest purchase prices, overstating ending inventory in inflationary years.
Periodic LIFO year-end layering: increment layer pricing order · case 02
The year-end LIFO increment is valued at the latest purchase prices, overstating ending inventory in inflationary years.
Periodic LIFO year-end layering: increment layer pricing order · case 03
The year-end LIFO increment is valued at the latest purchase prices, overstating ending inventory in inflationary years.
Periodic LIFO year-end layering: increment layer pricing order · case 04
The year-end LIFO increment is valued at the latest purchase prices, overstating ending inventory in inflationary years.
Periodic LIFO year-end layering: increment layer pricing order · case 05
The year-end LIFO increment is valued at the latest purchase prices, overstating ending inventory in inflationary years.
Periodic LIFO year-end layering: liquidation direction · case 01
A LIFO liquidation keeps the newest base layers and discards the oldest, so the surviving layers carry recent prices.
Periodic LIFO year-end layering: liquidation direction · case 02
A LIFO liquidation keeps the newest base layers and discards the oldest, so the surviving layers carry recent prices.
Periodic LIFO year-end layering: liquidation direction · case 03
A LIFO liquidation keeps the newest base layers and discards the oldest, so the surviving layers carry recent prices.
Periodic LIFO year-end layering: liquidation direction · case 04
A LIFO liquidation keeps the newest base layers and discards the oldest, so the surviving layers carry recent prices.
Periodic LIFO year-end layering: liquidation direction · case 05
A LIFO liquidation keeps the newest base layers and discards the oldest, so the surviving layers carry recent prices.
Periodic LIFO year-end layering: available quantity bound · case 01
An impossible ending count larger than purchases alone is rejected, even though beginning units make it valid.
Periodic LIFO year-end layering: available quantity bound · case 02
An impossible ending count larger than purchases alone is rejected, even though beginning units make it valid.
Periodic LIFO year-end layering: available quantity bound · case 03
An impossible ending count larger than purchases alone is rejected, even though beginning units make it valid.
Periodic LIFO year-end layering: available quantity bound · case 04
An impossible ending count larger than purchases alone is rejected, even though beginning units make it valid.
Periodic LIFO year-end layering: available quantity bound · case 05
An impossible ending count larger than purchases alone is rejected, even though beginning units make it valid.
Periodic LIFO year-end layering: empty layer suppression · case 01
Liquidation output contains zero-quantity layers for fully liquidated base years.
Periodic LIFO year-end layering: empty layer suppression · case 02
Liquidation output contains zero-quantity layers for fully liquidated base years.
Periodic LIFO year-end layering: empty layer suppression · case 03
Liquidation output contains zero-quantity layers for fully liquidated base years.
Periodic LIFO year-end layering: empty layer suppression · case 04
Liquidation output contains zero-quantity layers for fully liquidated base years.
Periodic LIFO year-end layering: empty layer suppression · case 05
Liquidation output contains zero-quantity layers for fully liquidated base years.
Periodic LIFO year-end layering: negative count rejection · case 01
A negative physical count is accepted and produces negative layers instead of an error.
Periodic LIFO year-end layering: negative count rejection · case 02
A negative physical count is accepted and produces negative layers instead of an error.
Periodic LIFO year-end layering: negative count rejection · case 03
A negative physical count is accepted and produces negative layers instead of an error.
Periodic LIFO year-end layering: negative count rejection · case 04
A negative physical count is accepted and produces negative layers instead of an error.
Periodic LIFO year-end layering: negative count rejection · case 05
A negative physical count is accepted and produces negative layers instead of an error.
Periodic LIFO year-end layering: increment exhaustion stop · case 01
The increment layer absorbs units from every purchase even after the increment is satisfied.
Periodic LIFO year-end layering: increment exhaustion stop · case 02
The increment layer absorbs units from every purchase even after the increment is satisfied.
Periodic LIFO year-end layering: increment exhaustion stop · case 03
The increment layer absorbs units from every purchase even after the increment is satisfied.
Periodic LIFO year-end layering: increment exhaustion stop · case 04
The increment layer absorbs units from every purchase even after the increment is satisfied.
Periodic LIFO year-end layering: increment exhaustion stop · case 05
The increment layer absorbs units from every purchase even after the increment is satisfied.
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 ↗