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

In-flight retry policy capture: Unknown failure violates retry transition semantics · case 01

Unknown failure violates retry transition semantics

HTTP retries● Open access↗
FA-30202

In-flight retry policy capture: Unknown failure violates retry transition semantics · case 02

Unknown failure violates retry transition semantics

HTTP retries◈ Members↗
FA-30203

In-flight retry policy capture: Unknown failure violates retry transition semantics · case 03

Unknown failure violates retry transition semantics

HTTP retries◈ Members↗
FA-30204

In-flight retry policy capture: Unknown failure violates retry transition semantics · case 04

Unknown failure violates retry transition semantics

HTTP retries◈ Members↗
FA-30205

In-flight retry policy capture: Unknown failure violates retry transition semantics · case 05

Unknown failure violates retry transition semantics

HTTP retries◈ Members↗
FA-30206

In-flight retry policy capture: Policy pinning violates retry transition semantics · case 01

Policy pinning violates retry transition semantics

HTTP retries● Open access↗
FA-30207

In-flight retry policy capture: Policy pinning violates retry transition semantics · case 02

Policy pinning violates retry transition semantics

HTTP retries◈ Members↗
FA-30208

In-flight retry policy capture: Policy pinning violates retry transition semantics · case 03

Policy pinning violates retry transition semantics

HTTP retries◈ Members↗
FA-30209

In-flight retry policy capture: Policy pinning violates retry transition semantics · case 04

Policy pinning violates retry transition semantics

HTTP retries◈ Members↗
FA-30210

In-flight retry policy capture: Policy pinning violates retry transition semantics · case 05

Policy pinning violates retry transition semantics

HTTP retries◈ Members↗
FA-30211

In-flight retry policy capture: Status membership violates retry transition semantics · case 01

Status membership violates retry transition semantics

HTTP retries● Open access↗
FA-30212

In-flight retry policy capture: Status membership violates retry transition semantics · case 02

Status membership violates retry transition semantics

HTTP retries◈ Members↗
FA-30213

In-flight retry policy capture: Status membership violates retry transition semantics · case 03

Status membership violates retry transition semantics

HTTP retries◈ Members↗
FA-30214

In-flight retry policy capture: Status membership violates retry transition semantics · case 04

Status membership violates retry transition semantics

HTTP retries◈ Members↗
FA-30215

In-flight retry policy capture: Status membership violates retry transition semantics · case 05

Status membership violates retry transition semantics

HTTP retries◈ Members↗
FA-30216

In-flight retry policy capture: Cap boundary violates retry transition semantics · case 01

Cap boundary violates retry transition semantics

HTTP retries● Open access↗
FA-30217

In-flight retry policy capture: Cap boundary violates retry transition semantics · case 02

Cap boundary violates retry transition semantics

HTTP retries◈ Members↗
FA-30218

In-flight retry policy capture: Cap boundary violates retry transition semantics · case 03

Cap boundary violates retry transition semantics

HTTP retries◈ Members↗
FA-30219

In-flight retry policy capture: Cap boundary violates retry transition semantics · case 04

Cap boundary violates retry transition semantics

HTTP retries◈ Members↗
FA-30220

In-flight retry policy capture: Cap boundary violates retry transition semantics · case 05

Cap boundary violates retry transition semantics

HTTP retries◈ Members↗
FA-30221

In-flight retry policy capture: Charge request violates retry transition semantics · case 01

Charge request violates retry transition semantics

HTTP retries● Open access↗
FA-30222

In-flight retry policy capture: Charge request violates retry transition semantics · case 02

Charge request violates retry transition semantics

HTTP retries◈ Members↗
FA-30223

In-flight retry policy capture: Charge request violates retry transition semantics · case 03

Charge request violates retry transition semantics

HTTP retries◈ Members↗
FA-30224

In-flight retry policy capture: Charge request violates retry transition semantics · case 04

Charge request violates retry transition semantics

HTTP retries◈ Members↗
FA-30225

In-flight retry policy capture: Charge request violates retry transition semantics · case 05

Charge request violates retry transition semantics

HTTP retries◈ Members↗
FA-30226

Conditional mutation retry reconciliation: Precondition capture violates retry transition semantics · case 01

Precondition capture violates retry transition semantics

HTTP retries● Open access↗
FA-30227

