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

Bag of exactly 23 kg charged as overweight · case 01

A bag weighing exactly the free weight limit incurs the 100 surcharge.

Airline fare rule evaluation● Open access↗
FA-66802

Bag of exactly 23 kg charged as overweight · case 02

A bag weighing exactly the free weight limit incurs the 100 surcharge.

Airline fare rule evaluation◈ Members↗
FA-66803

Bag of exactly 23 kg charged as overweight · case 03

A bag weighing exactly the free weight limit incurs the 100 surcharge.

Airline fare rule evaluation◈ Members↗
FA-66804

Bag of exactly 23 kg charged as overweight · case 04

A bag weighing exactly the free weight limit incurs the 100 surcharge.

Airline fare rule evaluation◈ Members↗
FA-66805

Bag of exactly 23 kg charged as overweight · case 05

A bag weighing exactly the free weight limit incurs the 100 surcharge.

Airline fare rule evaluation◈ Members↗
FA-66806

Bags within the free allowance escape the 32 kg maximum · case 01

A 33 kg first bag on a fare with one free piece is accepted and priced.

Airline fare rule evaluation● Open access↗
FA-66807

Bags within the free allowance escape the 32 kg maximum · case 02

A 33 kg first bag on a fare with one free piece is accepted and priced.

Airline fare rule evaluation◈ Members↗
FA-66808

Bags within the free allowance escape the 32 kg maximum · case 03

A 33 kg first bag on a fare with one free piece is accepted and priced.

Airline fare rule evaluation◈ Members↗
FA-66809

Bags within the free allowance escape the 32 kg maximum · case 04

A 33 kg first bag on a fare with one free piece is accepted and priced.

Airline fare rule evaluation◈ Members↗
FA-66810

Bags within the free allowance escape the 32 kg maximum · case 05

A 33 kg first bag on a fare with one free piece is accepted and priced.

Airline fare rule evaluation◈ Members↗
FA-66811

Elite benefit replaces the fare allowance · case 01

An elite traveller on a two-bag fare only gets one free bag.

Airline fare rule evaluation● Open access↗
FA-66812

Elite benefit replaces the fare allowance · case 02

An elite traveller on a two-bag fare only gets one free bag.

Airline fare rule evaluation◈ Members↗
FA-66813

Elite benefit replaces the fare allowance · case 03

An elite traveller on a two-bag fare only gets one free bag.

Airline fare rule evaluation◈ Members↗
FA-66814

Elite benefit replaces the fare allowance · case 04

An elite traveller on a two-bag fare only gets one free bag.

Airline fare rule evaluation◈ Members↗
FA-66815

Elite benefit replaces the fare allowance · case 05

An elite traveller on a two-bag fare only gets one free bag.

Airline fare rule evaluation◈ Members↗
FA-66816

Overweight surcharge waived for free bags · case 01

A 28 kg bag within the free allowance goes through without the weight surcharge.

Airline fare rule evaluation● Open access↗
FA-66817

Overweight surcharge waived for free bags · case 02

A 28 kg bag within the free allowance goes through without the weight surcharge.

Airline fare rule evaluation◈ Members↗
FA-66818

Overweight surcharge waived for free bags · case 03

A 28 kg bag within the free allowance goes through without the weight surcharge.

Airline fare rule evaluation◈ Members↗
FA-66819

Overweight surcharge waived for free bags · case 04

A 28 kg bag within the free allowance goes through without the weight surcharge.

Airline fare rule evaluation◈ Members↗
FA-66820

Overweight surcharge waived for free bags · case 05

A 28 kg bag within the free allowance goes through without the weight surcharge.

Airline fare rule evaluation◈ Members↗
FA-66821

Commencement window applied to the return date · case 01

A trip that starts inside the travel window but returns after it fails COMMENCE.

Airline fare rule evaluation● Open access↗
FA-66822

Commencement window applied to the return date · case 02

A trip that starts inside the travel window but returns after it fails COMMENCE.

Airline fare rule evaluation◈ Members↗
FA-66823

Commencement window applied to the return date · case 03

A trip that starts inside the travel window but returns after it fails COMMENCE.

Airline fare rule evaluation◈ Members↗
FA-66824

Commencement window applied to the return date · case 04

A trip that starts inside the travel window but returns after it fails COMMENCE.

