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

Monotonic floor stops advancing or survives explicit reset · case 01

The decoded time state disagrees with the explicit regression oracle for floor.

Time representation● Open access↗
FA-18602

Monotonic floor stops advancing or survives explicit reset · case 02

The decoded time state disagrees with the explicit regression oracle for floor.

Time representation◈ Members↗
FA-18603

Monotonic floor stops advancing or survives explicit reset · case 03

The decoded time state disagrees with the explicit regression oracle for floor.

Time representation◈ Members↗
FA-18604

Monotonic floor stops advancing or survives explicit reset · case 04

The decoded time state disagrees with the explicit regression oracle for floor.

Time representation◈ Members↗
FA-18605

Monotonic floor stops advancing or survives explicit reset · case 05

The decoded time state disagrees with the explicit regression oracle for floor.

Time representation◈ Members↗
FA-18606

Rollback diagnostic confuses equality or ignores expected elapsed progress · case 01

The decoded time state disagrees with the explicit regression oracle for rollback.

Time representation● Open access↗
FA-18607

Rollback diagnostic confuses equality or ignores expected elapsed progress · case 02

The decoded time state disagrees with the explicit regression oracle for rollback.

Time representation◈ Members↗
FA-18608

Rollback diagnostic confuses equality or ignores expected elapsed progress · case 03

The decoded time state disagrees with the explicit regression oracle for rollback.

Time representation◈ Members↗
FA-18609

Rollback diagnostic confuses equality or ignores expected elapsed progress · case 04

The decoded time state disagrees with the explicit regression oracle for rollback.

Time representation◈ Members↗
FA-18610

Rollback diagnostic confuses equality or ignores expected elapsed progress · case 05

The decoded time state disagrees with the explicit regression oracle for rollback.

Time representation◈ Members↗
FA-18611

Presentation continuity ignores raw mode or selects backward floor · case 01

The decoded time state disagrees with the explicit regression oracle for output.

Time representation● Open access↗
FA-18612

Presentation continuity ignores raw mode or selects backward floor · case 02

The decoded time state disagrees with the explicit regression oracle for output.

Time representation◈ Members↗
FA-18613

Presentation continuity ignores raw mode or selects backward floor · case 03

The decoded time state disagrees with the explicit regression oracle for output.

Time representation◈ Members↗
FA-18614

Presentation continuity ignores raw mode or selects backward floor · case 04

The decoded time state disagrees with the explicit regression oracle for output.

Time representation◈ Members↗
FA-18615

Presentation continuity ignores raw mode or selects backward floor · case 05

The decoded time state disagrees with the explicit regression oracle for output.

Time representation◈ Members↗
FA-18616

Presentation bias includes disabled floor or accumulates old correction twice · case 01

The decoded time state disagrees with the explicit regression oracle for bias.

Time representation● Open access↗
FA-18617

Presentation bias includes disabled floor or accumulates old correction twice · case 02

The decoded time state disagrees with the explicit regression oracle for bias.

Time representation◈ Members↗
FA-18618

Presentation bias includes disabled floor or accumulates old correction twice · case 03

The decoded time state disagrees with the explicit regression oracle for bias.

Time representation◈ Members↗
FA-18619

Presentation bias includes disabled floor or accumulates old correction twice · case 04

The decoded time state disagrees with the explicit regression oracle for bias.

Time representation◈ Members↗
FA-18620

Presentation bias includes disabled floor or accumulates old correction twice · case 05

The decoded time state disagrees with the explicit regression oracle for bias.

Time representation◈ Members↗
FA-18621

Rollback debt goes negative or reverses correction direction · case 01

The decoded time state disagrees with the explicit regression oracle for debt.

Time representation● Open access↗
FA-18622

Rollback debt goes negative or reverses correction direction · case 02

The decoded time state disagrees with the explicit regression oracle for debt.

Time representation◈ Members↗
FA-18623

Rollback debt goes negative or reverses correction direction · case 03

The decoded time state disagrees with the explicit regression oracle for debt.

Time representation◈ Members↗
FA-18624

Rollback debt goes negative or reverses correction direction · case 04

The decoded time state disagrees with the explicit regression oracle for debt.

Time representation◈ Members↗
FA-18625

Rollback debt goes negative or reverses correction direction · case 05

The decoded time state disagrees with the explicit regression oracle for debt.

Time representation◈ Members↗
FA-18626

Presentation provenance ignores actual selected source · case 01

