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

Cache redirects only under the stipulated freshness and response policy: explicit temporary freshness · case 01

Cache redirects only under the stipulated freshness and response policy: the explicit temporary freshness branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28402

Cache redirects only under the stipulated freshness and response policy: explicit temporary freshness · case 02

Cache redirects only under the stipulated freshness and response policy: the explicit temporary freshness branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28403

Cache redirects only under the stipulated freshness and response policy: explicit temporary freshness · case 03

Cache redirects only under the stipulated freshness and response policy: the explicit temporary freshness branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28404

Cache redirects only under the stipulated freshness and response policy: explicit temporary freshness · case 04

Cache redirects only under the stipulated freshness and response policy: the explicit temporary freshness branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28405

Cache redirects only under the stipulated freshness and response policy: explicit temporary freshness · case 05

Cache redirects only under the stipulated freshness and response policy: the explicit temporary freshness branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28406

Cache redirects only under the stipulated freshness and response policy: no store veto · case 01

Cache redirects only under the stipulated freshness and response policy: the no store veto branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28407

Cache redirects only under the stipulated freshness and response policy: no store veto · case 02

Cache redirects only under the stipulated freshness and response policy: the no store veto branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28408

Cache redirects only under the stipulated freshness and response policy: no store veto · case 03

Cache redirects only under the stipulated freshness and response policy: the no store veto branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28409

Cache redirects only under the stipulated freshness and response policy: no store veto · case 04

Cache redirects only under the stipulated freshness and response policy: the no store veto branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28410

Cache redirects only under the stipulated freshness and response policy: no store veto · case 05

Cache redirects only under the stipulated freshness and response policy: the no store veto branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28411

Cache redirects only under the stipulated freshness and response policy: private shared veto · case 01

Cache redirects only under the stipulated freshness and response policy: the private shared veto branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28412

Cache redirects only under the stipulated freshness and response policy: private shared veto · case 02

Cache redirects only under the stipulated freshness and response policy: the private shared veto branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28413

Cache redirects only under the stipulated freshness and response policy: private shared veto · case 03

Cache redirects only under the stipulated freshness and response policy: the private shared veto branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28414

Cache redirects only under the stipulated freshness and response policy: private shared veto · case 04

Cache redirects only under the stipulated freshness and response policy: the private shared veto branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28415

Cache redirects only under the stipulated freshness and response policy: private shared veto · case 05

Cache redirects only under the stipulated freshness and response policy: the private shared veto branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28416

Cache redirects only under the stipulated freshness and response policy: expired insertion · case 01

Cache redirects only under the stipulated freshness and response policy: the expired insertion branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28417

Cache redirects only under the stipulated freshness and response policy: expired insertion · case 02

Cache redirects only under the stipulated freshness and response policy: the expired insertion branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28418

Cache redirects only under the stipulated freshness and response policy: expired insertion · case 03

Cache redirects only under the stipulated freshness and response policy: the expired insertion branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28419

Cache redirects only under the stipulated freshness and response policy: expired insertion · case 04

Cache redirects only under the stipulated freshness and response policy: the expired insertion branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28420

Cache redirects only under the stipulated freshness and response policy: expired insertion · case 05

Cache redirects only under the stipulated freshness and response policy: the expired insertion branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28421

Cache redirects only under the stipulated freshness and response policy: location required · case 01

Cache redirects only under the stipulated freshness and response policy: the location required branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28422

Cache redirects only under the stipulated freshness and response policy: location required · case 02

Cache redirects only under the stipulated freshness and response policy: the location required branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28423

Cache redirects only under the stipulated freshness and response policy: location required · case 03

Cache redirects only under the stipulated freshness and response policy: the location required branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28424

Cache redirects only under the stipulated freshness and response policy: location required · case 04

Cache redirects only under the stipulated freshness and response policy: the location required branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28425

Cache redirects only under the stipulated freshness and response policy: location required · case 05

Cache redirects only under the stipulated freshness and response policy: the location required branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28426

Cache redirects only under the stipulated freshness and response policy: transient with freshness · case 01

Cache redirects only under the stipulated freshness and response policy: the transient with freshness branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28427

Cache redirects only under the stipulated freshness and response policy: transient with freshness · case 02

