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

Empty collection facet evidence requires a present array rather than null or missing data · case 01

Empty collection facet evidence requires a present array rather than null or missing data is violated by the widget projection.

Filter interfaces● Open access↗
FA-26302

Empty collection facet evidence requires a present array rather than null or missing data · case 02

Empty collection facet evidence requires a present array rather than null or missing data is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26303

Empty collection facet evidence requires a present array rather than null or missing data · case 03

Empty collection facet evidence requires a present array rather than null or missing data is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26304

Empty collection facet evidence requires a present array rather than null or missing data · case 04

Empty collection facet evidence requires a present array rather than null or missing data is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26305

Empty collection facet evidence requires a present array rather than null or missing data · case 05

Empty collection facet evidence requires a present array rather than null or missing data is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26306

Serialized collection operators preserve their namespaced quantifier · case 01

Serialized collection operators preserve their namespaced quantifier is violated by the widget projection.

Filter interfaces● Open access↗
FA-26307

Serialized collection operators preserve their namespaced quantifier · case 02

Serialized collection operators preserve their namespaced quantifier is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26308

Serialized collection operators preserve their namespaced quantifier · case 03

Serialized collection operators preserve their namespaced quantifier is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26309

Serialized collection operators preserve their namespaced quantifier · case 04

Serialized collection operators preserve their namespaced quantifier is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26310

Serialized collection operators preserve their namespaced quantifier · case 05

Serialized collection operators preserve their namespaced quantifier is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26311

Import staging validates field identity without dropping falsy operands · case 01

Import staging validates field identity without dropping falsy operands is violated by the widget projection.

Filter interfaces● Open access↗
FA-26312

Import staging validates field identity without dropping falsy operands · case 02

Import staging validates field identity without dropping falsy operands is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26313

Import staging validates field identity without dropping falsy operands · case 03

Import staging validates field identity without dropping falsy operands is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26314

Import staging validates field identity without dropping falsy operands · case 04

Import staging validates field identity without dropping falsy operands is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26315

Import staging validates field identity without dropping falsy operands · case 05

Import staging validates field identity without dropping falsy operands is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26316

Import review retains unresolved field operands for correction · case 01

Import review retains unresolved field operands for correction is violated by the widget projection.

Filter interfaces● Open access↗
FA-26317

Import review retains unresolved field operands for correction · case 02

Import review retains unresolved field operands for correction is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26318

Import review retains unresolved field operands for correction · case 03

Import review retains unresolved field operands for correction is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26319

Import review retains unresolved field operands for correction · case 04

Import review retains unresolved field operands for correction is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26320

Import review retains unresolved field operands for correction · case 05

Import review retains unresolved field operands for correction is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26321

Import review is required for either scope or schema-version mismatch · case 01

Import review is required for either scope or schema-version mismatch is violated by the widget projection.

Filter interfaces● Open access↗
FA-26322

Import review is required for either scope or schema-version mismatch · case 02

Import review is required for either scope or schema-version mismatch is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26323

Import review is required for either scope or schema-version mismatch · case 03

Import review is required for either scope or schema-version mismatch is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26324

Import review is required for either scope or schema-version mismatch · case 04

Import review is required for either scope or schema-version mismatch is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26325

Import review is required for either scope or schema-version mismatch · case 05

Import review is required for either scope or schema-version mismatch is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26326

Import deduplication uses full criterion identity and honors the chosen policy · case 01

Import deduplication uses full criterion identity and honors the chosen policy is violated by the widget projection.

Filter interfaces● Open access↗
FA-26327

Import deduplication uses full criterion identity and honors the chosen policy · case 02

Import deduplication uses full criterion identity and honors the chosen policy is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26328

Import deduplication uses full criterion identity and honors the chosen policy · case 03

Import deduplication uses full criterion identity and honors the chosen policy is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26329

Import deduplication uses full criterion identity and honors the chosen policy · case 04