The decoded time state disagrees with the explicit regression oracle for mode.

Time representation● Open access↗
FA-18627

Presentation provenance ignores actual selected source · case 02

The decoded time state disagrees with the explicit regression oracle for mode.

Time representation◈ Members↗
FA-18628

Presentation provenance ignores actual selected source · case 03

The decoded time state disagrees with the explicit regression oracle for mode.

Time representation◈ Members↗
FA-18629

Presentation provenance ignores actual selected source · case 04

The decoded time state disagrees with the explicit regression oracle for mode.

Time representation◈ Members↗
FA-18630

Presentation provenance ignores actual selected source · case 05

The decoded time state disagrees with the explicit regression oracle for mode.

Time representation◈ Members↗
FA-18631

Invalid or raw wall value contaminates continuity checkpoint · case 01

The decoded time state disagrees with the explicit regression oracle for checkpoint_output.

Time representation● Open access↗
FA-18632

Invalid or raw wall value contaminates continuity checkpoint · case 02

The decoded time state disagrees with the explicit regression oracle for checkpoint_output.

Time representation◈ Members↗
FA-18633

Invalid or raw wall value contaminates continuity checkpoint · case 03

The decoded time state disagrees with the explicit regression oracle for checkpoint_output.

Time representation◈ Members↗
FA-18634

Invalid or raw wall value contaminates continuity checkpoint · case 04

The decoded time state disagrees with the explicit regression oracle for checkpoint_output.

Time representation◈ Members↗
FA-18635

Invalid or raw wall value contaminates continuity checkpoint · case 05

The decoded time state disagrees with the explicit regression oracle for checkpoint_output.

Time representation◈ Members↗
FA-18636

Checkpoint consumes regressed monotonic sample or never advances sample origin · case 01

The decoded time state disagrees with the explicit regression oracle for checkpoint_mono.

Time representation● Open access↗
FA-18637

Checkpoint consumes regressed monotonic sample or never advances sample origin · case 02

The decoded time state disagrees with the explicit regression oracle for checkpoint_mono.

Time representation◈ Members↗
FA-18638

Checkpoint consumes regressed monotonic sample or never advances sample origin · case 03

The decoded time state disagrees with the explicit regression oracle for checkpoint_mono.

Time representation◈ Members↗
FA-18639

Checkpoint consumes regressed monotonic sample or never advances sample origin · case 04

The decoded time state disagrees with the explicit regression oracle for checkpoint_mono.

Time representation◈ Members↗
FA-18640

Checkpoint consumes regressed monotonic sample or never advances sample origin · case 05

The decoded time state disagrees with the explicit regression oracle for checkpoint_mono.

Time representation◈ Members↗
FA-18641

Era anchor truncates negative eras or uses maximum label as period · case 01

The decoded time state disagrees with the explicit regression oracle for base_era.

Time representation● Open access↗
FA-18642

Era anchor truncates negative eras or uses maximum label as period · case 02

The decoded time state disagrees with the explicit regression oracle for base_era.

Time representation◈ Members↗
FA-18643

Era anchor truncates negative eras or uses maximum label as period · case 03

The decoded time state disagrees with the explicit regression oracle for base_era.

Time representation◈ Members↗
FA-18644

Era anchor truncates negative eras or uses maximum label as period · case 04

The decoded time state disagrees with the explicit regression oracle for base_era.

Time representation◈ Members↗
FA-18645

Era anchor truncates negative eras or uses maximum label as period · case 05

The decoded time state disagrees with the explicit regression oracle for base_era.

Time representation◈ Members↗
FA-18646

Era resolution excludes adjacent historical candidate · case 01

The decoded time state disagrees with the explicit regression oracle for candidates.

Time representation● Open access↗
FA-18647

Era resolution excludes adjacent historical candidate · case 02

The decoded time state disagrees with the explicit regression oracle for candidates.

Time representation◈ Members↗
FA-18648

Era resolution excludes adjacent historical candidate · case 03

The decoded time state disagrees with the explicit regression oracle for candidates.

Time representation◈ Members↗
FA-18649

Era resolution excludes adjacent historical candidate · case 04

The decoded time state disagrees with the explicit regression oracle for candidates.

Time representation◈ Members↗
FA-18650

Era resolution excludes adjacent historical candidate · case 05

The decoded time state disagrees with the explicit regression oracle for candidates.

Time representation◈ Members↗
FA-18651