Cache redirects only under the stipulated freshness and response policy: the transient with freshness branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28428

Cache redirects only under the stipulated freshness and response policy: transient with freshness · case 03

Cache redirects only under the stipulated freshness and response policy: the transient with freshness branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28429

Cache redirects only under the stipulated freshness and response policy: transient with freshness · case 04

Cache redirects only under the stipulated freshness and response policy: the transient with freshness branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28430

Cache redirects only under the stipulated freshness and response policy: transient with freshness · case 05

Cache redirects only under the stipulated freshness and response policy: the transient with freshness branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28431

Cache redirects only under the stipulated freshness and response policy: stored age metadata · case 01

Cache redirects only under the stipulated freshness and response policy: the stored age metadata branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28432

Cache redirects only under the stipulated freshness and response policy: stored age metadata · case 02

Cache redirects only under the stipulated freshness and response policy: the stored age metadata branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28433

Cache redirects only under the stipulated freshness and response policy: stored age metadata · case 03

Cache redirects only under the stipulated freshness and response policy: the stored age metadata branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28434

Cache redirects only under the stipulated freshness and response policy: stored age metadata · case 04

Cache redirects only under the stipulated freshness and response policy: the stored age metadata branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28435

Cache redirects only under the stipulated freshness and response policy: stored age metadata · case 05

Cache redirects only under the stipulated freshness and response policy: the stored age metadata branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28436

Cache redirects only under the stipulated freshness and response policy: status persisted · case 01

Cache redirects only under the stipulated freshness and response policy: the status persisted branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28437

Cache redirects only under the stipulated freshness and response policy: status persisted · case 02

Cache redirects only under the stipulated freshness and response policy: the status persisted branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28438

Cache redirects only under the stipulated freshness and response policy: status persisted · case 03

Cache redirects only under the stipulated freshness and response policy: the status persisted branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28439

Cache redirects only under the stipulated freshness and response policy: status persisted · case 04

Cache redirects only under the stipulated freshness and response policy: the status persisted branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28440

Cache redirects only under the stipulated freshness and response policy: status persisted · case 05

Cache redirects only under the stipulated freshness and response policy: the status persisted branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28441

Resolve stored redirect chains with per-entry freshness and provenance: chain order · case 01

Resolve stored redirect chains with per-entry freshness and provenance: the chain order branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28442

Resolve stored redirect chains with per-entry freshness and provenance: chain order · case 02

Resolve stored redirect chains with per-entry freshness and provenance: the chain order branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28443

Resolve stored redirect chains with per-entry freshness and provenance: chain order · case 03

Resolve stored redirect chains with per-entry freshness and provenance: the chain order branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28444

Resolve stored redirect chains with per-entry freshness and provenance: chain order · case 04

Resolve stored redirect chains with per-entry freshness and provenance: the chain order branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28445

Resolve stored redirect chains with per-entry freshness and provenance: chain order · case 05

Resolve stored redirect chains with per-entry freshness and provenance: the chain order branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28446

Resolve stored redirect chains with per-entry freshness and provenance: first stale entry · case 01

Resolve stored redirect chains with per-entry freshness and provenance: the first stale entry branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28447

Resolve stored redirect chains with per-entry freshness and provenance: first stale entry · case 02

Resolve stored redirect chains with per-entry freshness and provenance: the first stale entry branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28448

Resolve stored redirect chains with per-entry freshness and provenance: first stale entry · case 03

Resolve stored redirect chains with per-entry freshness and provenance: the first stale entry branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28449

Resolve stored redirect chains with per-entry freshness and provenance: first stale entry · case 04

Resolve stored redirect chains with per-entry freshness and provenance: the first stale entry branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28450

Resolve stored redirect chains with per-entry freshness and provenance: first stale entry · case 05

Resolve stored redirect chains with per-entry freshness and provenance: the first stale entry branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28451

Resolve stored redirect chains with per-entry freshness and provenance: all entries fresh · case 01

Resolve stored redirect chains with per-entry freshness and provenance: the all entries fresh branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28452

Resolve stored redirect chains with per-entry freshness and provenance: all entries fresh · case 02

Resolve stored redirect chains with per-entry freshness and provenance: the all entries fresh branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28453

