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

Purchased points with volume bonus: bonus counted toward limit · case 01

Members hit the annual purchase limit early because bonus points are counted as purchased.

Loyalty points ledgers● Open access↗
FA-60802

Purchased points with volume bonus: bonus counted toward limit · case 02

Members hit the annual purchase limit early because bonus points are counted as purchased.

Loyalty points ledgers◈ Members↗
FA-60803

Purchased points with volume bonus: bonus counted toward limit · case 03

Members hit the annual purchase limit early because bonus points are counted as purchased.

Loyalty points ledgers◈ Members↗
FA-60804

Purchased points with volume bonus: bonus counted toward limit · case 04

Members hit the annual purchase limit early because bonus points are counted as purchased.

Loyalty points ledgers◈ Members↗
FA-60805

Purchased points with volume bonus: bonus counted toward limit · case 05

Members hit the annual purchase limit early because bonus points are counted as purchased.

Loyalty points ledgers◈ Members↗
FA-60806

Purchased points with volume bonus: limit breach handling · case 01

A request that would exceed the annual limit is silently trimmed to the remaining allowance.

Loyalty points ledgers● Open access↗
FA-60807

Purchased points with volume bonus: limit breach handling · case 02

A request that would exceed the annual limit is silently trimmed to the remaining allowance.

Loyalty points ledgers◈ Members↗
FA-60808

Purchased points with volume bonus: limit breach handling · case 03

A request that would exceed the annual limit is silently trimmed to the remaining allowance.

Loyalty points ledgers◈ Members↗
FA-60809

Purchased points with volume bonus: limit breach handling · case 04

A request that would exceed the annual limit is silently trimmed to the remaining allowance.

Loyalty points ledgers◈ Members↗
FA-60810

Purchased points with volume bonus: limit breach handling · case 05

A request that would exceed the annual limit is silently trimmed to the remaining allowance.

Loyalty points ledgers◈ Members↗
FA-60811

Purchased points with volume bonus: price basis · case 01

Members are charged for the bonus points they receive free.

Loyalty points ledgers● Open access↗
FA-60812

Purchased points with volume bonus: price basis · case 02

Members are charged for the bonus points they receive free.

Loyalty points ledgers◈ Members↗
FA-60813

Purchased points with volume bonus: price basis · case 03

Members are charged for the bonus points they receive free.

Loyalty points ledgers◈ Members↗
FA-60814

Purchased points with volume bonus: price basis · case 04

Members are charged for the bonus points they receive free.

Loyalty points ledgers◈ Members↗
FA-60815

Purchased points with volume bonus: price basis · case 05

Members are charged for the bonus points they receive free.

Loyalty points ledgers◈ Members↗
FA-60816

Household pool redemption draw: requester priority · case 01

Household members are drained before the member who is redeeming.

Loyalty points ledgers● Open access↗
FA-60817

Household pool redemption draw: requester priority · case 02

Household members are drained before the member who is redeeming.

Loyalty points ledgers◈ Members↗
FA-60818

Household pool redemption draw: requester priority · case 03

Household members are drained before the member who is redeeming.

Loyalty points ledgers◈ Members↗
FA-60819

Household pool redemption draw: requester priority · case 04

Household members are drained before the member who is redeeming.

Loyalty points ledgers◈ Members↗
FA-60820

Household pool redemption draw: requester priority · case 05

Household members are drained before the member who is redeeming.

Loyalty points ledgers◈ Members↗
FA-60821

Household pool redemption draw: contribution cap · case 01

A member who limited their pool contribution is drawn beyond their limit.

Loyalty points ledgers● Open access↗
FA-60822

Household pool redemption draw: contribution cap · case 02

A member who limited their pool contribution is drawn beyond their limit.

Loyalty points ledgers◈ Members↗
FA-60823

Household pool redemption draw: contribution cap · case 03

A member who limited their pool contribution is drawn beyond their limit.

Loyalty points ledgers◈ Members↗
FA-60824