Airline fare rule evaluation◈ Members↗
FA-66825

Commencement window applied to the return date · case 05

A trip that starts inside the travel window but returns after it fails COMMENCE.

Airline fare rule evaluation◈ Members↗
FA-66826

Tickets sold on the final sale day rejected · case 01

Sales on the advertised last day of the promotion fail.

Airline fare rule evaluation● Open access↗
FA-66827

Tickets sold on the final sale day rejected · case 02

Sales on the advertised last day of the promotion fail.

Airline fare rule evaluation◈ Members↗
FA-66828

Tickets sold on the final sale day rejected · case 03

Sales on the advertised last day of the promotion fail.

Airline fare rule evaluation◈ Members↗
FA-66829

Tickets sold on the final sale day rejected · case 04

Sales on the advertised last day of the promotion fail.

Airline fare rule evaluation◈ Members↗
FA-66830

Tickets sold on the final sale day rejected · case 05

Sales on the advertised last day of the promotion fail.

Airline fare rule evaluation◈ Members↗
FA-66831

Return on the completion date flagged late · case 01

Travel completed exactly on the deadline fails COMPLETE.

Airline fare rule evaluation● Open access↗
FA-66832

Return on the completion date flagged late · case 02

Travel completed exactly on the deadline fails COMPLETE.

Airline fare rule evaluation◈ Members↗
FA-66833

Return on the completion date flagged late · case 03

Travel completed exactly on the deadline fails COMPLETE.

Airline fare rule evaluation◈ Members↗
FA-66834

Return on the completion date flagged late · case 04

Travel completed exactly on the deadline fails COMPLETE.

Airline fare rule evaluation◈ Members↗
FA-66835

Return on the completion date flagged late · case 05

Travel completed exactly on the deadline fails COMPLETE.

Airline fare rule evaluation◈ Members↗
FA-66836

Travel window checked against the sale date · case 01

Tickets sold before the travel window opens always fail COMMENCE.

Airline fare rule evaluation● Open access↗
FA-66837

Travel window checked against the sale date · case 02

Tickets sold before the travel window opens always fail COMMENCE.

Airline fare rule evaluation◈ Members↗
FA-66838

Travel window checked against the sale date · case 03

Tickets sold before the travel window opens always fail COMMENCE.

Airline fare rule evaluation◈ Members↗
FA-66839

Travel window checked against the sale date · case 04

Tickets sold before the travel window opens always fail COMMENCE.

Airline fare rule evaluation◈ Members↗
FA-66840

Travel window checked against the sale date · case 05

Tickets sold before the travel window opens always fail COMMENCE.

Airline fare rule evaluation◈ Members↗
FA-66841

Route request admission: path occupancy scope · case 01

A route is granted into a section that already holds a train.

Railway interlocking logic● Open access↗
FA-66842

Route request admission: path occupancy scope · case 02

A route is granted into a section that already holds a train.

Railway interlocking logic◈ Members↗
FA-66843

Route request admission: path occupancy scope · case 03

A route is granted into a section that already holds a train.

Railway interlocking logic◈ Members↗
FA-66844

Route request admission: path occupancy scope · case 04

A route is granted into a section that already holds a train.

Railway interlocking logic◈ Members↗
FA-66845

Route request admission: path occupancy scope · case 05

A route is granted into a section that already holds a train.

Railway interlocking logic◈ Members↗
FA-66846

Route request admission: shared point agreement · case 01

Compatible routes that use a common point in the same lie are refused.

Railway interlocking logic● Open access↗
FA-66847

Route request admission: shared point agreement · case 02

Compatible routes that use a common point in the same lie are refused.

Railway interlocking logic◈ Members↗
FA-66848

Route request admission: shared point agreement · case 03

Compatible routes that use a common point in the same lie are refused.

Railway interlocking logic◈ Members↗
FA-66849

Route request admission: shared point agreement · case 04

Compatible routes that use a common point in the same lie are refused.

Railway interlocking logic◈ Members↗
FA-66850

Route request admission: shared point agreement · case 05

Compatible routes that use a common point in the same lie are refused.

Railway interlocking logic◈ Members↗
FA-66851

Route request admission: opposing detection scope · case 01

Routes in the opposite direction anywhere on the layout block each other and opposing routes are misreported.

Railway interlocking logic● Open access↗
FA-66852