Resolve stored redirect chains with per-entry freshness and provenance: all entries fresh · case 03

Resolve stored redirect chains with per-entry freshness and provenance: the all entries fresh branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28454

Resolve stored redirect chains with per-entry freshness and provenance: all entries fresh · case 04

Resolve stored redirect chains with per-entry freshness and provenance: the all entries fresh branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28455

Resolve stored redirect chains with per-entry freshness and provenance: all entries fresh · case 05

Resolve stored redirect chains with per-entry freshness and provenance: the all entries fresh branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28456

Resolve stored redirect chains with per-entry freshness and provenance: entry age clock rollback · case 01

Resolve stored redirect chains with per-entry freshness and provenance: the entry age clock rollback branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28457

Resolve stored redirect chains with per-entry freshness and provenance: entry age clock rollback · case 02

Resolve stored redirect chains with per-entry freshness and provenance: the entry age clock rollback branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28458

Resolve stored redirect chains with per-entry freshness and provenance: entry age clock rollback · case 03

Resolve stored redirect chains with per-entry freshness and provenance: the entry age clock rollback branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28459

Resolve stored redirect chains with per-entry freshness and provenance: entry age clock rollback · case 04

Resolve stored redirect chains with per-entry freshness and provenance: the entry age clock rollback branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28460

Resolve stored redirect chains with per-entry freshness and provenance: entry age clock rollback · case 05

Resolve stored redirect chains with per-entry freshness and provenance: the entry age clock rollback branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28461

Resolve stored redirect chains with per-entry freshness and provenance: cache provenance · case 01

Resolve stored redirect chains with per-entry freshness and provenance: the cache provenance branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28462

Resolve stored redirect chains with per-entry freshness and provenance: cache provenance · case 02

Resolve stored redirect chains with per-entry freshness and provenance: the cache provenance branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28463

Resolve stored redirect chains with per-entry freshness and provenance: cache provenance · case 03

Resolve stored redirect chains with per-entry freshness and provenance: the cache provenance branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28464

Resolve stored redirect chains with per-entry freshness and provenance: cache provenance · case 04

Resolve stored redirect chains with per-entry freshness and provenance: the cache provenance branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28465

Resolve stored redirect chains with per-entry freshness and provenance: cache provenance · case 05

Resolve stored redirect chains with per-entry freshness and provenance: the cache provenance branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28466

Resolve stored redirect chains with per-entry freshness and provenance: blocked cache hit · case 01

Resolve stored redirect chains with per-entry freshness and provenance: the blocked cache hit branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28467

Resolve stored redirect chains with per-entry freshness and provenance: blocked cache hit · case 02

Resolve stored redirect chains with per-entry freshness and provenance: the blocked cache hit branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28468

Resolve stored redirect chains with per-entry freshness and provenance: blocked cache hit · case 03

Resolve stored redirect chains with per-entry freshness and provenance: the blocked cache hit branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28469

Resolve stored redirect chains with per-entry freshness and provenance: blocked cache hit · case 04

Resolve stored redirect chains with per-entry freshness and provenance: the blocked cache hit branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28470

Resolve stored redirect chains with per-entry freshness and provenance: blocked cache hit · case 05

Resolve stored redirect chains with per-entry freshness and provenance: the blocked cache hit branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28471

Resolve stored redirect chains with per-entry freshness and provenance: lookup target · case 01

Resolve stored redirect chains with per-entry freshness and provenance: the lookup target branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28472

Resolve stored redirect chains with per-entry freshness and provenance: lookup target · case 02

Resolve stored redirect chains with per-entry freshness and provenance: the lookup target branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28473

Resolve stored redirect chains with per-entry freshness and provenance: lookup target · case 03

Resolve stored redirect chains with per-entry freshness and provenance: the lookup target branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28474

Resolve stored redirect chains with per-entry freshness and provenance: lookup target · case 04

Resolve stored redirect chains with per-entry freshness and provenance: the lookup target branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28475

Resolve stored redirect chains with per-entry freshness and provenance: lookup target · case 05

Resolve stored redirect chains with per-entry freshness and provenance: the lookup target branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28476

Resolve stored redirect chains with per-entry freshness and provenance: cached response count · case 01