Era distance loses absolute value or discards era identity · case 01

The decoded time state disagrees with the explicit regression oracle for distances.

Time representation● Open access↗
FA-18652

Era distance loses absolute value or discards era identity · case 02

The decoded time state disagrees with the explicit regression oracle for distances.

Time representation◈ Members↗
FA-18653

Era distance loses absolute value or discards era identity · case 03

The decoded time state disagrees with the explicit regression oracle for distances.

Time representation◈ Members↗
FA-18654

Era distance loses absolute value or discards era identity · case 04

The decoded time state disagrees with the explicit regression oracle for distances.

Time representation◈ Members↗
FA-18655

Era distance loses absolute value or discards era identity · case 05

The decoded time state disagrees with the explicit regression oracle for distances.

Time representation◈ Members↗
FA-18656

Era selection chooses farthest or central era unconditionally · case 01

The decoded time state disagrees with the explicit regression oracle for nearest.

Time representation● Open access↗
FA-18657

Era selection chooses farthest or central era unconditionally · case 02

The decoded time state disagrees with the explicit regression oracle for nearest.

Time representation◈ Members↗
FA-18658

Era selection chooses farthest or central era unconditionally · case 03

The decoded time state disagrees with the explicit regression oracle for nearest.

Time representation◈ Members↗
FA-18659

Era selection chooses farthest or central era unconditionally · case 04

The decoded time state disagrees with the explicit regression oracle for nearest.

Time representation◈ Members↗
FA-18660

Era selection chooses farthest or central era unconditionally · case 05

The decoded time state disagrees with the explicit regression oracle for nearest.

Time representation◈ Members↗
FA-18661

Era tie is silently resolved to first or newest candidate · case 01

The decoded time state disagrees with the explicit regression oracle for winners.

Time representation● Open access↗
FA-18662

Era tie is silently resolved to first or newest candidate · case 02

The decoded time state disagrees with the explicit regression oracle for winners.

Time representation◈ Members↗
FA-18663

Era tie is silently resolved to first or newest candidate · case 03

The decoded time state disagrees with the explicit regression oracle for winners.

Time representation◈ Members↗
FA-18664

Era tie is silently resolved to first or newest candidate · case 04

The decoded time state disagrees with the explicit regression oracle for winners.

Time representation◈ Members↗
FA-18665

Era tie is silently resolved to first or newest candidate · case 05

The decoded time state disagrees with the explicit regression oracle for winners.

Time representation◈ Members↗
FA-18666

Era reference uncertainty reaches a neighboring-era decision boundary · case 01

The decoded time state disagrees with the explicit regression oracle for ambiguous.

Time representation● Open access↗
FA-18667

Era reference uncertainty reaches a neighboring-era decision boundary · case 02

The decoded time state disagrees with the explicit regression oracle for ambiguous.

Time representation◈ Members↗
FA-18668

Era reference uncertainty reaches a neighboring-era decision boundary · case 03

The decoded time state disagrees with the explicit regression oracle for ambiguous.

Time representation◈ Members↗
FA-18669

Era reference uncertainty reaches a neighboring-era decision boundary · case 04

The decoded time state disagrees with the explicit regression oracle for ambiguous.

Time representation◈ Members↗
FA-18670

Era reference uncertainty reaches a neighboring-era decision boundary · case 05

The decoded time state disagrees with the explicit regression oracle for ambiguous.

Time representation◈ Members↗
FA-18671

Era wire validation admits next week or next within-week cycle · case 01

The decoded time state disagrees with the explicit regression oracle for valid_fields.

Time representation● Open access↗
FA-18672

Era wire validation admits next week or next within-week cycle · case 02

The decoded time state disagrees with the explicit regression oracle for valid_fields.

Time representation◈ Members↗
FA-18673

Era wire validation admits next week or next within-week cycle · case 03

The decoded time state disagrees with the explicit regression oracle for valid_fields.

Time representation◈ Members↗
FA-18674

Era wire validation admits next week or next within-week cycle · case 04

The decoded time state disagrees with the explicit regression oracle for valid_fields.

Time representation◈ Members↗
FA-18675

Era wire validation admits next week or next within-week cycle · case 05

The decoded time state disagrees with the explicit regression oracle for valid_fields.

Time representation◈ Members↗
FA-18676

Era resolver ignores trust radius or excludes exact radius boundary · case 01

The decoded time state disagrees with the explicit regression oracle for trusted.