Route request admission: opposing detection scope · case 02

Routes in the opposite direction anywhere on the layout block each other and opposing routes are misreported.

Railway interlocking logic◈ Members↗
FA-66853

Route request admission: opposing detection scope · case 03

Routes in the opposite direction anywhere on the layout block each other and opposing routes are misreported.

Railway interlocking logic◈ Members↗
FA-66854

Route request admission: opposing detection scope · case 04

Routes in the opposite direction anywhere on the layout block each other and opposing routes are misreported.

Railway interlocking logic◈ Members↗
FA-66855

Route request admission: opposing detection scope · case 05

Routes in the opposite direction anywhere on the layout block each other and opposing routes are misreported.

Railway interlocking logic◈ Members↗
FA-66856

Route request admission: re-request of a set route · case 01

Re-requesting a route that is already set reports a conflict with itself.

Railway interlocking logic● Open access↗
FA-66857

Route request admission: re-request of a set route · case 02

Re-requesting a route that is already set reports a conflict with itself.

Railway interlocking logic◈ Members↗
FA-66858

Route request admission: re-request of a set route · case 03

Re-requesting a route that is already set reports a conflict with itself.

Railway interlocking logic◈ Members↗
FA-66859

Route request admission: re-request of a set route · case 04

Re-requesting a route that is already set reports a conflict with itself.

Railway interlocking logic◈ Members↗
FA-66860

Route request admission: re-request of a set route · case 05

Re-requesting a route that is already set reports a conflict with itself.

Railway interlocking logic◈ Members↗
FA-66861

Route request admission: overlap conflict geometry · case 01

A route is granted whose path runs through the overlap of a locked route (or the reverse).

Railway interlocking logic● Open access↗
FA-66862

Route request admission: overlap conflict geometry · case 02

A route is granted whose path runs through the overlap of a locked route (or the reverse).

Railway interlocking logic◈ Members↗
FA-66863

Route request admission: overlap conflict geometry · case 03

A route is granted whose path runs through the overlap of a locked route (or the reverse).

Railway interlocking logic◈ Members↗
FA-66864

Route request admission: overlap conflict geometry · case 04

A route is granted whose path runs through the overlap of a locked route (or the reverse).

Railway interlocking logic◈ Members↗
FA-66865

Route request admission: overlap conflict geometry · case 05

A route is granted whose path runs through the overlap of a locked route (or the reverse).

Railway interlocking logic◈ Members↗
FA-66866

Four-aspect signal chain evaluation: dark signal treatment · case 01

The signal in rear of a dark signal shows a proceed aspect.

Railway interlocking logic● Open access↗
FA-66867

Four-aspect signal chain evaluation: dark signal treatment · case 02

The signal in rear of a dark signal shows a proceed aspect.

Railway interlocking logic◈ Members↗
FA-66868

Four-aspect signal chain evaluation: dark signal treatment · case 03

The signal in rear of a dark signal shows a proceed aspect.

Railway interlocking logic◈ Members↗
FA-66869

Four-aspect signal chain evaluation: dark signal treatment · case 04

The signal in rear of a dark signal shows a proceed aspect.

Railway interlocking logic◈ Members↗
FA-66870

Four-aspect signal chain evaluation: dark signal treatment · case 05

The signal in rear of a dark signal shows a proceed aspect.

Railway interlocking logic◈ Members↗
FA-66871

Four-aspect signal chain evaluation: failed filament scope · case 01

Signals with a failed red filament go dark even while showing a proceed aspect.

Railway interlocking logic● Open access↗
FA-66872

Four-aspect signal chain evaluation: failed filament scope · case 02

Signals with a failed red filament go dark even while showing a proceed aspect.

Railway interlocking logic◈ Members↗
FA-66873

Four-aspect signal chain evaluation: failed filament scope · case 03

Signals with a failed red filament go dark even while showing a proceed aspect.

Railway interlocking logic◈ Members↗
FA-66874

Four-aspect signal chain evaluation: failed filament scope · case 04

Signals with a failed red filament go dark even while showing a proceed aspect.

Railway interlocking logic◈ Members↗
FA-66875

Four-aspect signal chain evaluation: failed filament scope · case 05

Signals with a failed red filament go dark even while showing a proceed aspect.

Railway interlocking logic◈ Members↗
FA-66876