Import deduplication uses full criterion identity and honors the chosen policy is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26330

Import deduplication uses full criterion identity and honors the chosen policy · case 05

Import deduplication uses full criterion identity and honors the chosen policy is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26331

Import publication requires review confirmation and fully resolved fields · case 01

Import publication requires review confirmation and fully resolved fields is violated by the widget projection.

Filter interfaces● Open access↗
FA-26332

Import publication requires review confirmation and fully resolved fields · case 02

Import publication requires review confirmation and fully resolved fields is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26333

Import publication requires review confirmation and fully resolved fields · case 03

Import publication requires review confirmation and fully resolved fields is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26334

Import publication requires review confirmation and fully resolved fields · case 04

Import publication requires review confirmation and fully resolved fields is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26335

Import publication requires review confirmation and fully resolved fields · case 05

Import publication requires review confirmation and fully resolved fields is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26336

The import replace option controls whether previous filter criteria survive · case 01

The import replace option controls whether previous filter criteria survive is violated by the widget projection.

Filter interfaces● Open access↗
FA-26337

The import replace option controls whether previous filter criteria survive · case 02

The import replace option controls whether previous filter criteria survive is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26338

The import replace option controls whether previous filter criteria survive · case 03

The import replace option controls whether previous filter criteria survive is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26339

The import replace option controls whether previous filter criteria survive · case 04

The import replace option controls whether previous filter criteria survive is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26340

The import replace option controls whether previous filter criteria survive · case 05

The import replace option controls whether previous filter criteria survive is violated by the widget projection.

Filter interfaces◈ Members↗
FA-26341

Failed write-independent preconditions precede range parsing · case 01

Failed write-independent preconditions precede range parsing.

HTTP ranges● Open access↗
FA-26342

Failed write-independent preconditions precede range parsing · case 02

Failed write-independent preconditions precede range parsing.

HTTP ranges◈ Members↗
FA-26343

Failed write-independent preconditions precede range parsing · case 03

Failed write-independent preconditions precede range parsing.

HTTP ranges◈ Members↗
FA-26344

Failed write-independent preconditions precede range parsing · case 04

Failed write-independent preconditions precede range parsing.

HTTP ranges◈ Members↗
FA-26345

Failed write-independent preconditions precede range parsing · case 05

Failed write-independent preconditions precede range parsing.

HTTP ranges◈ Members↗
FA-26346

A matching cache validator suppresses range unsatisfiability · case 01

A matching cache validator suppresses range unsatisfiability.

HTTP ranges● Open access↗
FA-26347

A matching cache validator suppresses range unsatisfiability · case 02

A matching cache validator suppresses range unsatisfiability.

HTTP ranges◈ Members↗
FA-26348

A matching cache validator suppresses range unsatisfiability · case 03

A matching cache validator suppresses range unsatisfiability.

HTTP ranges◈ Members↗
FA-26349

A matching cache validator suppresses range unsatisfiability · case 04

A matching cache validator suppresses range unsatisfiability.

HTTP ranges◈ Members↗
FA-26350

A matching cache validator suppresses range unsatisfiability · case 05

A matching cache validator suppresses range unsatisfiability.

HTTP ranges◈ Members↗
FA-26351

Wildcard preconditions test representation existence without requiring a stored tag · case 01

Wildcard preconditions test representation existence without requiring a stored tag.

HTTP ranges● Open access↗
FA-26352

Wildcard preconditions test representation existence without requiring a stored tag · case 02

Wildcard preconditions test representation existence without requiring a stored tag.

HTTP ranges◈ Members↗
FA-26353

Wildcard preconditions test representation existence without requiring a stored tag · case 03

Wildcard preconditions test representation existence without requiring a stored tag.

HTTP ranges◈ Members↗
FA-26354

Wildcard preconditions test representation existence without requiring a stored tag · case 04

Wildcard preconditions test representation existence without requiring a stored tag.

