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

Gap displacement uses offset sum or reversed offset change · case 01

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

Time representation● Open access↗
FA-17702

Gap displacement uses offset sum or reversed offset change · case 02

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

Time representation◈ Members↗
FA-17703

Gap displacement uses offset sum or reversed offset change · case 03

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

Time representation◈ Members↗
FA-17704

Gap displacement uses offset sum or reversed offset change · case 04

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

Time representation◈ Members↗
FA-17705

Gap displacement uses offset sum or reversed offset change · case 05

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

Time representation◈ Members↗
FA-17706

Forward transition assigns gap boundaries incorrectly · case 01

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

Time representation● Open access↗
FA-17707

Forward transition assigns gap boundaries incorrectly · case 02

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

Time representation◈ Members↗
FA-17708

Forward transition assigns gap boundaries incorrectly · case 03

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

Time representation◈ Members↗
FA-17709

Forward transition assigns gap boundaries incorrectly · case 04

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

Time representation◈ Members↗
FA-17710

Forward transition assigns gap boundaries incorrectly · case 05

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

Time representation◈ Members↗
FA-17711

Gap shift ignores directional and reject policy · case 01

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

Time representation● Open access↗
FA-17712

Gap shift ignores directional and reject policy · case 02

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

Time representation◈ Members↗
FA-17713

Gap shift ignores directional and reject policy · case 03

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

Time representation◈ Members↗
FA-17714

Gap shift ignores directional and reject policy · case 04

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

Time representation◈ Members↗
FA-17715

Gap shift ignores directional and reject policy · case 05

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

Time representation◈ Members↗
FA-17716

Gap resolution rejects repairable times or accepts reject policy · case 01

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

Time representation● Open access↗
FA-17717

Gap resolution rejects repairable times or accepts reject policy · case 02

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

Time representation◈ Members↗
FA-17718

Gap resolution rejects repairable times or accepts reject policy · case 03

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

Time representation◈ Members↗
FA-17719

Gap resolution rejects repairable times or accepts reject policy · case 04

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

Time representation◈ Members↗
FA-17720

Gap resolution rejects repairable times or accepts reject policy · case 05

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

Time representation◈ Members↗
FA-17721

Gap repair keeps an offset from the discarded side · case 01

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

Time representation● Open access↗
FA-17722

Gap repair keeps an offset from the discarded side · case 02

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

Time representation◈ Members↗
FA-17723

Gap repair keeps an offset from the discarded side · case 03

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

Time representation◈ Members↗
FA-17724

Gap repair keeps an offset from the discarded side · case 04

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

Time representation◈ Members↗
FA-17725

Gap repair keeps an offset from the discarded side · case 05

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

Time representation◈ Members↗
FA-17726

Gap repair exposes local coordinate as UTC · case 01

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

Time representation● Open access↗
FA-17727

Gap repair exposes local coordinate as UTC · case 02

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

Time representation◈ Members↗
FA-17728

Gap repair exposes local coordinate as UTC · case 03

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

Time representation◈ Members↗
FA-17729

Gap repair exposes local coordinate as UTC · case 04

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

Time representation◈ Members↗
FA-17730

Gap repair exposes local coordinate as UTC · case 05

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

Time representation◈ Members↗
FA-17731

Backward or zero civil adjustment gets a positive direction marker · case 01

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

Time representation● Open access↗
FA-17732

Backward or zero civil adjustment gets a positive direction marker · case 02

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

Time representation◈ Members↗
FA-17733

Backward or zero civil adjustment gets a positive direction marker · case 03

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

Time representation◈ Members↗
FA-17734

Backward or zero civil adjustment gets a positive direction marker · case 04

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

Time representation◈ Members↗
FA-17735

Backward or zero civil adjustment gets a positive direction marker · case 05

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

Time representation◈ Members↗
FA-17736

Rejected local time is reported as a successful shift · case 01

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

Time representation● Open access↗
FA-17737

Rejected local time is reported as a successful shift · case 02

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

Time representation◈ Members↗
FA-17738

Rejected local time is reported as a successful shift · case 03

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

Time representation◈ Members↗
FA-17739

Rejected local time is reported as a successful shift · case 04

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

Time representation◈ Members↗
FA-17740

Rejected local time is reported as a successful shift · case 05

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

Time representation◈ Members↗
FA-17741

Day encoding erases leap metadata or adds a leap to every day · case 01

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

Time representation● Open access↗
FA-17742

Day encoding erases leap metadata or adds a leap to every day · case 02

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

Time representation◈ Members↗
FA-17743

Day encoding erases leap metadata or adds a leap to every day · case 03

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

Time representation◈ Members↗
FA-17744

Day encoding erases leap metadata or adds a leap to every day · case 04

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

Time representation◈ Members↗
FA-17745

Day encoding erases leap metadata or adds a leap to every day · case 05

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

Time representation◈ Members↗
FA-17746

Leap label validator admits next midnight or rejects extra second · case 01

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

Time representation● Open access↗
FA-17747

Leap label validator admits next midnight or rejects extra second · case 02

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

Time representation◈ Members↗
FA-17748

Leap label validator admits next midnight or rejects extra second · case 03

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

Time representation◈ Members↗
FA-17749

Leap label validator admits next midnight or rejects extra second · case 04

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

Time representation◈ Members↗
FA-17750

Leap label validator admits next midnight or rejects extra second · case 05

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

Time representation◈ Members↗
FA-17751