Four-aspect signal chain evaluation: diverging aspect cap · case 01

A diverging junction signal displays a preliminary caution or green.

Railway interlocking logic● Open access↗
FA-66877

Four-aspect signal chain evaluation: diverging aspect cap · case 02

A diverging junction signal displays a preliminary caution or green.

Railway interlocking logic◈ Members↗
FA-66878

Four-aspect signal chain evaluation: diverging aspect cap · case 03

A diverging junction signal displays a preliminary caution or green.

Railway interlocking logic◈ Members↗
FA-66879

Four-aspect signal chain evaluation: diverging aspect cap · case 04

A diverging junction signal displays a preliminary caution or green.

Railway interlocking logic◈ Members↗
FA-66880

Four-aspect signal chain evaluation: diverging aspect cap · case 05

A diverging junction signal displays a preliminary caution or green.

Railway interlocking logic◈ Members↗
FA-66881

Four-aspect signal chain evaluation: line end boundary · case 01

The last signal before a buffer stop shows green.

Railway interlocking logic● Open access↗
FA-66882

Four-aspect signal chain evaluation: line end boundary · case 02

The last signal before a buffer stop shows green.

Railway interlocking logic◈ Members↗
FA-66883

Four-aspect signal chain evaluation: line end boundary · case 03

The last signal before a buffer stop shows green.

Railway interlocking logic◈ Members↗
FA-66884

Four-aspect signal chain evaluation: line end boundary · case 04

The last signal before a buffer stop shows green.

Railway interlocking logic◈ Members↗
FA-66885

Four-aspect signal chain evaluation: line end boundary · case 05

The last signal before a buffer stop shows green.

Railway interlocking logic◈ Members↗
FA-66886

Four-aspect signal chain evaluation: preliminary caution step · case 01

A signal two blocks behind a red shows green instead of double yellow.

Railway interlocking logic● Open access↗
FA-66887

Four-aspect signal chain evaluation: preliminary caution step · case 02

A signal two blocks behind a red shows green instead of double yellow.

Railway interlocking logic◈ Members↗
FA-66888

Four-aspect signal chain evaluation: preliminary caution step · case 03

A signal two blocks behind a red shows green instead of double yellow.

Railway interlocking logic◈ Members↗
FA-66889

Four-aspect signal chain evaluation: preliminary caution step · case 04

A signal two blocks behind a red shows green instead of double yellow.

Railway interlocking logic◈ Members↗
FA-66890

Four-aspect signal chain evaluation: preliminary caution step · case 05

A signal two blocks behind a red shows green instead of double yellow.

Railway interlocking logic◈ Members↗
FA-66891

Point machine throw control: refusal alarm · case 01

A locked point without detection raises no alarm, or a healthy locked point raises one.

Railway interlocking logic● Open access↗
FA-66892

Point machine throw control: refusal alarm · case 02

A locked point without detection raises no alarm, or a healthy locked point raises one.

Railway interlocking logic◈ Members↗
FA-66893

Point machine throw control: refusal alarm · case 03

A locked point without detection raises no alarm, or a healthy locked point raises one.

Railway interlocking logic◈ Members↗
FA-66894

Point machine throw control: refusal alarm · case 04

A locked point without detection raises no alarm, or a healthy locked point raises one.

Railway interlocking logic◈ Members↗
FA-66895

Point machine throw control: refusal alarm · case 05

A locked point without detection raises no alarm, or a healthy locked point raises one.

Railway interlocking logic◈ Members↗
FA-66896

Point machine throw control: detection deadline boundary · case 01

A point detected exactly at the deadline is declared failed.

Railway interlocking logic● Open access↗
FA-66897

Point machine throw control: detection deadline boundary · case 02

A point detected exactly at the deadline is declared failed.

Railway interlocking logic◈ Members↗
FA-66898

Point machine throw control: detection deadline boundary · case 03

A point detected exactly at the deadline is declared failed.

Railway interlocking logic◈ Members↗
FA-66899

Point machine throw control: detection deadline boundary · case 04

A point detected exactly at the deadline is declared failed.

Railway interlocking logic◈ Members↗
FA-66900

Point machine throw control: detection deadline boundary · case 05

A point detected exactly at the deadline is declared failed.

Railway interlocking logic◈ 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 ↗