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

Retry routing with origin affinity: Capture pin violates retry transition semantics · case 01

Capture pin violates retry transition semantics

HTTP retries● Open access↗
FA-30502

Retry routing with origin affinity: Capture pin violates retry transition semantics · case 02

Capture pin violates retry transition semantics

HTTP retries◈ Members↗
FA-30503

Retry routing with origin affinity: Capture pin violates retry transition semantics · case 03

Capture pin violates retry transition semantics

HTTP retries◈ Members↗
FA-30504

Retry routing with origin affinity: Capture pin violates retry transition semantics · case 04

Capture pin violates retry transition semantics

HTTP retries◈ Members↗
FA-30505

Retry routing with origin affinity: Capture pin violates retry transition semantics · case 05

Capture pin violates retry transition semantics

HTTP retries◈ Members↗
FA-30506

Retry routing with origin affinity: Failure tried violates retry transition semantics · case 01

Failure tried violates retry transition semantics

HTTP retries● Open access↗
FA-30507

Retry routing with origin affinity: Failure tried violates retry transition semantics · case 02

Failure tried violates retry transition semantics

HTTP retries◈ Members↗
FA-30508

Retry routing with origin affinity: Failure tried violates retry transition semantics · case 03

Failure tried violates retry transition semantics

HTTP retries◈ Members↗
FA-30509

Retry routing with origin affinity: Failure tried violates retry transition semantics · case 04

Failure tried violates retry transition semantics

HTTP retries◈ Members↗
FA-30510

Retry routing with origin affinity: Failure tried violates retry transition semantics · case 05

Failure tried violates retry transition semantics

HTTP retries◈ Members↗
FA-30511

Retry routing with origin affinity: Failure release violates retry transition semantics · case 01

Failure release violates retry transition semantics

HTTP retries● Open access↗
FA-30512

Retry routing with origin affinity: Failure release violates retry transition semantics · case 02

Failure release violates retry transition semantics

HTTP retries◈ Members↗
FA-30513

Retry routing with origin affinity: Failure release violates retry transition semantics · case 03

Failure release violates retry transition semantics

HTTP retries◈ Members↗
FA-30514

Retry routing with origin affinity: Failure release violates retry transition semantics · case 04

Failure release violates retry transition semantics

HTTP retries◈ Members↗
FA-30515

Retry routing with origin affinity: Failure release violates retry transition semantics · case 05

Failure release violates retry transition semantics

HTTP retries◈ Members↗
FA-30516

Retry routing with origin affinity: Success stop violates retry transition semantics · case 01

Success stop violates retry transition semantics

HTTP retries● Open access↗
FA-30517

Retry routing with origin affinity: Success stop violates retry transition semantics · case 02

Success stop violates retry transition semantics

HTTP retries◈ Members↗
FA-30518

Retry routing with origin affinity: Success stop violates retry transition semantics · case 03

Success stop violates retry transition semantics

HTTP retries◈ Members↗
FA-30519

Retry routing with origin affinity: Success stop violates retry transition semantics · case 04

Success stop violates retry transition semantics

HTTP retries◈ Members↗
FA-30520

Retry routing with origin affinity: Success stop violates retry transition semantics · case 05

Success stop violates retry transition semantics

HTTP retries◈ Members↗
FA-30521

Retry routing with origin affinity: Pool health reset violates retry transition semantics · case 01

Pool health reset violates retry transition semantics

HTTP retries● Open access↗
FA-30522

Retry routing with origin affinity: Pool health reset violates retry transition semantics · case 02

Pool health reset violates retry transition semantics

HTTP retries◈ Members↗
FA-30523

Retry routing with origin affinity: Pool health reset violates retry transition semantics · case 03

Pool health reset violates retry transition semantics

HTTP retries◈ Members↗
FA-30524

Retry routing with origin affinity: Pool health reset violates retry transition semantics · case 04

Pool health reset violates retry transition semantics

HTTP retries◈ Members↗
FA-30525

Retry routing with origin affinity: Pool health reset violates retry transition semantics · case 05

Pool health reset violates retry transition semantics

HTTP retries◈ Members↗
FA-30526