Household pool redemption draw: contribution cap · case 04

A member who limited their pool contribution is drawn beyond their limit.

Loyalty points ledgers◈ Members↗
FA-60825

Household pool redemption draw: contribution cap · case 05

A member who limited their pool contribution is drawn beyond their limit.

Loyalty points ledgers◈ Members↗
FA-60826

Household pool redemption draw: pool sufficiency · case 01

A redemption is accepted against capped balances and returns draws that fall short of the request.

Loyalty points ledgers● Open access↗
FA-60827

Household pool redemption draw: pool sufficiency · case 02

A redemption is accepted against capped balances and returns draws that fall short of the request.

Loyalty points ledgers◈ Members↗
FA-60828

Household pool redemption draw: pool sufficiency · case 03

A redemption is accepted against capped balances and returns draws that fall short of the request.

Loyalty points ledgers◈ Members↗
FA-60829

Household pool redemption draw: pool sufficiency · case 04

A redemption is accepted against capped balances and returns draws that fall short of the request.

Loyalty points ledgers◈ Members↗
FA-60830

Household pool redemption draw: pool sufficiency · case 05

A redemption is accepted against capped balances and returns draws that fall short of the request.

Loyalty points ledgers◈ Members↗
FA-60831

Household pool redemption draw: contributor order key · case 01

A capped high-balance member is drawn before members who can actually contribute more.

Loyalty points ledgers● Open access↗
FA-60832

Household pool redemption draw: contributor order key · case 02

A capped high-balance member is drawn before members who can actually contribute more.

Loyalty points ledgers◈ Members↗
FA-60833

Household pool redemption draw: contributor order key · case 03

A capped high-balance member is drawn before members who can actually contribute more.

Loyalty points ledgers◈ Members↗
FA-60834

Household pool redemption draw: contributor order key · case 04

A capped high-balance member is drawn before members who can actually contribute more.

Loyalty points ledgers◈ Members↗
FA-60835

Household pool redemption draw: contributor order key · case 05

A capped high-balance member is drawn before members who can actually contribute more.

Loyalty points ledgers◈ Members↗
FA-60836

Household pool redemption draw: remaining need tracking · case 01

A household redemption pulls points from every member, drawing far more than the reward costs.

Loyalty points ledgers● Open access↗
FA-60837

Household pool redemption draw: remaining need tracking · case 02

A household redemption pulls points from every member, drawing far more than the reward costs.

Loyalty points ledgers◈ Members↗
FA-60838

Household pool redemption draw: remaining need tracking · case 03

A household redemption pulls points from every member, drawing far more than the reward costs.

Loyalty points ledgers◈ Members↗
FA-60839

Household pool redemption draw: remaining need tracking · case 04

A household redemption pulls points from every member, drawing far more than the reward costs.

Loyalty points ledgers◈ Members↗
FA-60840

Household pool redemption draw: remaining need tracking · case 05

A household redemption pulls points from every member, drawing far more than the reward costs.

Loyalty points ledgers◈ Members↗
FA-60841

30/360 US bond basis: end day 31 is clamped regardless of the start day · case 01

Periods ending on the 31st lose a day even when the start day is early in the month.

Bond day-count conventions● Open access↗
FA-60842

30/360 US bond basis: end day 31 is clamped regardless of the start day · case 02

Periods ending on the 31st lose a day even when the start day is early in the month.

Bond day-count conventions◈ Members↗
FA-60843

30/360 US bond basis: end day 31 is clamped regardless of the start day · case 03

Periods ending on the 31st lose a day even when the start day is early in the month.

Bond day-count conventions◈ Members↗
FA-60844

30/360 US bond basis: end day 31 is clamped regardless of the start day · case 04

Periods ending on the 31st lose a day even when the start day is early in the month.

Bond day-count conventions◈ Members↗
FA-60845

30/360 US bond basis: end day 31 is clamped regardless of the start day · case 05

Periods ending on the 31st lose a day even when the start day is early in the month.

