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

Series availability sums incompatible cell inventories · case 01

Series discharge is allowed to draw the sum of individual cell inventories.

Battery state accounting● Open access↗
FA-12302

Series availability sums incompatible cell inventories · case 02

Series discharge is allowed to draw the sum of individual cell inventories.

Battery state accounting◈ Members↗
FA-12303

Series availability sums incompatible cell inventories · case 03

Series discharge is allowed to draw the sum of individual cell inventories.

Battery state accounting◈ Members↗
FA-12304

Series availability sums incompatible cell inventories · case 04

Series discharge is allowed to draw the sum of individual cell inventories.

Battery state accounting◈ Members↗
FA-12305

Series availability sums incompatible cell inventories · case 05

Series discharge is allowed to draw the sum of individual cell inventories.

Battery state accounting◈ Members↗
FA-12306

Removing a module loses charge provenance · case 01

Pack removal subtracts module capacity instead of that module inventory.

Battery state accounting● Open access↗
FA-12307

Removing a module loses charge provenance · case 02

Pack removal subtracts module capacity instead of that module inventory.

Battery state accounting◈ Members↗
FA-12308

Removing a module loses charge provenance · case 03

Pack removal subtracts module capacity instead of that module inventory.

Battery state accounting◈ Members↗
FA-12309

Removing a module loses charge provenance · case 04

Pack removal subtracts module capacity instead of that module inventory.

Battery state accounting◈ Members↗
FA-12310

Removing a module loses charge provenance · case 05

Pack removal subtracts module capacity instead of that module inventory.

Battery state accounting◈ Members↗
FA-12311

Cycle wear is inferred from net inventory change · case 01

Opposite direction transfers cancel before discharge throughput is counted.

Battery state accounting● Open access↗
FA-12312

Cycle wear is inferred from net inventory change · case 02

Opposite direction transfers cancel before discharge throughput is counted.

Battery state accounting◈ Members↗
FA-12313

Cycle wear is inferred from net inventory change · case 03

Opposite direction transfers cancel before discharge throughput is counted.

Battery state accounting◈ Members↗
FA-12314

Cycle wear is inferred from net inventory change · case 04

Opposite direction transfers cancel before discharge throughput is counted.

Battery state accounting◈ Members↗
FA-12315

Cycle wear is inferred from net inventory change · case 05

Opposite direction transfers cancel before discharge throughput is counted.

Battery state accounting◈ Members↗
FA-12316

Reserve policy permanently deletes charge · case 01

The protected reserve is subtracted from stored inventory even without delivery.

Battery state accounting● Open access↗
FA-12317

Reserve policy permanently deletes charge · case 02

The protected reserve is subtracted from stored inventory even without delivery.

Battery state accounting◈ Members↗
FA-12318

Reserve policy permanently deletes charge · case 03

The protected reserve is subtracted from stored inventory even without delivery.

Battery state accounting◈ Members↗
FA-12319

Reserve policy permanently deletes charge · case 04

The protected reserve is subtracted from stored inventory even without delivery.

Battery state accounting◈ Members↗
FA-12320

Reserve policy permanently deletes charge · case 05

The protected reserve is subtracted from stored inventory even without delivery.

Battery state accounting◈ Members↗
FA-12321

Overflow charge is retained as a hidden future credit · case 01

Only the final event sum is clipped to capacity.

Battery state accounting● Open access↗
FA-12322

Overflow charge is retained as a hidden future credit · case 02

Only the final event sum is clipped to capacity.

Battery state accounting◈ Members↗
FA-12323

Overflow charge is retained as a hidden future credit · case 03

Only the final event sum is clipped to capacity.

Battery state accounting◈ Members↗
FA-12324

Overflow charge is retained as a hidden future credit · case 04

Only the final event sum is clipped to capacity.

Battery state accounting◈ Members↗
FA-12325

Overflow charge is retained as a hidden future credit · case 05

Only the final event sum is clipped to capacity.

Battery state accounting◈ Members↗
FA-12326