Conditional mutation retry reconciliation: Precondition capture violates retry transition semantics · case 02

Precondition capture violates retry transition semantics

HTTP retries◈ Members↗
FA-30228

Conditional mutation retry reconciliation: Precondition capture violates retry transition semantics · case 03

Precondition capture violates retry transition semantics

HTTP retries◈ Members↗
FA-30229

Conditional mutation retry reconciliation: Precondition capture violates retry transition semantics · case 04

Precondition capture violates retry transition semantics

HTTP retries◈ Members↗
FA-30230

Conditional mutation retry reconciliation: Precondition capture violates retry transition semantics · case 05

Precondition capture violates retry transition semantics

HTTP retries◈ Members↗
FA-30231

Conditional mutation retry reconciliation: Body capture violates retry transition semantics · case 01

Body capture violates retry transition semantics

HTTP retries● Open access↗
FA-30232

Conditional mutation retry reconciliation: Body capture violates retry transition semantics · case 02

Body capture violates retry transition semantics

HTTP retries◈ Members↗
FA-30233

Conditional mutation retry reconciliation: Body capture violates retry transition semantics · case 03

Body capture violates retry transition semantics

HTTP retries◈ Members↗
FA-30234

Conditional mutation retry reconciliation: Body capture violates retry transition semantics · case 04

Body capture violates retry transition semantics

HTTP retries◈ Members↗
FA-30235

Conditional mutation retry reconciliation: Body capture violates retry transition semantics · case 05

Body capture violates retry transition semantics

HTTP retries◈ Members↗
FA-30236

Conditional mutation retry reconciliation: Begin state violates retry transition semantics · case 01

Begin state violates retry transition semantics

HTTP retries● Open access↗
FA-30237

Conditional mutation retry reconciliation: Begin state violates retry transition semantics · case 02

Begin state violates retry transition semantics

HTTP retries◈ Members↗
FA-30238

Conditional mutation retry reconciliation: Begin state violates retry transition semantics · case 03

Begin state violates retry transition semantics

HTTP retries◈ Members↗
FA-30239

Conditional mutation retry reconciliation: Begin state violates retry transition semantics · case 04

Begin state violates retry transition semantics

HTTP retries◈ Members↗
FA-30240

Conditional mutation retry reconciliation: Begin state violates retry transition semantics · case 05

Begin state violates retry transition semantics

HTTP retries◈ Members↗
FA-30241

Conditional mutation retry reconciliation: Send state violates retry transition semantics · case 01

Send state violates retry transition semantics

HTTP retries● Open access↗
FA-30242

Conditional mutation retry reconciliation: Send state violates retry transition semantics · case 02

Send state violates retry transition semantics

HTTP retries◈ Members↗
FA-30243

Conditional mutation retry reconciliation: Send state violates retry transition semantics · case 03

Send state violates retry transition semantics

HTTP retries◈ Members↗
FA-30244

Conditional mutation retry reconciliation: Send state violates retry transition semantics · case 04

Send state violates retry transition semantics

HTTP retries◈ Members↗
FA-30245

Conditional mutation retry reconciliation: Send state violates retry transition semantics · case 05

Send state violates retry transition semantics

HTTP retries◈ Members↗
FA-30246

Conditional mutation retry reconciliation: Lost after send violates retry transition semantics · case 01

Lost after send violates retry transition semantics

HTTP retries● Open access↗
FA-30247

Conditional mutation retry reconciliation: Lost after send violates retry transition semantics · case 02

Lost after send violates retry transition semantics

HTTP retries◈ Members↗
FA-30248

Conditional mutation retry reconciliation: Lost after send violates retry transition semantics · case 03

Lost after send violates retry transition semantics

HTTP retries◈ Members↗
FA-30249

Conditional mutation retry reconciliation: Lost after send violates retry transition semantics · case 04

Lost after send violates retry transition semantics

HTTP retries◈ Members↗
FA-30250

Conditional mutation retry reconciliation: Lost after send violates retry transition semantics · case 05

Lost after send violates retry transition semantics

HTTP retries◈ Members↗
FA-30251

Conditional mutation retry reconciliation: Inspection gate violates retry transition semantics · case 01

Inspection gate violates retry transition semantics

HTTP retries● Open access↗
FA-30252