Bounded body spooling for replay: Threshold capture violates retry transition semantics · case 01

Threshold capture violates retry transition semantics

HTTP retries● Open access↗
FA-30527

Bounded body spooling for replay: Threshold capture violates retry transition semantics · case 02

Threshold capture violates retry transition semantics

HTTP retries◈ Members↗
FA-30528

Bounded body spooling for replay: Threshold capture violates retry transition semantics · case 03

Threshold capture violates retry transition semantics

HTTP retries◈ Members↗
FA-30529

Bounded body spooling for replay: Threshold capture violates retry transition semantics · case 04

Threshold capture violates retry transition semantics

HTTP retries◈ Members↗
FA-30530

Bounded body spooling for replay: Threshold capture violates retry transition semantics · case 05

Threshold capture violates retry transition semantics

HTTP retries◈ Members↗
FA-30531

Bounded body spooling for replay: Total limit violates retry transition semantics · case 01

Total limit violates retry transition semantics

HTTP retries● Open access↗
FA-30532

Bounded body spooling for replay: Total limit violates retry transition semantics · case 02

Total limit violates retry transition semantics

HTTP retries◈ Members↗
FA-30533

Bounded body spooling for replay: Total limit violates retry transition semantics · case 03

Total limit violates retry transition semantics

HTTP retries◈ Members↗
FA-30534

Bounded body spooling for replay: Total limit violates retry transition semantics · case 04

Total limit violates retry transition semantics

HTTP retries◈ Members↗
FA-30535

Bounded body spooling for replay: Total limit violates retry transition semantics · case 05

Total limit violates retry transition semantics

HTTP retries◈ Members↗
FA-30536

Bounded body spooling for replay: Fresh spool violates retry transition semantics · case 01

Fresh spool violates retry transition semantics

HTTP retries● Open access↗
FA-30537

Bounded body spooling for replay: Fresh spool violates retry transition semantics · case 02

Fresh spool violates retry transition semantics

HTTP retries◈ Members↗
FA-30538

Bounded body spooling for replay: Fresh spool violates retry transition semantics · case 03

Fresh spool violates retry transition semantics

HTTP retries◈ Members↗
FA-30539

Bounded body spooling for replay: Fresh spool violates retry transition semantics · case 04

Fresh spool violates retry transition semantics

HTTP retries◈ Members↗
FA-30540

Bounded body spooling for replay: Fresh spool violates retry transition semantics · case 05

Fresh spool violates retry transition semantics

HTTP retries◈ Members↗
FA-30541

Bounded body spooling for replay: Capture gate violates retry transition semantics · case 01

Capture gate violates retry transition semantics

HTTP retries● Open access↗
FA-30542

Bounded body spooling for replay: Capture gate violates retry transition semantics · case 02

Capture gate violates retry transition semantics

HTTP retries◈ Members↗
FA-30543

Bounded body spooling for replay: Capture gate violates retry transition semantics · case 03

Capture gate violates retry transition semantics

HTTP retries◈ Members↗
FA-30544

Bounded body spooling for replay: Capture gate violates retry transition semantics · case 04

Capture gate violates retry transition semantics

HTTP retries◈ Members↗
FA-30545

Bounded body spooling for replay: Capture gate violates retry transition semantics · case 05

Capture gate violates retry transition semantics

HTTP retries◈ Members↗
FA-30546

Bounded body spooling for replay: Limit boundary violates retry transition semantics · case 01

Limit boundary violates retry transition semantics

HTTP retries● Open access↗
FA-30547

Bounded body spooling for replay: Limit boundary violates retry transition semantics · case 02

Limit boundary violates retry transition semantics

HTTP retries◈ Members↗
FA-30548

Bounded body spooling for replay: Limit boundary violates retry transition semantics · case 03

Limit boundary violates retry transition semantics

HTTP retries◈ Members↗
FA-30549

Bounded body spooling for replay: Limit boundary violates retry transition semantics · case 04

Limit boundary violates retry transition semantics

HTTP retries◈ Members↗
FA-30550

Bounded body spooling for replay: Limit boundary violates retry transition semantics · case 05

Limit boundary violates retry transition semantics

HTTP retries◈ Members↗
FA-30551

