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

Record-stream checkpoint fence controller: draining / record after cut · case 01

While draining, event record_after_cut produces draining/deliver_post_cut instead of draining/buffer_post_cut.

Protocols● Open access↗
FA-20302

Record-stream checkpoint fence controller: draining / record after cut · case 02

While draining, event record_after_cut produces draining/deliver_post_cut instead of draining/buffer_post_cut.

Protocols◈ Members↗
FA-20303

Record-stream checkpoint fence controller: draining / record after cut · case 03

While draining, event record_after_cut produces draining/deliver_post_cut instead of draining/buffer_post_cut.

Protocols◈ Members↗
FA-20304

Record-stream checkpoint fence controller: draining / record after cut · case 04

While draining, event record_after_cut produces draining/deliver_post_cut instead of draining/buffer_post_cut.

Protocols◈ Members↗
FA-20305

Record-stream checkpoint fence controller: draining / record after cut · case 05

While draining, event record_after_cut produces draining/deliver_post_cut instead of draining/buffer_post_cut.

Protocols◈ Members↗
FA-20306

Record-stream checkpoint fence controller: draining / pre cut drained · case 01

While draining, event pre_cut_drained produces streaming/deliver_all instead of fenced/ack_fence.

Protocols● Open access↗
FA-20307

Record-stream checkpoint fence controller: draining / pre cut drained · case 02

While draining, event pre_cut_drained produces streaming/deliver_all instead of fenced/ack_fence.

Protocols◈ Members↗
FA-20308

Record-stream checkpoint fence controller: draining / pre cut drained · case 03

While draining, event pre_cut_drained produces streaming/deliver_all instead of fenced/ack_fence.

Protocols◈ Members↗
FA-20309

Record-stream checkpoint fence controller: draining / pre cut drained · case 04

While draining, event pre_cut_drained produces streaming/deliver_all instead of fenced/ack_fence.

Protocols◈ Members↗
FA-20310

Record-stream checkpoint fence controller: draining / pre cut drained · case 05

While draining, event pre_cut_drained produces streaming/deliver_all instead of fenced/ack_fence.

Protocols◈ Members↗
FA-20311

Record-stream checkpoint fence controller: fenced / checkpoint request · case 01

While fenced, event checkpoint_request produces streaming/deliver_all instead of checkpointing/snapshot_cut.

Protocols● Open access↗
FA-20312

Record-stream checkpoint fence controller: fenced / checkpoint request · case 02

While fenced, event checkpoint_request produces streaming/deliver_all instead of checkpointing/snapshot_cut.

Protocols◈ Members↗
FA-20313

Record-stream checkpoint fence controller: fenced / checkpoint request · case 03

While fenced, event checkpoint_request produces streaming/deliver_all instead of checkpointing/snapshot_cut.

Protocols◈ Members↗
FA-20314

Record-stream checkpoint fence controller: fenced / checkpoint request · case 04

While fenced, event checkpoint_request produces streaming/deliver_all instead of checkpointing/snapshot_cut.

Protocols◈ Members↗
FA-20315

Record-stream checkpoint fence controller: fenced / checkpoint request · case 05

While fenced, event checkpoint_request produces streaming/deliver_all instead of checkpointing/snapshot_cut.

Protocols◈ Members↗
FA-20316

Record-stream checkpoint fence controller: checkpointing / checkpoint saved · case 01

While checkpointing, event checkpoint_saved produces streaming/resume instead of saved/report_checkpoint.

Protocols● Open access↗
FA-20317

Record-stream checkpoint fence controller: checkpointing / checkpoint saved · case 02

While checkpointing, event checkpoint_saved produces streaming/resume instead of saved/report_checkpoint.

Protocols◈ Members↗
FA-20318

Record-stream checkpoint fence controller: checkpointing / checkpoint saved · case 03

While checkpointing, event checkpoint_saved produces streaming/resume instead of saved/report_checkpoint.

Protocols◈ Members↗
FA-20319

Record-stream checkpoint fence controller: checkpointing / checkpoint saved · case 04

While checkpointing, event checkpoint_saved produces streaming/resume instead of saved/report_checkpoint.

Protocols◈ Members↗
FA-20320

Record-stream checkpoint fence controller: checkpointing / checkpoint saved · case 05

While checkpointing, event checkpoint_saved produces streaming/resume instead of saved/report_checkpoint.

Protocols◈ Members↗
FA-20321

Record-stream checkpoint fence controller: saved / resume · case 01

While saved, event resume produces saved/wait instead of streaming/release_buffer_in_order.

Protocols● Open access↗
FA-20322

Record-stream checkpoint fence controller: saved / resume · case 02