Conditional mutation retry reconciliation: Inspection gate violates retry transition semantics · case 02

Inspection gate violates retry transition semantics

HTTP retries◈ Members↗
FA-30253

Conditional mutation retry reconciliation: Inspection gate violates retry transition semantics · case 03

Inspection gate violates retry transition semantics

HTTP retries◈ Members↗
FA-30254

Conditional mutation retry reconciliation: Inspection gate violates retry transition semantics · case 04

Inspection gate violates retry transition semantics

HTTP retries◈ Members↗
FA-30255

Conditional mutation retry reconciliation: Inspection gate violates retry transition semantics · case 05

Inspection gate violates retry transition semantics

HTTP retries◈ Members↗
FA-30256

Conditional mutation retry reconciliation: Successor version violates retry transition semantics · case 01

Successor version violates retry transition semantics

HTTP retries● Open access↗
FA-30257

Conditional mutation retry reconciliation: Successor version violates retry transition semantics · case 02

Successor version violates retry transition semantics

HTTP retries◈ Members↗
FA-30258

Conditional mutation retry reconciliation: Successor version violates retry transition semantics · case 03

Successor version violates retry transition semantics

HTTP retries◈ Members↗
FA-30259

Conditional mutation retry reconciliation: Successor version violates retry transition semantics · case 04

Successor version violates retry transition semantics

HTTP retries◈ Members↗
FA-30260

Conditional mutation retry reconciliation: Successor version violates retry transition semantics · case 05

Successor version violates retry transition semantics

HTTP retries◈ Members↗
FA-30261

Conditional mutation retry reconciliation: Same body violates retry transition semantics · case 01

Same body violates retry transition semantics

HTTP retries● Open access↗
FA-30262

Conditional mutation retry reconciliation: Same body violates retry transition semantics · case 02

Same body violates retry transition semantics

HTTP retries◈ Members↗
FA-30263

Conditional mutation retry reconciliation: Same body violates retry transition semantics · case 03

Same body violates retry transition semantics

HTTP retries◈ Members↗
FA-30264

Conditional mutation retry reconciliation: Same body violates retry transition semantics · case 04

Same body violates retry transition semantics

HTTP retries◈ Members↗
FA-30265

Conditional mutation retry reconciliation: Same body violates retry transition semantics · case 05

Same body violates retry transition semantics

HTTP retries◈ Members↗
FA-30266

Conditional mutation retry reconciliation: Reconciled terminal violates retry transition semantics · case 01

Reconciled terminal violates retry transition semantics

HTTP retries● Open access↗
FA-30267

Conditional mutation retry reconciliation: Reconciled terminal violates retry transition semantics · case 02

Reconciled terminal violates retry transition semantics

HTTP retries◈ Members↗
FA-30268

Conditional mutation retry reconciliation: Reconciled terminal violates retry transition semantics · case 03

Reconciled terminal violates retry transition semantics

HTTP retries◈ Members↗
FA-30269

Conditional mutation retry reconciliation: Reconciled terminal violates retry transition semantics · case 04

Reconciled terminal violates retry transition semantics

HTTP retries◈ Members↗
FA-30270

Conditional mutation retry reconciliation: Reconciled terminal violates retry transition semantics · case 05

Reconciled terminal violates retry transition semantics

HTTP retries◈ Members↗
FA-30271

Conditional mutation retry reconciliation: Unchanged version violates retry transition semantics · case 01

Unchanged version violates retry transition semantics

HTTP retries● Open access↗
FA-30272

Conditional mutation retry reconciliation: Unchanged version violates retry transition semantics · case 02

Unchanged version violates retry transition semantics

HTTP retries◈ Members↗
FA-30273

Conditional mutation retry reconciliation: Unchanged version violates retry transition semantics · case 03

Unchanged version violates retry transition semantics

HTTP retries◈ Members↗
FA-30274

Conditional mutation retry reconciliation: Unchanged version violates retry transition semantics · case 04

Unchanged version violates retry transition semantics

HTTP retries◈ Members↗
FA-30275

Conditional mutation retry reconciliation: Unchanged version violates retry transition semantics · case 05

Unchanged version violates retry transition semantics

HTTP retries◈ Members↗
FA-30276

Conditional mutation retry reconciliation: Conflict terminal violates retry transition semantics · case 01