Bond day-count conventions◈ Members↗
FA-60846

30/360 US bond basis: the 28th of a leap February counts as month end · case 01

Accruals starting on 28 February of a leap year are extended as if the month had ended.

Bond day-count conventions● Open access↗
FA-60847

30/360 US bond basis: the 28th of a leap February counts as month end · case 02

Accruals starting on 28 February of a leap year are extended as if the month had ended.

Bond day-count conventions◈ Members↗
FA-60848

30/360 US bond basis: the 28th of a leap February counts as month end · case 03

Accruals starting on 28 February of a leap year are extended as if the month had ended.

Bond day-count conventions◈ Members↗
FA-60849

30/360 US bond basis: the 28th of a leap February counts as month end · case 04

Accruals starting on 28 February of a leap year are extended as if the month had ended.

Bond day-count conventions◈ Members↗
FA-60850

30/360 US bond basis: the 28th of a leap February counts as month end · case 05

Accruals starting on 28 February of a leap year are extended as if the month had ended.

Bond day-count conventions◈ Members↗
FA-60851

30/360 US bond basis: an end date on the last day of February is promoted to 30 on its own · case 01

Periods ending on the last day of February gain days although they started mid-month.

Bond day-count conventions● Open access↗
FA-60852

30/360 US bond basis: an end date on the last day of February is promoted to 30 on its own · case 02

Periods ending on the last day of February gain days although they started mid-month.

Bond day-count conventions◈ Members↗
FA-60853

30/360 US bond basis: an end date on the last day of February is promoted to 30 on its own · case 03

Periods ending on the last day of February gain days although they started mid-month.

Bond day-count conventions◈ Members↗
FA-60854

30/360 US bond basis: an end date on the last day of February is promoted to 30 on its own · case 04

Periods ending on the last day of February gain days although they started mid-month.

Bond day-count conventions◈ Members↗
FA-60855

30/360 US bond basis: an end date on the last day of February is promoted to 30 on its own · case 05

Periods ending on the last day of February gain days although they started mid-month.

Bond day-count conventions◈ Members↗
FA-60856

30/360 US bond basis: the D2 rule is evaluated before D1 is promoted from February end · case 01

A period from the end of February to a 31st keeps D2=31 and overstates the count by one day.

Bond day-count conventions● Open access↗
FA-60857

30/360 US bond basis: the D2 rule is evaluated before D1 is promoted from February end · case 02

A period from the end of February to a 31st keeps D2=31 and overstates the count by one day.

Bond day-count conventions◈ Members↗
FA-60858

30/360 US bond basis: the D2 rule is evaluated before D1 is promoted from February end · case 03

A period from the end of February to a 31st keeps D2=31 and overstates the count by one day.

Bond day-count conventions◈ Members↗
FA-60859

30/360 US bond basis: the D2 rule is evaluated before D1 is promoted from February end · case 04

A period from the end of February to a 31st keeps D2=31 and overstates the count by one day.

Bond day-count conventions◈ Members↗
FA-60860

30/360 US bond basis: the D2 rule is evaluated before D1 is promoted from February end · case 05

A period from the end of February to a 31st keeps D2=31 and overstates the count by one day.

Bond day-count conventions◈ Members↗
FA-60861

30/360 US bond basis: the D1=31 clamp is made conditional on the end date · case 01

A start on the 31st with an end mid-month produces a count one day short.

Bond day-count conventions● Open access↗
FA-60862

30/360 US bond basis: the D1=31 clamp is made conditional on the end date · case 02

A start on the 31st with an end mid-month produces a count one day short.

Bond day-count conventions◈ Members↗
FA-60863

30/360 US bond basis: the D1=31 clamp is made conditional on the end date · case 03

A start on the 31st with an end mid-month produces a count one day short.

Bond day-count conventions◈ Members↗
FA-60864

30/360 US bond basis: the D1=31 clamp is made conditional on the end date · case 04

A start on the 31st with an end mid-month produces a count one day short.