While saved, event resume produces saved/wait instead of streaming/release_buffer_in_order.

Protocols◈ Members↗
FA-20323

Record-stream checkpoint fence controller: saved / resume · case 03

While saved, event resume produces saved/wait instead of streaming/release_buffer_in_order.

Protocols◈ Members↗
FA-20324

Record-stream checkpoint fence controller: saved / resume · case 04

While saved, event resume produces saved/wait instead of streaming/release_buffer_in_order.

Protocols◈ Members↗
FA-20325

Record-stream checkpoint fence controller: saved / resume · case 05

While saved, event resume produces saved/wait instead of streaming/release_buffer_in_order.

Protocols◈ Members↗
FA-20326

Record-stream checkpoint fence controller: checkpointing / checkpoint failed · case 01

While checkpointing, event checkpoint_failed produces streaming/drop_buffer instead of fenced/report_failure_keep_buffer.

Protocols● Open access↗
FA-20327

Record-stream checkpoint fence controller: checkpointing / checkpoint failed · case 02

While checkpointing, event checkpoint_failed produces streaming/drop_buffer instead of fenced/report_failure_keep_buffer.

Protocols◈ Members↗
FA-20328

Record-stream checkpoint fence controller: checkpointing / checkpoint failed · case 03

While checkpointing, event checkpoint_failed produces streaming/drop_buffer instead of fenced/report_failure_keep_buffer.

Protocols◈ Members↗
FA-20329

Record-stream checkpoint fence controller: checkpointing / checkpoint failed · case 04

While checkpointing, event checkpoint_failed produces streaming/drop_buffer instead of fenced/report_failure_keep_buffer.

Protocols◈ Members↗
FA-20330

Record-stream checkpoint fence controller: checkpointing / checkpoint failed · case 05

While checkpointing, event checkpoint_failed produces streaming/drop_buffer instead of fenced/report_failure_keep_buffer.

Protocols◈ Members↗
FA-20331

Record-stream checkpoint fence controller: fenced / record after cut · case 01

While fenced, event record_after_cut produces streaming/deliver instead of fenced/buffer_post_cut.

Protocols● Open access↗
FA-20332

Record-stream checkpoint fence controller: fenced / record after cut · case 02

While fenced, event record_after_cut produces streaming/deliver instead of fenced/buffer_post_cut.

Protocols◈ Members↗
FA-20333

Record-stream checkpoint fence controller: fenced / record after cut · case 03

While fenced, event record_after_cut produces streaming/deliver instead of fenced/buffer_post_cut.

Protocols◈ Members↗
FA-20334

Record-stream checkpoint fence controller: fenced / record after cut · case 04

While fenced, event record_after_cut produces streaming/deliver instead of fenced/buffer_post_cut.

Protocols◈ Members↗
FA-20335

Record-stream checkpoint fence controller: fenced / record after cut · case 05

While fenced, event record_after_cut produces streaming/deliver instead of fenced/buffer_post_cut.

Protocols◈ Members↗
FA-20336

Record-stream checkpoint fence controller: streaming / unsolicited resume · case 01

While streaming, event unsolicited_resume produces streaming/replay_previous instead of streaming/reject_unfenced.

Protocols● Open access↗
FA-20337

Record-stream checkpoint fence controller: streaming / unsolicited resume · case 02

While streaming, event unsolicited_resume produces streaming/replay_previous instead of streaming/reject_unfenced.

Protocols◈ Members↗
FA-20338

Record-stream checkpoint fence controller: streaming / unsolicited resume · case 03

While streaming, event unsolicited_resume produces streaming/replay_previous instead of streaming/reject_unfenced.

Protocols◈ Members↗
FA-20339

Record-stream checkpoint fence controller: streaming / unsolicited resume · case 04

While streaming, event unsolicited_resume produces streaming/replay_previous instead of streaming/reject_unfenced.

Protocols◈ Members↗
FA-20340

Record-stream checkpoint fence controller: streaming / unsolicited resume · case 05

While streaming, event unsolicited_resume produces streaming/replay_previous instead of streaming/reject_unfenced.

Protocols◈ Members↗
FA-20341

New utterance reuses an outstanding delivery serial · case 01

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements● Open access↗
FA-20342

New utterance reuses an outstanding delivery serial · case 02

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20343

New utterance reuses an outstanding delivery serial · case 03

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20344

New utterance reuses an outstanding delivery serial · case 04

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20345

New utterance reuses an outstanding delivery serial · case 05

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20346

A replacement keeps the old utterance payload · case 01

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements● Open access↗
FA-20347

A replacement keeps the old utterance payload · case 02

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20348