Atomic label collapses leap second or applies leap at day start · case 01

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

Time representation● Open access↗
FA-17752

Atomic label collapses leap second or applies leap at day start · case 02

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

Time representation◈ Members↗
FA-17753

Atomic label collapses leap second or applies leap at day start · case 03

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

Time representation◈ Members↗
FA-17754

Atomic label collapses leap second or applies leap at day start · case 04

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

Time representation◈ Members↗
FA-17755

Atomic label collapses leap second or applies leap at day start · case 05

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

Time representation◈ Members↗
FA-17756

Leap metadata is confused with the extra-second label · case 01

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

Time representation● Open access↗
FA-17757

Leap metadata is confused with the extra-second label · case 02

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

Time representation◈ Members↗
FA-17758

Leap metadata is confused with the extra-second label · case 03

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

Time representation◈ Members↗
FA-17759

Leap metadata is confused with the extra-second label · case 04

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

Time representation◈ Members↗
FA-17760

Leap metadata is confused with the extra-second label · case 05

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

Time representation◈ Members↗
FA-17761

Leap-second display becomes hour twenty-four or midnight · case 01

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

Time representation● Open access↗
FA-17762

Leap-second display becomes hour twenty-four or midnight · case 02

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

Time representation◈ Members↗
FA-17763

Leap-second display becomes hour twenty-four or midnight · case 03

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

Time representation◈ Members↗
FA-17764

Leap-second display becomes hour twenty-four or midnight · case 04

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

Time representation◈ Members↗
FA-17765

Leap-second display becomes hour twenty-four or midnight · case 05

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

Time representation◈ Members↗
FA-17766

Leap display loses the repeated final minute · case 01

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

Time representation● Open access↗
FA-17767

Leap display loses the repeated final minute · case 02

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

Time representation◈ Members↗
FA-17768

Leap display loses the repeated final minute · case 03

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

Time representation◈ Members↗
FA-17769

Leap display loses the repeated final minute · case 04

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

Time representation◈ Members↗
FA-17770

Leap display loses the repeated final minute · case 05

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

Time representation◈ Members↗
FA-17771

Extra-second label is reduced modulo sixty · case 01

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

Time representation● Open access↗
FA-17772

Extra-second label is reduced modulo sixty · case 02

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

Time representation◈ Members↗
FA-17773

Extra-second label is reduced modulo sixty · case 03

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

Time representation◈ Members↗
FA-17774

Extra-second label is reduced modulo sixty · case 04

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

Time representation◈ Members↗
FA-17775

Extra-second label is reduced modulo sixty · case 05

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

Time representation◈ Members↗
FA-17776

End-of-day marker ignores inserted leap label · case 01

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

Time representation● Open access↗
FA-17777

End-of-day marker ignores inserted leap label · case 02

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

Time representation◈ Members↗
FA-17778

End-of-day marker ignores inserted leap label · case 03

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

Time representation◈ Members↗
FA-17779

End-of-day marker ignores inserted leap label · case 04

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

Time representation◈ Members↗
FA-17780

End-of-day marker ignores inserted leap label · case 05

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

Time representation◈ Members↗
FA-17781

Midnight countdown counts labels instead of remaining tick intervals · case 01

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

Time representation● Open access↗
FA-17782

Midnight countdown counts labels instead of remaining tick intervals · case 02

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

Time representation◈ Members↗
FA-17783

Midnight countdown counts labels instead of remaining tick intervals · case 03

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

Time representation◈ Members↗
FA-17784

Midnight countdown counts labels instead of remaining tick intervals · case 04

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

Time representation◈ Members↗
FA-17785

Midnight countdown counts labels instead of remaining tick intervals · case 05

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

Time representation◈ Members↗
FA-17786

Following midnight discards leap adjustment or absolute origin · case 01

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

Time representation● Open access↗
FA-17787

Following midnight discards leap adjustment or absolute origin · case 02

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

Time representation◈ Members↗
FA-17788

Following midnight discards leap adjustment or absolute origin · case 03

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

Time representation◈ Members↗
FA-17789

Following midnight discards leap adjustment or absolute origin · case 04

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

Time representation◈ Members↗
FA-17790

Following midnight discards leap adjustment or absolute origin · case 05

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

Time representation◈ Members↗
FA-17791

Smear span counts endpoint labels instead of elapsed ticks · case 01

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

Time representation● Open access↗
FA-17792

Smear span counts endpoint labels instead of elapsed ticks · case 02

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

Time representation◈ Members↗
FA-17793

Smear span counts endpoint labels instead of elapsed ticks · case 03

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

Time representation◈ Members↗
FA-17794

Smear span counts endpoint labels instead of elapsed ticks · case 04

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

Time representation◈ Members↗
FA-17795

Smear span counts endpoint labels instead of elapsed ticks · case 05

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

Time representation◈ Members↗
FA-17796

Smear progress extrapolates outside its window or forgets window origin · case 01

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

Time representation● Open access↗
FA-17797

Smear progress extrapolates outside its window or forgets window origin · case 02

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

Time representation◈ Members↗
FA-17798

Smear progress extrapolates outside its window or forgets window origin · case 03

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

Time representation◈ Members↗
FA-17799

Smear progress extrapolates outside its window or forgets window origin · case 04

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

Time representation◈ Members↗
FA-17800

Smear progress extrapolates outside its window or forgets window origin · case 05

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

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 ↗