Bond day-count conventions◈ Members↗
FA-60865

30/360 US bond basis: the D1=31 clamp is made conditional on the end date · case 05

A start on the 31st with an end mid-month produces a count one day short.

Bond day-count conventions◈ Members↗
FA-60866

30E/360 ISDA with maturity exemption: a February maturity end date is promoted to day 30 · case 01

The final period of a bond maturing at the end of February accrues two or one extra days.

Bond day-count conventions● Open access↗
FA-60867

30E/360 ISDA with maturity exemption: a February maturity end date is promoted to day 30 · case 02

The final period of a bond maturing at the end of February accrues two or one extra days.

Bond day-count conventions◈ Members↗
FA-60868

30E/360 ISDA with maturity exemption: a February maturity end date is promoted to day 30 · case 03

The final period of a bond maturing at the end of February accrues two or one extra days.

Bond day-count conventions◈ Members↗
FA-60869

30E/360 ISDA with maturity exemption: a February maturity end date is promoted to day 30 · case 04

The final period of a bond maturing at the end of February accrues two or one extra days.

Bond day-count conventions◈ Members↗
FA-60870

30E/360 ISDA with maturity exemption: a February maturity end date is promoted to day 30 · case 05

The final period of a bond maturing at the end of February accrues two or one extra days.

Bond day-count conventions◈ Members↗
FA-60871

30E/360 ISDA with maturity exemption: the maturity exemption matches on day of month only · case 01

An interim February month-end that shares the maturity day number escapes promotion.

Bond day-count conventions● Open access↗
FA-60872

30E/360 ISDA with maturity exemption: the maturity exemption matches on day of month only · case 02

An interim February month-end that shares the maturity day number escapes promotion.

Bond day-count conventions◈ Members↗
FA-60873

30E/360 ISDA with maturity exemption: the maturity exemption matches on day of month only · case 03

An interim February month-end that shares the maturity day number escapes promotion.

Bond day-count conventions◈ Members↗
FA-60874

30E/360 ISDA with maturity exemption: the maturity exemption matches on day of month only · case 04

An interim February month-end that shares the maturity day number escapes promotion.

Bond day-count conventions◈ Members↗
FA-60875

30E/360 ISDA with maturity exemption: the maturity exemption matches on day of month only · case 05

An interim February month-end that shares the maturity day number escapes promotion.

Bond day-count conventions◈ Members↗
FA-60876

30E/360 ISDA with maturity exemption: February is always treated as 28 days long · case 01

Accruals starting or ending on 29 February are not recognized as month end.

Bond day-count conventions● Open access↗
FA-60877

30E/360 ISDA with maturity exemption: February is always treated as 28 days long · case 02

Accruals starting or ending on 29 February are not recognized as month end.

Bond day-count conventions◈ Members↗
FA-60878

30E/360 ISDA with maturity exemption: February is always treated as 28 days long · case 03

Accruals starting or ending on 29 February are not recognized as month end.

Bond day-count conventions◈ Members↗
FA-60879

30E/360 ISDA with maturity exemption: February is always treated as 28 days long · case 04

Accruals starting or ending on 29 February are not recognized as month end.

Bond day-count conventions◈ Members↗
FA-60880

30E/360 ISDA with maturity exemption: February is always treated as 28 days long · case 05

Accruals starting or ending on 29 February are not recognized as month end.

Bond day-count conventions◈ Members↗
FA-60881

30E/360 ISDA with maturity exemption: only a start on the 31st is promoted · case 01

A period starting at the end of February accrues from day 28 or 29 instead of day 30.

Bond day-count conventions● Open access↗
FA-60882

30E/360 ISDA with maturity exemption: only a start on the 31st is promoted · case 02

A period starting at the end of February accrues from day 28 or 29 instead of day 30.

Bond day-count conventions◈ Members↗
FA-60883

30E/360 ISDA with maturity exemption: only a start on the 31st is promoted · case 03

A period starting at the end of February accrues from day 28 or 29 instead of day 30.