Idle loss is charged once per observation · case 01

Repeated observations accumulate loss regardless of elapsed model time.

Battery state accounting● Open access↗
FA-12327

Idle loss is charged once per observation · case 02

Repeated observations accumulate loss regardless of elapsed model time.

Battery state accounting◈ Members↗
FA-12328

Idle loss is charged once per observation · case 03

Repeated observations accumulate loss regardless of elapsed model time.

Battery state accounting◈ Members↗
FA-12329

Idle loss is charged once per observation · case 04

Repeated observations accumulate loss regardless of elapsed model time.

Battery state accounting◈ Members↗
FA-12330

Idle loss is charged once per observation · case 05

Repeated observations accumulate loss regardless of elapsed model time.

Battery state accounting◈ Members↗
FA-12331

Replacement inherits the previous cell wear counter · case 01

A slot stores wear independently of the identity occupying it.

Battery state accounting● Open access↗
FA-12332

Replacement inherits the previous cell wear counter · case 02

A slot stores wear independently of the identity occupying it.

Battery state accounting◈ Members↗
FA-12333

Replacement inherits the previous cell wear counter · case 03

A slot stores wear independently of the identity occupying it.

Battery state accounting◈ Members↗
FA-12334

Replacement inherits the previous cell wear counter · case 04

A slot stores wear independently of the identity occupying it.

Battery state accounting◈ Members↗
FA-12335

Replacement inherits the previous cell wear counter · case 05

A slot stores wear independently of the identity occupying it.

Battery state accounting◈ Members↗
FA-12336

Balancing credits the receiver without debiting losses · case 01

Transfer loss is ignored while moving inventory between cells.

Battery state accounting● Open access↗
FA-12337

Balancing credits the receiver without debiting losses · case 02

Transfer loss is ignored while moving inventory between cells.

Battery state accounting◈ Members↗
FA-12338

Balancing credits the receiver without debiting losses · case 03

Transfer loss is ignored while moving inventory between cells.

Battery state accounting◈ Members↗
FA-12339

Balancing credits the receiver without debiting losses · case 04

Transfer loss is ignored while moving inventory between cells.

Battery state accounting◈ Members↗
FA-12340

Balancing credits the receiver without debiting losses · case 05

Transfer loss is ignored while moving inventory between cells.

Battery state accounting◈ Members↗
FA-12341

Repeated route operations are collapsed into one completion · case 01

Repeated route operations are collapsed into one completion.

Manufacturing workflow integrity● Open access↗
FA-12342

Repeated route operations are collapsed into one completion · case 02

Repeated route operations are collapsed into one completion.

Manufacturing workflow integrity◈ Members↗
FA-12343

Repeated route operations are collapsed into one completion · case 03

Repeated route operations are collapsed into one completion.

Manufacturing workflow integrity◈ Members↗
FA-12344

Repeated route operations are collapsed into one completion · case 04

Repeated route operations are collapsed into one completion.

Manufacturing workflow integrity◈ Members↗
FA-12345

Repeated route operations are collapsed into one completion · case 05

Repeated route operations are collapsed into one completion.

Manufacturing workflow integrity◈ Members↗
FA-12346

Inspection evidence survives a rework cycle incorrectly · case 01

Inspection evidence survives a rework cycle incorrectly.

Manufacturing workflow integrity● Open access↗
FA-12347

Inspection evidence survives a rework cycle incorrectly · case 02

Inspection evidence survives a rework cycle incorrectly.

Manufacturing workflow integrity◈ Members↗
FA-12348

Inspection evidence survives a rework cycle incorrectly · case 03

Inspection evidence survives a rework cycle incorrectly.

Manufacturing workflow integrity◈ Members↗
FA-12349

Inspection evidence survives a rework cycle incorrectly · case 04

Inspection evidence survives a rework cycle incorrectly.

Manufacturing workflow integrity◈ Members↗
FA-12350

Inspection evidence survives a rework cycle incorrectly · case 05

Inspection evidence survives a rework cycle incorrectly.

