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
Re-keying instance overrides after a series start or interval change: index map · case 01
After changing weekly to every-two-weeks, exceptions attach to the wrong occurrences.
Re-keying instance overrides after a series start or interval change: index map · case 02
After changing weekly to every-two-weeks, exceptions attach to the wrong occurrences.
Re-keying instance overrides after a series start or interval change: index map · case 03
After changing weekly to every-two-weeks, exceptions attach to the wrong occurrences.
Re-keying instance overrides after a series start or interval change: index map · case 04
After changing weekly to every-two-weeks, exceptions attach to the wrong occurrences.
Re-keying instance overrides after a series start or interval change: index map · case 05
After changing weekly to every-two-weeks, exceptions attach to the wrong occurrences.
Re-keying instance overrides after a series start or interval change: noop drop · case 01
A moved instance whose target now coincides with its new slot is kept as a redundant exception, and a former no-op is dropped although it now moves the instance.
Re-keying instance overrides after a series start or interval change: noop drop · case 02
A moved instance whose target now coincides with its new slot is kept as a redundant exception, and a former no-op is dropped although it now moves the instance.
Re-keying instance overrides after a series start or interval change: noop drop · case 03
A moved instance whose target now coincides with its new slot is kept as a redundant exception, and a former no-op is dropped although it now moves the instance.
Re-keying instance overrides after a series start or interval change: noop drop · case 04
A moved instance whose target now coincides with its new slot is kept as a redundant exception, and a former no-op is dropped although it now moves the instance.
Re-keying instance overrides after a series start or interval change: noop drop · case 05
A moved instance whose target now coincides with its new slot is kept as a redundant exception, and a former no-op is dropped although it now moves the instance.
Re-keying instance overrides after a series start or interval change: target policy · case 01
Instances that were explicitly rescheduled to a fixed date are shifted along with the series.
Re-keying instance overrides after a series start or interval change: target policy · case 02
Instances that were explicitly rescheduled to a fixed date are shifted along with the series.
Re-keying instance overrides after a series start or interval change: target policy · case 03
Instances that were explicitly rescheduled to a fixed date are shifted along with the series.
Re-keying instance overrides after a series start or interval change: target policy · case 04
Instances that were explicitly rescheduled to a fixed date are shifted along with the series.
Re-keying instance overrides after a series start or interval change: target policy · case 05
Instances that were explicitly rescheduled to a fixed date are shifted along with the series.
Re-keying instance overrides after a series start or interval change: output order · case 01
Exceptions are returned in edit order, not by occurrence.
Re-keying instance overrides after a series start or interval change: output order · case 02
Exceptions are returned in edit order, not by occurrence.
Re-keying instance overrides after a series start or interval change: output order · case 03
Exceptions are returned in edit order, not by occurrence.
Re-keying instance overrides after a series start or interval change: output order · case 04
Exceptions are returned in edit order, not by occurrence.
Re-keying instance overrides after a series start or interval change: output order · case 05
Exceptions are returned in edit order, not by occurrence.
Next due date for a recurring task after completions: completion order · case 01
Completions synced out of order leave a scheduled task on a stale due date.
Next due date for a recurring task after completions: completion order · case 02
Completions synced out of order leave a scheduled task on a stale due date.
Next due date for a recurring task after completions: completion order · case 03
Completions synced out of order leave a scheduled task on a stale due date.
Next due date for a recurring task after completions: completion order · case 04
Completions synced out of order leave a scheduled task on a stale due date.
Next due date for a recurring task after completions: completion order · case 05
Completions synced out of order leave a scheduled task on a stale due date.
Next due date for a recurring task after completions: regenerate base · case 01
A regenerating task completed early is rescheduled from its old due date.
Next due date for a recurring task after completions: regenerate base · case 02
A regenerating task completed early is rescheduled from its old due date.
Next due date for a recurring task after completions: regenerate base · case 03
A regenerating task completed early is rescheduled from its old due date.
Next due date for a recurring task after completions: regenerate base · case 04
A regenerating task completed early is rescheduled from its old due date.
Next due date for a recurring task after completions: regenerate base · case 05
A regenerating task completed early is rescheduled from its old due date.
Next due date for a recurring task after completions: catch up · case 01
A scheduled task completed late on its next due date stays due that same day.
Next due date for a recurring task after completions: catch up · case 02
A scheduled task completed late on its next due date stays due that same day.
Next due date for a recurring task after completions: catch up · case 03
A scheduled task completed late on its next due date stays due that same day.
Next due date for a recurring task after completions: catch up · case 04
A scheduled task completed late on its next due date stays due that same day.
Next due date for a recurring task after completions: catch up · case 05
A scheduled task completed late on its next due date stays due that same day.
Next due date for a recurring task after completions: series end · case 01
The final occurrence falling exactly on the end date is dropped.
Next due date for a recurring task after completions: series end · case 02
The final occurrence falling exactly on the end date is dropped.
Next due date for a recurring task after completions: series end · case 03
The final occurrence falling exactly on the end date is dropped.
Next due date for a recurring task after completions: series end · case 04
The final occurrence falling exactly on the end date is dropped.
Next due date for a recurring task after completions: series end · case 05
The final occurrence falling exactly on the end date is dropped.
Forward day-count period with last-day extension and service add-on: weekend test · case 01
A period ending on a Saturday is left due on the Saturday.
Forward day-count period with last-day extension and service add-on: weekend test · case 02
A period ending on a Saturday is left due on the Saturday.
Forward day-count period with last-day extension and service add-on: weekend test · case 03
A period ending on a Saturday is left due on the Saturday.
Forward day-count period with last-day extension and service add-on: weekend test · case 04
A period ending on a Saturday is left due on the Saturday.
Forward day-count period with last-day extension and service add-on: weekend test · case 05
A period ending on a Saturday is left due on the Saturday.
Forward day-count period with last-day extension and service add-on: roll loop · case 01
A period ending on Saturday is extended only to Sunday.
Forward day-count period with last-day extension and service add-on: roll loop · case 02
A period ending on Saturday is extended only to Sunday.
Forward day-count period with last-day extension and service add-on: roll loop · case 03
A period ending on Saturday is extended only to Sunday.
Forward day-count period with last-day extension and service add-on: roll loop · case 04
A period ending on Saturday is extended only to Sunday.
Forward day-count period with last-day extension and service add-on: roll loop · case 05
A period ending on Saturday is extended only to Sunday.
Forward day-count period with last-day extension and service add-on: trigger exclusion · case 01
A 14-day period expires a day early because the trigger day is counted as day one.
Forward day-count period with last-day extension and service add-on: trigger exclusion · case 02
A 14-day period expires a day early because the trigger day is counted as day one.
Forward day-count period with last-day extension and service add-on: trigger exclusion · case 03
A 14-day period expires a day early because the trigger day is counted as day one.
Forward day-count period with last-day extension and service add-on: trigger exclusion · case 04
A 14-day period expires a day early because the trigger day is counted as day one.
Forward day-count period with last-day extension and service add-on: trigger exclusion · case 05
A 14-day period expires a day early because the trigger day is counted as day one.
Forward day-count period with last-day extension and service add-on: service scope · case 01
Electronic service still receives three extra days.
Forward day-count period with last-day extension and service add-on: service scope · case 02
Electronic service still receives three extra days.
Forward day-count period with last-day extension and service add-on: service scope · case 03
Electronic service still receives three extra days.
Forward day-count period with last-day extension and service add-on: service scope · case 04
Electronic service still receives three extra days.
Forward day-count period with last-day extension and service add-on: service scope · case 05
Electronic service still receives three extra days.
Forward day-count period with last-day extension and service add-on: service addon order · case 01
When the base period ends on a weekend, mail service yields a deadline one or two days early.
Forward day-count period with last-day extension and service add-on: service addon order · case 02
When the base period ends on a weekend, mail service yields a deadline one or two days early.
Forward day-count period with last-day extension and service add-on: service addon order · case 03
When the base period ends on a weekend, mail service yields a deadline one or two days early.
Forward day-count period with last-day extension and service add-on: service addon order · case 04
When the base period ends on a weekend, mail service yields a deadline one or two days early.
Forward day-count period with last-day extension and service add-on: service addon order · case 05
When the base period ends on a weekend, mail service yields a deadline one or two days early.
Short periods counted in court days with observed holidays: observed shift · case 01
A July 4 falling on Sunday does not close the court on Monday July 5.
Short periods counted in court days with observed holidays: observed shift · case 02
A July 4 falling on Sunday does not close the court on Monday July 5.
Short periods counted in court days with observed holidays: observed shift · case 03
A July 4 falling on Sunday does not close the court on Monday July 5.
Short periods counted in court days with observed holidays: observed shift · case 04
A July 4 falling on Sunday does not close the court on Monday July 5.
Short periods counted in court days with observed holidays: observed shift · case 05
A July 4 falling on Sunday does not close the court on Monday July 5.
Short periods counted in court days with observed holidays: short threshold · case 01
An 11-day period skips weekends although only shorter periods do.
Short periods counted in court days with observed holidays: short threshold · case 02
An 11-day period skips weekends although only shorter periods do.
Short periods counted in court days with observed holidays: short threshold · case 03
An 11-day period skips weekends although only shorter periods do.
Short periods counted in court days with observed holidays: short threshold · case 04
An 11-day period skips weekends although only shorter periods do.
Short periods counted in court days with observed holidays: short threshold · case 05
An 11-day period skips weekends although only shorter periods do.
Short periods counted in court days with observed holidays: skip rule · case 01
A 7-day period counts an intermediate holiday as a day.
Short periods counted in court days with observed holidays: skip rule · case 02
A 7-day period counts an intermediate holiday as a day.
Short periods counted in court days with observed holidays: skip rule · case 03
A 7-day period counts an intermediate holiday as a day.
Short periods counted in court days with observed holidays: skip rule · case 04
A 7-day period counts an intermediate holiday as a day.
Short periods counted in court days with observed holidays: skip rule · case 05
A 7-day period counts an intermediate holiday as a day.
Short periods counted in court days with observed holidays: final roll · case 01
A 30-day period ending on a Sunday is left due on the Sunday.
Short periods counted in court days with observed holidays: final roll · case 02
A 30-day period ending on a Sunday is left due on the Sunday.
Short periods counted in court days with observed holidays: final roll · case 03
A 30-day period ending on a Sunday is left due on the Sunday.
Short periods counted in court days with observed holidays: final roll · case 04
A 30-day period ending on a Sunday is left due on the Sunday.
Short periods counted in court days with observed holidays: final roll · case 05
A 30-day period ending on a Sunday is left due on the Sunday.
Backward-counted filing deadline before a hearing: hearing day exclusion · case 01
The filing deadline is one day later than allowed because the hearing day is counted.
Backward-counted filing deadline before a hearing: hearing day exclusion · case 02
The filing deadline is one day later than allowed because the hearing day is counted.
Backward-counted filing deadline before a hearing: hearing day exclusion · case 03
The filing deadline is one day later than allowed because the hearing day is counted.
Backward-counted filing deadline before a hearing: hearing day exclusion · case 04
The filing deadline is one day later than allowed because the hearing day is counted.
Backward-counted filing deadline before a hearing: hearing day exclusion · case 05
The filing deadline is one day later than allowed because the hearing day is counted.
Backward-counted filing deadline before a hearing: court day skip · case 01
A court-day count treats a holiday as a court day.
Backward-counted filing deadline before a hearing: court day skip · case 02
A court-day count treats a holiday as a court day.
Backward-counted filing deadline before a hearing: court day skip · case 03
A court-day count treats a holiday as a court day.
Backward-counted filing deadline before a hearing: court day skip · case 04
A court-day count treats a holiday as a court day.
Backward-counted filing deadline before a hearing: court day skip · case 05
A court-day count treats a holiday as a court day.
Backward-counted filing deadline before a hearing: roll direction · case 01
A backward deadline landing on Sunday is moved to Monday, leaving less notice than required.
Backward-counted filing deadline before a hearing: roll direction · case 02
A backward deadline landing on Sunday is moved to Monday, leaving less notice than required.
Backward-counted filing deadline before a hearing: roll direction · case 03
A backward deadline landing on Sunday is moved to Monday, leaving less notice than required.
Backward-counted filing deadline before a hearing: roll direction · case 04
A backward deadline landing on Sunday is moved to Monday, leaving less notice than required.
Backward-counted filing deadline before a hearing: roll direction · case 05
A backward deadline landing on Sunday is moved to Monday, leaving less notice than required.
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 ↗