Bounded body spooling for replay: Overflow terminal violates retry transition semantics · case 01

Overflow terminal violates retry transition semantics

HTTP retries● Open access↗
FA-30552

Bounded body spooling for replay: Overflow terminal violates retry transition semantics · case 02

Overflow terminal violates retry transition semantics

HTTP retries◈ Members↗
FA-30553

Bounded body spooling for replay: Overflow terminal violates retry transition semantics · case 03

Overflow terminal violates retry transition semantics

HTTP retries◈ Members↗
FA-30554

Bounded body spooling for replay: Overflow terminal violates retry transition semantics · case 04

Overflow terminal violates retry transition semantics

HTTP retries◈ Members↗
FA-30555

Bounded body spooling for replay: Overflow terminal violates retry transition semantics · case 05

Overflow terminal violates retry transition semantics

HTTP retries◈ Members↗
FA-30556

Bounded body spooling for replay: Spill boundary violates retry transition semantics · case 01

Spill boundary violates retry transition semantics

HTTP retries● Open access↗
FA-30557

Bounded body spooling for replay: Spill boundary violates retry transition semantics · case 02

Spill boundary violates retry transition semantics

HTTP retries◈ Members↗
FA-30558

Bounded body spooling for replay: Spill boundary violates retry transition semantics · case 03

Spill boundary violates retry transition semantics

HTTP retries◈ Members↗
FA-30559

Bounded body spooling for replay: Spill boundary violates retry transition semantics · case 04

Spill boundary violates retry transition semantics

HTTP retries◈ Members↗
FA-30560

Bounded body spooling for replay: Spill boundary violates retry transition semantics · case 05

Spill boundary violates retry transition semantics

HTTP retries◈ Members↗
FA-30561

Bounded body spooling for replay: Spill prefix violates retry transition semantics · case 01

Spill prefix violates retry transition semantics

HTTP retries● Open access↗
FA-30562

Bounded body spooling for replay: Spill prefix violates retry transition semantics · case 02

Spill prefix violates retry transition semantics

HTTP retries◈ Members↗
FA-30563

Bounded body spooling for replay: Spill prefix violates retry transition semantics · case 03

Spill prefix violates retry transition semantics

HTTP retries◈ Members↗
FA-30564

Bounded body spooling for replay: Spill prefix violates retry transition semantics · case 04

Spill prefix violates retry transition semantics

HTTP retries◈ Members↗
FA-30565

Bounded body spooling for replay: Spill prefix violates retry transition semantics · case 05

Spill prefix violates retry transition semantics

HTTP retries◈ Members↗
FA-30566

Bounded body spooling for replay: Spill mode violates retry transition semantics · case 01

Spill mode violates retry transition semantics

HTTP retries● Open access↗
FA-30567

Bounded body spooling for replay: Spill mode violates retry transition semantics · case 02

Spill mode violates retry transition semantics

HTTP retries◈ Members↗
FA-30568

Bounded body spooling for replay: Spill mode violates retry transition semantics · case 03

Spill mode violates retry transition semantics

HTTP retries◈ Members↗
FA-30569

Bounded body spooling for replay: Spill mode violates retry transition semantics · case 04

Spill mode violates retry transition semantics

HTTP retries◈ Members↗
FA-30570

Bounded body spooling for replay: Spill mode violates retry transition semantics · case 05

Spill mode violates retry transition semantics

HTTP retries◈ Members↗
FA-30571

Bounded body spooling for replay: Disk append violates retry transition semantics · case 01

Disk append violates retry transition semantics

HTTP retries● Open access↗
FA-30572

Bounded body spooling for replay: Disk append violates retry transition semantics · case 02

Disk append violates retry transition semantics

HTTP retries◈ Members↗
FA-30573

Bounded body spooling for replay: Disk append violates retry transition semantics · case 03

Disk append violates retry transition semantics

HTTP retries◈ Members↗
FA-30574

Bounded body spooling for replay: Disk append violates retry transition semantics · case 04

Disk append violates retry transition semantics

HTTP retries◈ Members↗
FA-30575

Bounded body spooling for replay: Disk append violates retry transition semantics · case 05

