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

Civil predecessor uses current offset across step or freezes historical offset · case 01

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

Time representation● Open access↗
FA-18302

Civil predecessor uses current offset across step or freezes historical offset · case 02

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

Time representation◈ Members↗
FA-18303

Civil predecessor uses current offset across step or freezes historical offset · case 03

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

Time representation◈ Members↗
FA-18304

Civil predecessor uses current offset across step or freezes historical offset · case 04

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

Time representation◈ Members↗
FA-18305

Civil predecessor uses current offset across step or freezes historical offset · case 05

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

Time representation◈ Members↗
FA-18306

Civil predecessor erases actual discontinuity · case 01

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

Time representation● Open access↗
FA-18307

Civil predecessor erases actual discontinuity · case 02

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

Time representation◈ Members↗
FA-18308

Civil predecessor erases actual discontinuity · case 03

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

Time representation◈ Members↗
FA-18309

Civil predecessor erases actual discontinuity · case 04

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

Time representation◈ Members↗
FA-18310

Civil predecessor erases actual discontinuity · case 05

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

Time representation◈ Members↗
FA-18311

Offset step magnitude uses absolute offset or opposite orientation · case 01

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

Time representation● Open access↗
FA-18312

Offset step magnitude uses absolute offset or opposite orientation · case 02

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

Time representation◈ Members↗
FA-18313

Offset step magnitude uses absolute offset or opposite orientation · case 03

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

Time representation◈ Members↗
FA-18314

Offset step magnitude uses absolute offset or opposite orientation · case 04

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

Time representation◈ Members↗
FA-18315

Offset step magnitude uses absolute offset or opposite orientation · case 05

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

Time representation◈ Members↗
FA-18316

Civil label discontinuity is clamped to forward progress or loses backward jump sign · case 01

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

Time representation● Open access↗
FA-18317

Civil label discontinuity is clamped to forward progress or loses backward jump sign · case 02

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

Time representation◈ Members↗
FA-18318

Civil label discontinuity is clamped to forward progress or loses backward jump sign · case 03

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

Time representation◈ Members↗
FA-18319

Civil label discontinuity is clamped to forward progress or loses backward jump sign · case 04

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

Time representation◈ Members↗
FA-18320

Civil label discontinuity is clamped to forward progress or loses backward jump sign · case 05

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

Time representation◈ Members↗
FA-18321

Atomic fold tag persists forever or shifts its endpoint ownership · case 01

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

Time representation● Open access↗
FA-18322

Atomic fold tag persists forever or shifts its endpoint ownership · case 02

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

Time representation◈ Members↗
FA-18323

Atomic fold tag persists forever or shifts its endpoint ownership · case 03

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

Time representation◈ Members↗
FA-18324

Atomic fold tag persists forever or shifts its endpoint ownership · case 04

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

Time representation◈ Members↗
FA-18325

Atomic fold tag persists forever or shifts its endpoint ownership · case 05

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

Time representation◈ Members↗
FA-18326

Negative-step gap marker labels every later atomic tick · case 01

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

Time representation● Open access↗
FA-18327

Negative-step gap marker labels every later atomic tick · case 02

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

Time representation◈ Members↗
FA-18328

Negative-step gap marker labels every later atomic tick · case 03

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

Time representation◈ Members↗
FA-18329

Negative-step gap marker labels every later atomic tick · case 04

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

Time representation◈ Members↗
FA-18330

Negative-step gap marker labels every later atomic tick · case 05

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

Time representation◈ Members↗
FA-18331

Offset-step direction loses negative or zero distinction · case 01

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

Time representation● Open access↗
FA-18332

Offset-step direction loses negative or zero distinction · case 02

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

Time representation◈ Members↗
FA-18333

Offset-step direction loses negative or zero distinction · case 03

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

Time representation◈ Members↗
FA-18334

Offset-step direction loses negative or zero distinction · case 04

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

Time representation◈ Members↗
FA-18335

Offset-step direction loses negative or zero distinction · case 05

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

Time representation◈ Members↗
FA-18336

Tagged civil roundtrip discards active offset table branch · case 01

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

Time representation● Open access↗
FA-18337

Tagged civil roundtrip discards active offset table branch · case 02

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

Time representation◈ Members↗
FA-18338

Tagged civil roundtrip discards active offset table branch · case 03

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

Time representation◈ Members↗
FA-18339

Tagged civil roundtrip discards active offset table branch · case 04

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

Time representation◈ Members↗
FA-18340

Tagged civil roundtrip discards active offset table branch · case 05

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

Time representation◈ Members↗
FA-18341

Epoch adapter subtracts epoch in seconds from nanosecond coordinate · case 01

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

Time representation● Open access↗
FA-18342

Epoch adapter subtracts epoch in seconds from nanosecond coordinate · case 02

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

Time representation◈ Members↗
FA-18343

Epoch adapter subtracts epoch in seconds from nanosecond coordinate · case 03

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

Time representation◈ Members↗
FA-18344

Epoch adapter subtracts epoch in seconds from nanosecond coordinate · case 04

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

Time representation◈ Members↗
FA-18345

Epoch adapter subtracts epoch in seconds from nanosecond coordinate · case 05

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

Time representation◈ Members↗
FA-18346

Epoch adapter wraps or clamps seconds before representability admission · case 01

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

Time representation● Open access↗
FA-18347

Epoch adapter wraps or clamps seconds before representability admission · case 02

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

Time representation◈ Members↗
FA-18348

Epoch adapter wraps or clamps seconds before representability admission · case 03

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

Time representation◈ Members↗
FA-18349

Epoch adapter wraps or clamps seconds before representability admission · case 04

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

Time representation◈ Members↗
FA-18350

Epoch adapter wraps or clamps seconds before representability admission · case 05

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