Resolve stored redirect chains with per-entry freshness and provenance: the cached response count branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28477

Resolve stored redirect chains with per-entry freshness and provenance: cached response count · case 02

Resolve stored redirect chains with per-entry freshness and provenance: the cached response count branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28478

Resolve stored redirect chains with per-entry freshness and provenance: cached response count · case 03

Resolve stored redirect chains with per-entry freshness and provenance: the cached response count branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28479

Resolve stored redirect chains with per-entry freshness and provenance: cached response count · case 04

Resolve stored redirect chains with per-entry freshness and provenance: the cached response count branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28480

Resolve stored redirect chains with per-entry freshness and provenance: cached response count · case 05

Resolve stored redirect chains with per-entry freshness and provenance: the cached response count branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28481

Resolve stored redirect chains with per-entry freshness and provenance: empty chain identity · case 01

Resolve stored redirect chains with per-entry freshness and provenance: the empty chain identity branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28482

Resolve stored redirect chains with per-entry freshness and provenance: empty chain identity · case 02

Resolve stored redirect chains with per-entry freshness and provenance: the empty chain identity branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28483

Resolve stored redirect chains with per-entry freshness and provenance: empty chain identity · case 03

Resolve stored redirect chains with per-entry freshness and provenance: the empty chain identity branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28484

Resolve stored redirect chains with per-entry freshness and provenance: empty chain identity · case 04

Resolve stored redirect chains with per-entry freshness and provenance: the empty chain identity branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28485

Resolve stored redirect chains with per-entry freshness and provenance: empty chain identity · case 05

Resolve stored redirect chains with per-entry freshness and provenance: the empty chain identity branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28486

Resolve stored redirect chains with per-entry freshness and provenance: fresh prefix · case 01

Resolve stored redirect chains with per-entry freshness and provenance: the fresh prefix branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28487

Resolve stored redirect chains with per-entry freshness and provenance: fresh prefix · case 02

Resolve stored redirect chains with per-entry freshness and provenance: the fresh prefix branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28488

Resolve stored redirect chains with per-entry freshness and provenance: fresh prefix · case 03

Resolve stored redirect chains with per-entry freshness and provenance: the fresh prefix branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28489

Resolve stored redirect chains with per-entry freshness and provenance: fresh prefix · case 04

Resolve stored redirect chains with per-entry freshness and provenance: the fresh prefix branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28490

Resolve stored redirect chains with per-entry freshness and provenance: fresh prefix · case 05

Resolve stored redirect chains with per-entry freshness and provenance: the fresh prefix branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28491

Select a redirect rule by explicit priority, specificity and declaration order: path exactness · case 01

Select a redirect rule by explicit priority, specificity and declaration order: the path exactness branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28492

Select a redirect rule by explicit priority, specificity and declaration order: path exactness · case 02

Select a redirect rule by explicit priority, specificity and declaration order: the path exactness branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28493

Select a redirect rule by explicit priority, specificity and declaration order: path exactness · case 03

Select a redirect rule by explicit priority, specificity and declaration order: the path exactness branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28494

Select a redirect rule by explicit priority, specificity and declaration order: path exactness · case 04

Select a redirect rule by explicit priority, specificity and declaration order: the path exactness branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28495

Select a redirect rule by explicit priority, specificity and declaration order: path exactness · case 05

Select a redirect rule by explicit priority, specificity and declaration order: the path exactness branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28496

Select a redirect rule by explicit priority, specificity and declaration order: method filter · case 01

Select a redirect rule by explicit priority, specificity and declaration order: the method filter branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28497

Select a redirect rule by explicit priority, specificity and declaration order: method filter · case 02

Select a redirect rule by explicit priority, specificity and declaration order: the method filter branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28498

Select a redirect rule by explicit priority, specificity and declaration order: method filter · case 03

Select a redirect rule by explicit priority, specificity and declaration order: the method filter branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28499

Select a redirect rule by explicit priority, specificity and declaration order: method filter · case 04

Select a redirect rule by explicit priority, specificity and declaration order: the method filter branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28500

Select a redirect rule by explicit priority, specificity and declaration order: method filter · case 05

Select a redirect rule by explicit priority, specificity and declaration order: the method filter branch emits an incorrect decision.

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