Disk append violates retry transition semantics

HTTP retries◈ Members↗
FA-30576

Bounded body spooling for replay: Memory append violates retry transition semantics · case 01

Memory append violates retry transition semantics

HTTP retries● Open access↗
FA-30577

Bounded body spooling for replay: Memory append violates retry transition semantics · case 02

Memory append violates retry transition semantics

HTTP retries◈ Members↗
FA-30578

Bounded body spooling for replay: Memory append violates retry transition semantics · case 03

Memory append violates retry transition semantics

HTTP retries◈ Members↗
FA-30579

Bounded body spooling for replay: Memory append violates retry transition semantics · case 04

Memory append violates retry transition semantics

HTTP retries◈ Members↗
FA-30580

Bounded body spooling for replay: Memory append violates retry transition semantics · case 05

Memory append violates retry transition semantics

HTTP retries◈ Members↗
FA-30581

Bounded body spooling for replay: Size accounting violates retry transition semantics · case 01

Size accounting violates retry transition semantics

HTTP retries● Open access↗
FA-30582

Bounded body spooling for replay: Size accounting violates retry transition semantics · case 02

Size accounting violates retry transition semantics

HTTP retries◈ Members↗
FA-30583

Bounded body spooling for replay: Size accounting violates retry transition semantics · case 03

Size accounting violates retry transition semantics

HTTP retries◈ Members↗
FA-30584

Bounded body spooling for replay: Size accounting violates retry transition semantics · case 04

Size accounting violates retry transition semantics

HTTP retries◈ Members↗
FA-30585

Bounded body spooling for replay: Size accounting violates retry transition semantics · case 05

Size accounting violates retry transition semantics

HTTP retries◈ Members↗
FA-30586

Bounded body spooling for replay: Seal validity violates retry transition semantics · case 01

Seal validity violates retry transition semantics

HTTP retries● Open access↗
FA-30587

Bounded body spooling for replay: Seal validity violates retry transition semantics · case 02

Seal validity violates retry transition semantics

HTTP retries◈ Members↗
FA-30588

Bounded body spooling for replay: Seal validity violates retry transition semantics · case 03

Seal validity violates retry transition semantics

HTTP retries◈ Members↗
FA-30589

Bounded body spooling for replay: Seal validity violates retry transition semantics · case 04

Seal validity violates retry transition semantics

HTTP retries◈ Members↗
FA-30590

Bounded body spooling for replay: Seal validity violates retry transition semantics · case 05

Seal validity violates retry transition semantics

HTTP retries◈ Members↗
FA-30591

Bounded body spooling for replay: Disk failure violates retry transition semantics · case 01

Disk failure violates retry transition semantics

HTTP retries● Open access↗
FA-30592

Bounded body spooling for replay: Disk failure violates retry transition semantics · case 02

Disk failure violates retry transition semantics

HTTP retries◈ Members↗
FA-30593

Bounded body spooling for replay: Disk failure violates retry transition semantics · case 03

Disk failure violates retry transition semantics

HTTP retries◈ Members↗
FA-30594

Bounded body spooling for replay: Disk failure violates retry transition semantics · case 04

Disk failure violates retry transition semantics

HTTP retries◈ Members↗
FA-30595

Bounded body spooling for replay: Disk failure violates retry transition semantics · case 05

Disk failure violates retry transition semantics

HTTP retries◈ Members↗
FA-30596

Bounded body spooling for replay: Replay store violates retry transition semantics · case 01

Replay store violates retry transition semantics

HTTP retries● Open access↗
FA-30597

Bounded body spooling for replay: Replay store violates retry transition semantics · case 02

Replay store violates retry transition semantics

HTTP retries◈ Members↗
FA-30598

Bounded body spooling for replay: Replay store violates retry transition semantics · case 03

Replay store violates retry transition semantics

HTTP retries◈ Members↗
FA-30599

Bounded body spooling for replay: Replay store violates retry transition semantics · case 04

Replay store violates retry transition semantics

HTTP retries◈ Members↗
FA-30600

Bounded body spooling for replay: Replay store violates retry transition semantics · case 05

Replay store violates retry transition semantics

HTTP retries◈ 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 ↗