Time representation◈ Members↗
FA-18351

Epoch fraction uses signed magnitude or microsecond modulus · case 01

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

Time representation● Open access↗
FA-18352

Epoch fraction uses signed magnitude or microsecond modulus · case 02

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

Time representation◈ Members↗
FA-18353

Epoch fraction uses signed magnitude or microsecond modulus · case 03

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

Time representation◈ Members↗
FA-18354

Epoch fraction uses signed magnitude or microsecond modulus · case 04

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

Time representation◈ Members↗
FA-18355

Epoch fraction uses signed magnitude or microsecond modulus · case 05

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

Time representation◈ Members↗
FA-18356

Epoch range check mishandles asymmetric signed bounds · case 01

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

Time representation● Open access↗
FA-18357

Epoch range check mishandles asymmetric signed bounds · case 02

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

Time representation◈ Members↗
FA-18358

Epoch range check mishandles asymmetric signed bounds · case 03

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

Time representation◈ Members↗
FA-18359

Epoch range check mishandles asymmetric signed bounds · case 04

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

Time representation◈ Members↗
FA-18360

Epoch range check mishandles asymmetric signed bounds · case 05

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

Time representation◈ Members↗
FA-18361

Biased epoch wire word is encoded as twos complement or signed integer · case 01

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

Time representation● Open access↗
FA-18362

Biased epoch wire word is encoded as twos complement or signed integer · case 02

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

Time representation◈ Members↗
FA-18363

Biased epoch wire word is encoded as twos complement or signed integer · case 03

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

Time representation◈ Members↗
FA-18364

Biased epoch wire word is encoded as twos complement or signed integer · case 04

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

Time representation◈ Members↗
FA-18365

Biased epoch wire word is encoded as twos complement or signed integer · case 05

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

Time representation◈ Members↗
FA-18366

Saturation minimum loses epoch origin or valid most-negative second · case 01

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

Time representation● Open access↗
FA-18367

Saturation minimum loses epoch origin or valid most-negative second · case 02

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

Time representation◈ Members↗
FA-18368

Saturation minimum loses epoch origin or valid most-negative second · case 03

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

Time representation◈ Members↗
FA-18369

Saturation minimum loses epoch origin or valid most-negative second · case 04

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

Time representation◈ Members↗
FA-18370

Saturation minimum loses epoch origin or valid most-negative second · case 05

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

Time representation◈ Members↗
FA-18371

Saturation maximum omits fractional tail or admits next epoch second · case 01

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

Time representation● Open access↗
FA-18372

Saturation maximum omits fractional tail or admits next epoch second · case 02

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

Time representation◈ Members↗
FA-18373

Saturation maximum omits fractional tail or admits next epoch second · case 03

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

Time representation◈ Members↗
FA-18374

Saturation maximum omits fractional tail or admits next epoch second · case 04

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

Time representation◈ Members↗
FA-18375

Saturation maximum omits fractional tail or admits next epoch second · case 05

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

Time representation◈ Members↗
FA-18376

Timestamp saturation enforces only one representability bound · case 01

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

Time representation● Open access↗
FA-18377

Timestamp saturation enforces only one representability bound · case 02

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

Time representation◈ Members↗
FA-18378

Timestamp saturation enforces only one representability bound · case 03

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

Time representation◈ Members↗
FA-18379

Timestamp saturation enforces only one representability bound · case 04

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

Time representation◈ Members↗
FA-18380

Timestamp saturation enforces only one representability bound · case 05

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

Time representation◈ Members↗
FA-18381

Saturation loss loses direction or reverses discarded displacement · case 01

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

Time representation● Open access↗
FA-18382

Saturation loss loses direction or reverses discarded displacement · case 02

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

Time representation◈ Members↗
FA-18383

Saturation loss loses direction or reverses discarded displacement · case 03

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

Time representation◈ Members↗
FA-18384

Saturation loss loses direction or reverses discarded displacement · case 04

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

Time representation◈ Members↗
FA-18385

Saturation loss loses direction or reverses discarded displacement · case 05

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

Time representation◈ Members↗
FA-18386

Epoch reconstruction forgets bias or absolute epoch · case 01

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

Time representation● Open access↗
FA-18387

Epoch reconstruction forgets bias or absolute epoch · case 02

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

Time representation◈ Members↗
FA-18388

Epoch reconstruction forgets bias or absolute epoch · case 03

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

Time representation◈ Members↗
FA-18389

Epoch reconstruction forgets bias or absolute epoch · case 04

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

Time representation◈ Members↗
FA-18390

Epoch reconstruction forgets bias or absolute epoch · case 05

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

Time representation◈ Members↗
FA-18391

Offset parser accepts whitespace or lowercase marker despite exact wire grammar · case 01

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

Time representation● Open access↗
FA-18392

Offset parser accepts whitespace or lowercase marker despite exact wire grammar · case 02

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

Time representation◈ Members↗
FA-18393

Offset parser accepts whitespace or lowercase marker despite exact wire grammar · case 03

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

Time representation◈ Members↗
FA-18394

Offset parser accepts whitespace or lowercase marker despite exact wire grammar · case 04

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

Time representation◈ Members↗
FA-18395

Offset parser accepts whitespace or lowercase marker despite exact wire grammar · case 05

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

Time representation◈ Members↗
FA-18396

Offset marker admission accepts a presentation alias · case 01

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

Time representation● Open access↗
FA-18397

Offset marker admission accepts a presentation alias · case 02

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

Time representation◈ Members↗
FA-18398

Offset marker admission accepts a presentation alias · case 03

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

Time representation◈ Members↗
FA-18399

Offset marker admission accepts a presentation alias · case 04

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

Time representation◈ Members↗
FA-18400

Offset marker admission accepts a presentation alias · case 05

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

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 ↗