HTTP ranges◈ Members↗
FA-26355

Wildcard preconditions test representation existence without requiring a stored tag · case 05

Wildcard preconditions test representation existence without requiring a stored tag.

HTTP ranges◈ Members↗
FA-26356

An If-None-Match list compares complete opaque values · case 01

An If-None-Match list compares complete opaque values.

HTTP ranges● Open access↗
FA-26357

An If-None-Match list compares complete opaque values · case 02

An If-None-Match list compares complete opaque values.

HTTP ranges◈ Members↗
FA-26358

An If-None-Match list compares complete opaque values · case 03

An If-None-Match list compares complete opaque values.

HTTP ranges◈ Members↗
FA-26359

An If-None-Match list compares complete opaque values · case 04

An If-None-Match list compares complete opaque values.

HTTP ranges◈ Members↗
FA-26360

An If-None-Match list compares complete opaque values · case 05

An If-None-Match list compares complete opaque values.

HTTP ranges◈ Members↗
FA-26361

Subsecond storage timestamps do not spuriously invalidate second-granularity dates · case 01

Subsecond storage timestamps do not spuriously invalidate second-granularity dates.

HTTP ranges● Open access↗
FA-26362

Subsecond storage timestamps do not spuriously invalidate second-granularity dates · case 02

Subsecond storage timestamps do not spuriously invalidate second-granularity dates.

HTTP ranges◈ Members↗
FA-26363

Subsecond storage timestamps do not spuriously invalidate second-granularity dates · case 03

Subsecond storage timestamps do not spuriously invalidate second-granularity dates.

HTTP ranges◈ Members↗
FA-26364

Subsecond storage timestamps do not spuriously invalidate second-granularity dates · case 04

Subsecond storage timestamps do not spuriously invalidate second-granularity dates.

HTTP ranges◈ Members↗
FA-26365

Subsecond storage timestamps do not spuriously invalidate second-granularity dates · case 05

Subsecond storage timestamps do not spuriously invalidate second-granularity dates.

HTTP ranges◈ Members↗
FA-26366

A date validator with uncertain revision ordering falls back to the full representation · case 01

A date validator with uncertain revision ordering falls back to the full representation.

HTTP ranges● Open access↗
FA-26367

A date validator with uncertain revision ordering falls back to the full representation · case 02

A date validator with uncertain revision ordering falls back to the full representation.

HTTP ranges◈ Members↗
FA-26368

A date validator with uncertain revision ordering falls back to the full representation · case 03

A date validator with uncertain revision ordering falls back to the full representation.

HTTP ranges◈ Members↗
FA-26369

A date validator with uncertain revision ordering falls back to the full representation · case 04

A date validator with uncertain revision ordering falls back to the full representation.

HTTP ranges◈ Members↗
FA-26370

A date validator with uncertain revision ordering falls back to the full representation · case 05

A date validator with uncertain revision ordering falls back to the full representation.

HTTP ranges◈ Members↗
FA-26371

Full-response fallback removes partial Content-Range metadata · case 01

Full-response fallback removes partial Content-Range metadata.

HTTP ranges● Open access↗
FA-26372

Full-response fallback removes partial Content-Range metadata · case 02

Full-response fallback removes partial Content-Range metadata.

HTTP ranges◈ Members↗
FA-26373

Full-response fallback removes partial Content-Range metadata · case 03

Full-response fallback removes partial Content-Range metadata.

HTTP ranges◈ Members↗
FA-26374

Full-response fallback removes partial Content-Range metadata · case 04

Full-response fallback removes partial Content-Range metadata.

HTTP ranges◈ Members↗
FA-26375

Full-response fallback removes partial Content-Range metadata · case 05

Full-response fallback removes partial Content-Range metadata.

HTTP ranges◈ Members↗
FA-26376

An explicit nonmatching entity condition takes precedence over a matching date · case 01

An explicit nonmatching entity condition takes precedence over a matching date.