Bond day-count conventions◈ Members↗
FA-60884

30E/360 ISDA with maturity exemption: only a start on the 31st is promoted · case 04

A period starting at the end of February accrues from day 28 or 29 instead of day 30.

Bond day-count conventions◈ Members↗
FA-60885

30E/360 ISDA with maturity exemption: only a start on the 31st is promoted · case 05

A period starting at the end of February accrues from day 28 or 29 instead of day 30.

Bond day-count conventions◈ Members↗
FA-60886

ICMA regular-period accrued with ex-coupon: the accrual denominator is a nominal fraction of 365 days · case 01

Accrued interest drifts from the ICMA value for periods that are not exactly 365/freq days.

Bond day-count conventions● Open access↗
FA-60887

ICMA regular-period accrued with ex-coupon: the accrual denominator is a nominal fraction of 365 days · case 02

Accrued interest drifts from the ICMA value for periods that are not exactly 365/freq days.

Bond day-count conventions◈ Members↗
FA-60888

ICMA regular-period accrued with ex-coupon: the accrual denominator is a nominal fraction of 365 days · case 03

Accrued interest drifts from the ICMA value for periods that are not exactly 365/freq days.

Bond day-count conventions◈ Members↗
FA-60889

ICMA regular-period accrued with ex-coupon: the accrual denominator is a nominal fraction of 365 days · case 04

Accrued interest drifts from the ICMA value for periods that are not exactly 365/freq days.

Bond day-count conventions◈ Members↗
FA-60890

ICMA regular-period accrued with ex-coupon: the accrual denominator is a nominal fraction of 365 days · case 05

Accrued interest drifts from the ICMA value for periods that are not exactly 365/freq days.

Bond day-count conventions◈ Members↗
FA-60891

ICMA regular-period accrued with ex-coupon: the settlement day is counted as an accrued day · case 01

Every positive accrual is one day of coupon too high.

Bond day-count conventions● Open access↗
FA-60892

ICMA regular-period accrued with ex-coupon: the settlement day is counted as an accrued day · case 02

Every positive accrual is one day of coupon too high.

Bond day-count conventions◈ Members↗
FA-60893

ICMA regular-period accrued with ex-coupon: the settlement day is counted as an accrued day · case 03

Every positive accrual is one day of coupon too high.

Bond day-count conventions◈ Members↗
FA-60894

ICMA regular-period accrued with ex-coupon: the settlement day is counted as an accrued day · case 04

Every positive accrual is one day of coupon too high.

Bond day-count conventions◈ Members↗
FA-60895

ICMA regular-period accrued with ex-coupon: the settlement day is counted as an accrued day · case 05

Every positive accrual is one day of coupon too high.

Bond day-count conventions◈ Members↗
FA-60896

ICMA regular-period accrued with ex-coupon: a settlement exactly exdays before the coupon is not ex-coupon · case 01

Trades settling on the first ex-coupon day receive positive accrued interest.

Bond day-count conventions● Open access↗
FA-60897

ICMA regular-period accrued with ex-coupon: a settlement exactly exdays before the coupon is not ex-coupon · case 02

Trades settling on the first ex-coupon day receive positive accrued interest.

Bond day-count conventions◈ Members↗
FA-60898

ICMA regular-period accrued with ex-coupon: a settlement exactly exdays before the coupon is not ex-coupon · case 03

Trades settling on the first ex-coupon day receive positive accrued interest.

Bond day-count conventions◈ Members↗
FA-60899

ICMA regular-period accrued with ex-coupon: a settlement exactly exdays before the coupon is not ex-coupon · case 04

Trades settling on the first ex-coupon day receive positive accrued interest.

Bond day-count conventions◈ Members↗
FA-60900

ICMA regular-period accrued with ex-coupon: a settlement exactly exdays before the coupon is not ex-coupon · case 05

Trades settling on the first ex-coupon day receive positive accrued interest.

Bond day-count conventions◈ 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 ↗