Manufacturing workflow integrity◈ Members↗
FA-12351

Merged lot genealogy loses one input branch · case 01

Merged lot genealogy loses one input branch.

Manufacturing workflow integrity● Open access↗
FA-12352

Merged lot genealogy loses one input branch · case 02

Merged lot genealogy loses one input branch.

Manufacturing workflow integrity◈ Members↗
FA-12353

Merged lot genealogy loses one input branch · case 03

Merged lot genealogy loses one input branch.

Manufacturing workflow integrity◈ Members↗
FA-12354

Merged lot genealogy loses one input branch · case 04

Merged lot genealogy loses one input branch.

Manufacturing workflow integrity◈ Members↗
FA-12355

Merged lot genealogy loses one input branch · case 05

Merged lot genealogy loses one input branch.

Manufacturing workflow integrity◈ Members↗
FA-12356

A descendant lot escapes an upstream quality hold · case 01

A descendant lot escapes an upstream quality hold.

Manufacturing workflow integrity● Open access↗
FA-12357

A descendant lot escapes an upstream quality hold · case 02

A descendant lot escapes an upstream quality hold.

Manufacturing workflow integrity◈ Members↗
FA-12358

A descendant lot escapes an upstream quality hold · case 03

A descendant lot escapes an upstream quality hold.

Manufacturing workflow integrity◈ Members↗
FA-12359

A descendant lot escapes an upstream quality hold · case 04

A descendant lot escapes an upstream quality hold.

Manufacturing workflow integrity◈ Members↗
FA-12360

A descendant lot escapes an upstream quality hold · case 05

A descendant lot escapes an upstream quality hold.

Manufacturing workflow integrity◈ Members↗
FA-12361

An in-process lot silently adopts a revised route · case 01

An in-process lot silently adopts a revised route.

Manufacturing workflow integrity● Open access↗
FA-12362

An in-process lot silently adopts a revised route · case 02

An in-process lot silently adopts a revised route.

Manufacturing workflow integrity◈ Members↗
FA-12363

An in-process lot silently adopts a revised route · case 03

An in-process lot silently adopts a revised route.

Manufacturing workflow integrity◈ Members↗
FA-12364

An in-process lot silently adopts a revised route · case 04

An in-process lot silently adopts a revised route.

Manufacturing workflow integrity◈ Members↗
FA-12365

An in-process lot silently adopts a revised route · case 05

An in-process lot silently adopts a revised route.

Manufacturing workflow integrity◈ Members↗
FA-12366

A deviation approval leaks to another operation · case 01

A deviation approval leaks to another operation.

Manufacturing workflow integrity● Open access↗
FA-12367

A deviation approval leaks to another operation · case 02

A deviation approval leaks to another operation.

Manufacturing workflow integrity◈ Members↗
FA-12368

A deviation approval leaks to another operation · case 03

A deviation approval leaks to another operation.

Manufacturing workflow integrity◈ Members↗
FA-12369

A deviation approval leaks to another operation · case 04

A deviation approval leaks to another operation.

Manufacturing workflow integrity◈ Members↗
FA-12370

A deviation approval leaks to another operation · case 05

A deviation approval leaks to another operation.

Manufacturing workflow integrity◈ Members↗
FA-12371

Tool qualification for one operation authorizes another · case 01

Tool qualification for one operation authorizes another.

Manufacturing workflow integrity● Open access↗
FA-12372

Tool qualification for one operation authorizes another · case 02

Tool qualification for one operation authorizes another.

Manufacturing workflow integrity◈ Members↗
FA-12373

Tool qualification for one operation authorizes another · case 03

Tool qualification for one operation authorizes another.

Manufacturing workflow integrity◈ Members↗
FA-12374

Tool qualification for one operation authorizes another · case 04

Tool qualification for one operation authorizes another.

Manufacturing workflow integrity◈ Members↗
FA-12375

Tool qualification for one operation authorizes another · case 05

Tool qualification for one operation authorizes another.

Manufacturing workflow integrity◈ Members↗
FA-12376