A replacement keeps the old utterance payload · case 03

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20349

A replacement keeps the old utterance payload · case 04

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20350

A replacement keeps the old utterance payload · case 05

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20351

A receipt from a disconnected session is accepted · case 01

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements● Open access↗
FA-20352

A receipt from a disconnected session is accepted · case 02

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20353

A receipt from a disconnected session is accepted · case 03

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20354

A receipt from a disconnected session is accepted · case 04

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20355

A receipt from a disconnected session is accepted · case 05

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20356

Reconnect suppresses a fresh ticket already retired by the old session · case 01

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements● Open access↗
FA-20357

Reconnect suppresses a fresh ticket already retired by the old session · case 02

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20358

Reconnect suppresses a fresh ticket already retired by the old session · case 03

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20359

Reconnect suppresses a fresh ticket already retired by the old session · case 04

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20360

Reconnect suppresses a fresh ticket already retired by the old session · case 05

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20361

An obsolete receipt acknowledges replacement speech · case 01

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements● Open access↗
FA-20362

An obsolete receipt acknowledges replacement speech · case 02

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20363

An obsolete receipt acknowledges replacement speech · case 03

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20364

An obsolete receipt acknowledges replacement speech · case 04

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20365

An obsolete receipt acknowledges replacement speech · case 05

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20366

Receipt speaks the utterance identifier · case 01

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements● Open access↗
FA-20367

Receipt speaks the utterance identifier · case 02

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20368

Receipt speaks the utterance identifier · case 03

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20369

Receipt speaks the utterance identifier · case 04

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20370

Receipt speaks the utterance identifier · case 05

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20371

Acknowledged utterance stays pending · case 01

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements● Open access↗
FA-20372

Acknowledged utterance stays pending · case 02

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20373

Acknowledged utterance stays pending · case 03

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20374

Acknowledged utterance stays pending · case 04

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20375

Acknowledged utterance stays pending · case 05

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20376

Disconnected speech is retained for later receipts · case 01

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements● Open access↗
FA-20377

Disconnected speech is retained for later receipts · case 02

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20378

Disconnected speech is retained for later receipts · case 03

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20379

Disconnected speech is retained for later receipts · case 04

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20380

Disconnected speech is retained for later receipts · case 05

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20381

Reconnect keeps the old receipt namespace · case 01

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements● Open access↗
FA-20382

Reconnect keeps the old receipt namespace · case 02

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20383

Reconnect keeps the old receipt namespace · case 03

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20384

Reconnect keeps the old receipt namespace · case 04

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20385

Reconnect keeps the old receipt namespace · case 05

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20386

Reconnect fails to restart the receipt sequence · case 01

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements● Open access↗
FA-20387

Reconnect fails to restart the receipt sequence · case 02

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20388

Reconnect fails to restart the receipt sequence · case 03

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20389

Reconnect fails to restart the receipt sequence · case 04

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20390

Reconnect fails to restart the receipt sequence · case 05

The announcement trace violates the stated delivery-receipts contract.

Assistive announcements◈ Members↗
FA-20391

Replacement speech resumes at the prior cursor · case 01

The announcement trace violates the stated speech-cursor contract.

Assistive announcements● Open access↗
FA-20392

Replacement speech resumes at the prior cursor · case 02

The announcement trace violates the stated speech-cursor contract.

Assistive announcements◈ Members↗
FA-20393

Replacement speech resumes at the prior cursor · case 03

The announcement trace violates the stated speech-cursor contract.

Assistive announcements◈ Members↗
FA-20394

Replacement speech resumes at the prior cursor · case 04

The announcement trace violates the stated speech-cursor contract.

Assistive announcements◈ Members↗
FA-20395

Replacement speech resumes at the prior cursor · case 05

The announcement trace violates the stated speech-cursor contract.

Assistive announcements◈ Members↗
FA-20396

Pause request fails to suspend the announcement · case 01

The announcement trace violates the stated speech-cursor contract.

Assistive announcements● Open access↗
FA-20397

Pause request fails to suspend the announcement · case 02

The announcement trace violates the stated speech-cursor contract.

Assistive announcements◈ Members↗
FA-20398

Pause request fails to suspend the announcement · case 03

The announcement trace violates the stated speech-cursor contract.

Assistive announcements◈ Members↗
FA-20399

Pause request fails to suspend the announcement · case 04

The announcement trace violates the stated speech-cursor contract.

Assistive announcements◈ Members↗
FA-20400

Pause request fails to suspend the announcement · case 05

The announcement trace violates the stated speech-cursor contract.

Assistive announcements◈ 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 ↗