Time representation● Open access↗
FA-18677

Era resolver ignores trust radius or excludes exact radius boundary · case 02

The decoded time state disagrees with the explicit regression oracle for trusted.

Time representation◈ Members↗
FA-18678

Era resolver ignores trust radius or excludes exact radius boundary · case 03

The decoded time state disagrees with the explicit regression oracle for trusted.

Time representation◈ Members↗
FA-18679

Era resolver ignores trust radius or excludes exact radius boundary · case 04

The decoded time state disagrees with the explicit regression oracle for trusted.

Time representation◈ Members↗
FA-18680

Era resolver ignores trust radius or excludes exact radius boundary · case 05

The decoded time state disagrees with the explicit regression oracle for trusted.

Time representation◈ Members↗
FA-18681

Era admission omits ambiguity or reference trust gate · case 01

The decoded time state disagrees with the explicit regression oracle for chosen.

Time representation● Open access↗
FA-18682

Era admission omits ambiguity or reference trust gate · case 02

The decoded time state disagrees with the explicit regression oracle for chosen.

Time representation◈ Members↗
FA-18683

Era admission omits ambiguity or reference trust gate · case 03

The decoded time state disagrees with the explicit regression oracle for chosen.

Time representation◈ Members↗
FA-18684

Era admission omits ambiguity or reference trust gate · case 04

The decoded time state disagrees with the explicit regression oracle for chosen.

Time representation◈ Members↗
FA-18685

Era admission omits ambiguity or reference trust gate · case 05

The decoded time state disagrees with the explicit regression oracle for chosen.

Time representation◈ Members↗
FA-18686

Resolved era coordinate fails to scale week or drops within-week tick · case 01

The decoded time state disagrees with the explicit regression oracle for absolute_tick.

Time representation● Open access↗
FA-18687

Resolved era coordinate fails to scale week or drops within-week tick · case 02

The decoded time state disagrees with the explicit regression oracle for absolute_tick.

Time representation◈ Members↗
FA-18688

Resolved era coordinate fails to scale week or drops within-week tick · case 03

The decoded time state disagrees with the explicit regression oracle for absolute_tick.

Time representation◈ Members↗
FA-18689

Resolved era coordinate fails to scale week or drops within-week tick · case 04

The decoded time state disagrees with the explicit regression oracle for absolute_tick.

Time representation◈ Members↗
FA-18690

Resolved era coordinate fails to scale week or drops within-week tick · case 05

The decoded time state disagrees with the explicit regression oracle for absolute_tick.

Time representation◈ Members↗
FA-18691

Astronomical day boundary retains noon origin or shifts in wrong direction · case 01

The decoded time state disagrees with the explicit regression oracle for shifted.

Time representation● Open access↗
FA-18692

Astronomical day boundary retains noon origin or shifts in wrong direction · case 02

The decoded time state disagrees with the explicit regression oracle for shifted.

Time representation◈ Members↗
FA-18693

Astronomical day boundary retains noon origin or shifts in wrong direction · case 03

The decoded time state disagrees with the explicit regression oracle for shifted.

Time representation◈ Members↗
FA-18694

Astronomical day boundary retains noon origin or shifts in wrong direction · case 04

The decoded time state disagrees with the explicit regression oracle for shifted.

Time representation◈ Members↗
FA-18695

Astronomical day boundary retains noon origin or shifts in wrong direction · case 05

The decoded time state disagrees with the explicit regression oracle for shifted.

Time representation◈ Members↗
FA-18696

Noon coordinate day extraction ignores half-day shift or double-carries exact midnight · case 01

The decoded time state disagrees with the explicit regression oracle for day.

Time representation● Open access↗
FA-18697

Noon coordinate day extraction ignores half-day shift or double-carries exact midnight · case 02

The decoded time state disagrees with the explicit regression oracle for day.

Time representation◈ Members↗
FA-18698

Noon coordinate day extraction ignores half-day shift or double-carries exact midnight · case 03

The decoded time state disagrees with the explicit regression oracle for day.

Time representation◈ Members↗
FA-18699

Noon coordinate day extraction ignores half-day shift or double-carries exact midnight · case 04

The decoded time state disagrees with the explicit regression oracle for day.

Time representation◈ Members↗
FA-18700

Noon coordinate day extraction ignores half-day shift or double-carries exact midnight · case 05

The decoded time state disagrees with the explicit regression oracle for day.

Time representation◈ 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 ↗