One operator satisfies both release signatures · case 01

One operator satisfies both release signatures.

Manufacturing workflow integrity● Open access↗
FA-12377

One operator satisfies both release signatures · case 02

One operator satisfies both release signatures.

Manufacturing workflow integrity◈ Members↗
FA-12378

One operator satisfies both release signatures · case 03

One operator satisfies both release signatures.

Manufacturing workflow integrity◈ Members↗
FA-12379

One operator satisfies both release signatures · case 04

One operator satisfies both release signatures.

Manufacturing workflow integrity◈ Members↗
FA-12380

One operator satisfies both release signatures · case 05

One operator satisfies both release signatures.

Manufacturing workflow integrity◈ Members↗
FA-12381

Duplicate samples mask an unqualified mold cavity · case 01

Duplicate samples mask an unqualified mold cavity.

Manufacturing workflow integrity● Open access↗
FA-12382

Duplicate samples mask an unqualified mold cavity · case 02

Duplicate samples mask an unqualified mold cavity.

Manufacturing workflow integrity◈ Members↗
FA-12383

Duplicate samples mask an unqualified mold cavity · case 03

Duplicate samples mask an unqualified mold cavity.

Manufacturing workflow integrity◈ Members↗
FA-12384

Duplicate samples mask an unqualified mold cavity · case 04

Duplicate samples mask an unqualified mold cavity.

Manufacturing workflow integrity◈ Members↗
FA-12385

Duplicate samples mask an unqualified mold cavity · case 05

Duplicate samples mask an unqualified mold cavity.

Manufacturing workflow integrity◈ Members↗
FA-12386

A line clearance survives an intervening product run · case 01

A line clearance survives an intervening product run.

Manufacturing workflow integrity● Open access↗
FA-12387

A line clearance survives an intervening product run · case 02

A line clearance survives an intervening product run.

Manufacturing workflow integrity◈ Members↗
FA-12388

A line clearance survives an intervening product run · case 03

A line clearance survives an intervening product run.

Manufacturing workflow integrity◈ Members↗
FA-12389

A line clearance survives an intervening product run · case 04

A line clearance survives an intervening product run.

Manufacturing workflow integrity◈ Members↗
FA-12390

A line clearance survives an intervening product run · case 05

A line clearance survives an intervening product run.

Manufacturing workflow integrity◈ Members↗
FA-12391

Already-applied dilution steps are multiplied again · case 01

Already-applied dilution steps are multiplied again.

Laboratory measurement reporting● Open access↗
FA-12392

Already-applied dilution steps are multiplied again · case 02

Already-applied dilution steps are multiplied again.

Laboratory measurement reporting◈ Members↗
FA-12393

Already-applied dilution steps are multiplied again · case 03

Already-applied dilution steps are multiplied again.

Laboratory measurement reporting◈ Members↗
FA-12394

Already-applied dilution steps are multiplied again · case 04

Already-applied dilution steps are multiplied again.

Laboratory measurement reporting◈ Members↗
FA-12395

Already-applied dilution steps are multiplied again · case 05

Already-applied dilution steps are multiplied again.

Laboratory measurement reporting◈ Members↗
FA-12396

Aliquot blank is subtracted after dilution correction · case 01

Aliquot blank is subtracted after dilution correction.

Laboratory measurement reporting● Open access↗
FA-12397

Aliquot blank is subtracted after dilution correction · case 02

Aliquot blank is subtracted after dilution correction.

Laboratory measurement reporting◈ Members↗
FA-12398

Aliquot blank is subtracted after dilution correction · case 03

Aliquot blank is subtracted after dilution correction.

Laboratory measurement reporting◈ Members↗
FA-12399

Aliquot blank is subtracted after dilution correction · case 04

Aliquot blank is subtracted after dilution correction.

Laboratory measurement reporting◈ Members↗
FA-12400

Aliquot blank is subtracted after dilution correction · case 05

Aliquot blank is subtracted after dilution correction.

Laboratory measurement reporting◈ 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 ↗