HTTP ranges● Open access↗
FA-26377

An explicit nonmatching entity condition takes precedence over a matching date · case 02

An explicit nonmatching entity condition takes precedence over a matching date.

HTTP ranges◈ Members↗
FA-26378

An explicit nonmatching entity condition takes precedence over a matching date · case 03

An explicit nonmatching entity condition takes precedence over a matching date.

HTTP ranges◈ Members↗
FA-26379

An explicit nonmatching entity condition takes precedence over a matching date · case 04

An explicit nonmatching entity condition takes precedence over a matching date.

HTTP ranges◈ Members↗
FA-26380

An explicit nonmatching entity condition takes precedence over a matching date · case 05

An explicit nonmatching entity condition takes precedence over a matching date.

HTTP ranges◈ Members↗
FA-26381

Successful entity preconditions suppress a stale secondary date condition · case 01

Successful entity preconditions suppress a stale secondary date condition.

HTTP ranges● Open access↗
FA-26382

Successful entity preconditions suppress a stale secondary date condition · case 02

Successful entity preconditions suppress a stale secondary date condition.

HTTP ranges◈ Members↗
FA-26383

Successful entity preconditions suppress a stale secondary date condition · case 03

Successful entity preconditions suppress a stale secondary date condition.

HTTP ranges◈ Members↗
FA-26384

Successful entity preconditions suppress a stale secondary date condition · case 04

Successful entity preconditions suppress a stale secondary date condition.

HTTP ranges◈ Members↗
FA-26385

Successful entity preconditions suppress a stale secondary date condition · case 05

Successful entity preconditions suppress a stale secondary date condition.

HTTP ranges◈ Members↗
FA-26386

HEAD retains full representation metadata while suppressing the body · case 01

HEAD retains full representation metadata while suppressing the body.

HTTP ranges● Open access↗
FA-26387

HEAD retains full representation metadata while suppressing the body · case 02

HEAD retains full representation metadata while suppressing the body.

HTTP ranges◈ Members↗
FA-26388

HEAD retains full representation metadata while suppressing the body · case 03

HEAD retains full representation metadata while suppressing the body.

HTTP ranges◈ Members↗
FA-26389

HEAD retains full representation metadata while suppressing the body · case 04

HEAD retains full representation metadata while suppressing the body.

HTTP ranges◈ Members↗
FA-26390

HEAD retains full representation metadata while suppressing the body · case 05

HEAD retains full representation metadata while suppressing the body.

HTTP ranges◈ Members↗
FA-26391

Byte offsets address the selected encoded representation · case 01

Byte offsets address the selected encoded representation.

HTTP ranges● Open access↗
FA-26392

Byte offsets address the selected encoded representation · case 02

Byte offsets address the selected encoded representation.

HTTP ranges◈ Members↗
FA-26393

Byte offsets address the selected encoded representation · case 03

Byte offsets address the selected encoded representation.

HTTP ranges◈ Members↗
FA-26394

Byte offsets address the selected encoded representation · case 04

Byte offsets address the selected encoded representation.

HTTP ranges◈ Members↗
FA-26395

Byte offsets address the selected encoded representation · case 05

Byte offsets address the selected encoded representation.

HTTP ranges◈ Members↗
FA-26396

Range metadata uses the negotiated variant length · case 01

Range metadata uses the negotiated variant length.

HTTP ranges● Open access↗
FA-26397

Range metadata uses the negotiated variant length · case 02

Range metadata uses the negotiated variant length.

HTTP ranges◈ Members↗
FA-26398

Range metadata uses the negotiated variant length · case 03

Range metadata uses the negotiated variant length.

HTTP ranges◈ Members↗
FA-26399

Range metadata uses the negotiated variant length · case 04

Range metadata uses the negotiated variant length.

HTTP ranges◈ Members↗
FA-26400

Range metadata uses the negotiated variant length · case 05

Range metadata uses the negotiated variant length.

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