Conflict terminal violates retry transition semantics

HTTP retries● Open access↗
FA-30277

Conditional mutation retry reconciliation: Conflict terminal violates retry transition semantics · case 02

Conflict terminal violates retry transition semantics

HTTP retries◈ Members↗
FA-30278

Conditional mutation retry reconciliation: Conflict terminal violates retry transition semantics · case 03

Conflict terminal violates retry transition semantics

HTTP retries◈ Members↗
FA-30279

Conditional mutation retry reconciliation: Conflict terminal violates retry transition semantics · case 04

Conflict terminal violates retry transition semantics

HTTP retries◈ Members↗
FA-30280

Conditional mutation retry reconciliation: Conflict terminal violates retry transition semantics · case 05

Conflict terminal violates retry transition semantics

HTTP retries◈ Members↗
FA-30281

Conditional mutation retry reconciliation: Retry gate violates retry transition semantics · case 01

Retry gate violates retry transition semantics

HTTP retries● Open access↗
FA-30282

Conditional mutation retry reconciliation: Retry gate violates retry transition semantics · case 02

Retry gate violates retry transition semantics

HTTP retries◈ Members↗
FA-30283

Conditional mutation retry reconciliation: Retry gate violates retry transition semantics · case 03

Retry gate violates retry transition semantics

HTTP retries◈ Members↗
FA-30284

Conditional mutation retry reconciliation: Retry gate violates retry transition semantics · case 04

Retry gate violates retry transition semantics

HTTP retries◈ Members↗
FA-30285

Conditional mutation retry reconciliation: Retry gate violates retry transition semantics · case 05

Retry gate violates retry transition semantics

HTTP retries◈ Members↗
FA-30286

Conditional mutation retry reconciliation: Retry condition violates retry transition semantics · case 01

Retry condition violates retry transition semantics

HTTP retries● Open access↗
FA-30287

Conditional mutation retry reconciliation: Retry condition violates retry transition semantics · case 02

Retry condition violates retry transition semantics

HTTP retries◈ Members↗
FA-30288

Conditional mutation retry reconciliation: Retry condition violates retry transition semantics · case 03

Retry condition violates retry transition semantics

HTTP retries◈ Members↗
FA-30289

Conditional mutation retry reconciliation: Retry condition violates retry transition semantics · case 04

Retry condition violates retry transition semantics

HTTP retries◈ Members↗
FA-30290

Conditional mutation retry reconciliation: Retry condition violates retry transition semantics · case 05

Retry condition violates retry transition semantics

HTTP retries◈ Members↗
FA-30291

Conditional mutation retry reconciliation: Retry consumed violates retry transition semantics · case 01

Retry consumed violates retry transition semantics

HTTP retries● Open access↗
FA-30292

Conditional mutation retry reconciliation: Retry consumed violates retry transition semantics · case 02

Retry consumed violates retry transition semantics

HTTP retries◈ Members↗
FA-30293

Conditional mutation retry reconciliation: Retry consumed violates retry transition semantics · case 03

Retry consumed violates retry transition semantics

HTTP retries◈ Members↗
FA-30294

Conditional mutation retry reconciliation: Retry consumed violates retry transition semantics · case 04

Retry consumed violates retry transition semantics

HTTP retries◈ Members↗
FA-30295

Conditional mutation retry reconciliation: Retry consumed violates retry transition semantics · case 05

Retry consumed violates retry transition semantics

HTTP retries◈ Members↗
FA-30296

Conditional mutation retry reconciliation: Ack gate violates retry transition semantics · case 01

Ack gate violates retry transition semantics

HTTP retries● Open access↗
FA-30297

Conditional mutation retry reconciliation: Ack gate violates retry transition semantics · case 02

Ack gate violates retry transition semantics

HTTP retries◈ Members↗
FA-30298

Conditional mutation retry reconciliation: Ack gate violates retry transition semantics · case 03

Ack gate violates retry transition semantics

HTTP retries◈ Members↗
FA-30299

Conditional mutation retry reconciliation: Ack gate violates retry transition semantics · case 04

Ack gate violates retry transition semantics

HTTP retries◈ Members↗
FA-30300

Conditional mutation retry reconciliation: Ack gate violates retry transition semantics · case 05

Ack gate 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 ↗