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

Route advertisement lifecycle controller: candidate / loop detected · case 01

While candidate, event loop_detected produces usable/install instead of rejected/suppress.

Protocols● Open access↗
FA-19202

Route advertisement lifecycle controller: candidate / loop detected · case 02

While candidate, event loop_detected produces usable/install instead of rejected/suppress.

Protocols◈ Members↗
FA-19203

Route advertisement lifecycle controller: candidate / loop detected · case 03

While candidate, event loop_detected produces usable/install instead of rejected/suppress.

Protocols◈ Members↗
FA-19204

Route advertisement lifecycle controller: candidate / loop detected · case 04

While candidate, event loop_detected produces usable/install instead of rejected/suppress.

Protocols◈ Members↗
FA-19205

Route advertisement lifecycle controller: candidate / loop detected · case 05

While candidate, event loop_detected produces usable/install instead of rejected/suppress.

Protocols◈ Members↗
FA-19206

Route advertisement lifecycle controller: usable / withdraw · case 01

While usable, event withdraw produces usable/keep instead of withdrawn/remove_and_propagate.

Protocols● Open access↗
FA-19207

Route advertisement lifecycle controller: usable / withdraw · case 02

While usable, event withdraw produces usable/keep instead of withdrawn/remove_and_propagate.

Protocols◈ Members↗
FA-19208

Route advertisement lifecycle controller: usable / withdraw · case 03

While usable, event withdraw produces usable/keep instead of withdrawn/remove_and_propagate.

Protocols◈ Members↗
FA-19209

Route advertisement lifecycle controller: usable / withdraw · case 04

While usable, event withdraw produces usable/keep instead of withdrawn/remove_and_propagate.

Protocols◈ Members↗
FA-19210

Route advertisement lifecycle controller: usable / withdraw · case 05

While usable, event withdraw produces usable/keep instead of withdrawn/remove_and_propagate.

Protocols◈ Members↗
FA-19211

Route advertisement lifecycle controller: withdrawn / stale announce · case 01

While withdrawn, event stale_announce produces usable/install instead of withdrawn/suppress.

Protocols● Open access↗
FA-19212

Route advertisement lifecycle controller: withdrawn / stale announce · case 02

While withdrawn, event stale_announce produces usable/install instead of withdrawn/suppress.

Protocols◈ Members↗
FA-19213

Route advertisement lifecycle controller: withdrawn / stale announce · case 03

While withdrawn, event stale_announce produces usable/install instead of withdrawn/suppress.

Protocols◈ Members↗
FA-19214

Route advertisement lifecycle controller: withdrawn / stale announce · case 04

While withdrawn, event stale_announce produces usable/install instead of withdrawn/suppress.

Protocols◈ Members↗
FA-19215

Route advertisement lifecycle controller: withdrawn / stale announce · case 05

While withdrawn, event stale_announce produces usable/install instead of withdrawn/suppress.

Protocols◈ Members↗
FA-19216

Route advertisement lifecycle controller: usable / newer announce · case 01

While usable, event newer_announce produces usable/install instead of candidate/hold_validate.

Protocols● Open access↗
FA-19217

Route advertisement lifecycle controller: usable / newer announce · case 02

While usable, event newer_announce produces usable/install instead of candidate/hold_validate.

Protocols◈ Members↗
FA-19218

Route advertisement lifecycle controller: usable / newer announce · case 03

While usable, event newer_announce produces usable/install instead of candidate/hold_validate.

Protocols◈ Members↗
FA-19219

Route advertisement lifecycle controller: usable / newer announce · case 04

While usable, event newer_announce produces usable/install instead of candidate/hold_validate.

Protocols◈ Members↗
FA-19220

Route advertisement lifecycle controller: usable / newer announce · case 05

While usable, event newer_announce produces usable/install instead of candidate/hold_validate.

Protocols◈ Members↗
FA-19221

Route advertisement lifecycle controller: usable / neighbor down · case 01

While usable, event neighbor_down produces usable/keep instead of unreachable/invalidate.

Protocols● Open access↗
FA-19222

Route advertisement lifecycle controller: usable / neighbor down · case 02

While usable, event neighbor_down produces usable/keep instead of unreachable/invalidate.

Protocols◈ Members↗
FA-19223

Route advertisement lifecycle controller: usable / neighbor down · case 03

While usable, event neighbor_down produces usable/keep instead of unreachable/invalidate.

Protocols◈ Members↗
FA-19224

Route advertisement lifecycle controller: usable / neighbor down · case 04

While usable, event neighbor_down produces usable/keep instead of unreachable/invalidate.

Protocols◈ Members↗
FA-19225

Route advertisement lifecycle controller: usable / neighbor down · case 05

While usable, event neighbor_down produces usable/keep instead of unreachable/invalidate.

Protocols◈ Members↗
FA-19226

Route advertisement lifecycle controller: unreachable / neighbor up · case 01

While unreachable, event neighbor_up produces usable/install_cached instead of unknown/request_refresh.

Protocols● Open access↗
FA-19227

Route advertisement lifecycle controller: unreachable / neighbor up · case 02

While unreachable, event neighbor_up produces usable/install_cached instead of unknown/request_refresh.

Protocols◈ Members↗
FA-19228

Route advertisement lifecycle controller: unreachable / neighbor up · case 03

While unreachable, event neighbor_up produces usable/install_cached instead of unknown/request_refresh.

Protocols◈ Members↗
FA-19229

Route advertisement lifecycle controller: unreachable / neighbor up · case 04

While unreachable, event neighbor_up produces usable/install_cached instead of unknown/request_refresh.

Protocols◈ Members↗
FA-19230

Route advertisement lifecycle controller: unreachable / neighbor up · case 05

While unreachable, event neighbor_up produces usable/install_cached instead of unknown/request_refresh.

Protocols◈ Members↗
FA-19231

Route advertisement lifecycle controller: rejected / corrected announce · case 01

While rejected, event corrected_announce produces rejected/suppress instead of candidate/check_path.

Protocols● Open access↗
FA-19232

Route advertisement lifecycle controller: rejected / corrected announce · case 02

While rejected, event corrected_announce produces rejected/suppress instead of candidate/check_path.

Protocols◈ Members↗
FA-19233

Route advertisement lifecycle controller: rejected / corrected announce · case 03

While rejected, event corrected_announce produces rejected/suppress instead of candidate/check_path.

Protocols◈ Members↗
FA-19234

Route advertisement lifecycle controller: rejected / corrected announce · case 04

While rejected, event corrected_announce produces rejected/suppress instead of candidate/check_path.

Protocols◈ Members↗
FA-19235

Route advertisement lifecycle controller: rejected / corrected announce · case 05

While rejected, event corrected_announce produces rejected/suppress instead of candidate/check_path.

Protocols◈ Members↗
FA-19236

Route advertisement lifecycle controller: usable / duplicate announce · case 01

While usable, event duplicate_announce produces candidate/check_path instead of usable/refresh_liveness.

Protocols● Open access↗
FA-19237

Route advertisement lifecycle controller: usable / duplicate announce · case 02

While usable, event duplicate_announce produces candidate/check_path instead of usable/refresh_liveness.

Protocols◈ Members↗
FA-19238

Route advertisement lifecycle controller: usable / duplicate announce · case 03

While usable, event duplicate_announce produces candidate/check_path instead of usable/refresh_liveness.

Protocols◈ Members↗
FA-19239

Route advertisement lifecycle controller: usable / duplicate announce · case 04

While usable, event duplicate_announce produces candidate/check_path instead of usable/refresh_liveness.

Protocols◈ Members↗
FA-19240

Route advertisement lifecycle controller: usable / duplicate announce · case 05

While usable, event duplicate_announce produces candidate/check_path instead of usable/refresh_liveness.

Protocols◈ Members↗
FA-19241

Application schema-version exchange controller: unset / describe · case 01

While unset, event describe produces ready/send_records instead of described/send_schema_id.

Protocols● Open access↗
FA-19242

Application schema-version exchange controller: unset / describe · case 02

While unset, event describe produces ready/send_records instead of described/send_schema_id.

Protocols◈ Members↗
FA-19243

Application schema-version exchange controller: unset / describe · case 03

While unset, event describe produces ready/send_records instead of described/send_schema_id.

Protocols◈ Members↗
FA-19244

Application schema-version exchange controller: unset / describe · case 04

While unset, event describe produces ready/send_records instead of described/send_schema_id.

Protocols◈ Members↗
FA-19245

Application schema-version exchange controller: unset / describe · case 05

While unset, event describe produces ready/send_records instead of described/send_schema_id.

Protocols◈ Members↗
FA-19246

Application schema-version exchange controller: described / known schema · case 01

While described, event known_schema produces described/wait instead of ready/ack_schema.

Protocols● Open access↗
FA-19247

Application schema-version exchange controller: described / known schema · case 02

While described, event known_schema produces described/wait instead of ready/ack_schema.

Protocols◈ Members↗
FA-19248

Application schema-version exchange controller: described / known schema · case 03

While described, event known_schema produces described/wait instead of ready/ack_schema.

Protocols◈ Members↗
FA-19249

Application schema-version exchange controller: described / known schema · case 04

While described, event known_schema produces described/wait instead of ready/ack_schema.

Protocols◈ Members↗
FA-19250

Application schema-version exchange controller: described / known schema · case 05

While described, event known_schema produces described/wait instead of ready/ack_schema.

Protocols◈ Members↗
FA-19251

Application schema-version exchange controller: described / unknown schema · case 01

While described, event unknown_schema produces ready/send_records instead of defining/send_definition.

Protocols● Open access↗
FA-19252

Application schema-version exchange controller: described / unknown schema · case 02

While described, event unknown_schema produces ready/send_records instead of defining/send_definition.

Protocols◈ Members↗
FA-19253

Application schema-version exchange controller: described / unknown schema · case 03

While described, event unknown_schema produces ready/send_records instead of defining/send_definition.

Protocols◈ Members↗
FA-19254

Application schema-version exchange controller: described / unknown schema · case 04

While described, event unknown_schema produces ready/send_records instead of defining/send_definition.

Protocols◈ Members↗
FA-19255

Application schema-version exchange controller: described / unknown schema · case 05

While described, event unknown_schema produces ready/send_records instead of defining/send_definition.

Protocols◈ Members↗
FA-19256

Application schema-version exchange controller: defining / definition accepted · case 01

While defining, event definition_accepted produces defining/wait instead of ready/enable_records.

Protocols● Open access↗
FA-19257

Application schema-version exchange controller: defining / definition accepted · case 02

While defining, event definition_accepted produces defining/wait instead of ready/enable_records.

Protocols◈ Members↗
FA-19258

Application schema-version exchange controller: defining / definition accepted · case 03

While defining, event definition_accepted produces defining/wait instead of ready/enable_records.

Protocols◈ Members↗
FA-19259

Application schema-version exchange controller: defining / definition accepted · case 04

While defining, event definition_accepted produces defining/wait instead of ready/enable_records.

Protocols◈ Members↗
FA-19260

Application schema-version exchange controller: defining / definition accepted · case 05

While defining, event definition_accepted produces defining/wait instead of ready/enable_records.

Protocols◈ Members↗
FA-19261

Application schema-version exchange controller: defining / definition rejected · case 01

While defining, event definition_rejected produces ready/enable_records instead of failed/stop_records.

Protocols● Open access↗
FA-19262

Application schema-version exchange controller: defining / definition rejected · case 02

While defining, event definition_rejected produces ready/enable_records instead of failed/stop_records.

Protocols◈ Members↗
FA-19263

Application schema-version exchange controller: defining / definition rejected · case 03

While defining, event definition_rejected produces ready/enable_records instead of failed/stop_records.

Protocols◈ Members↗
FA-19264

Application schema-version exchange controller: defining / definition rejected · case 04

While defining, event definition_rejected produces ready/enable_records instead of failed/stop_records.

Protocols◈ Members↗
FA-19265

Application schema-version exchange controller: defining / definition rejected · case 05

While defining, event definition_rejected produces ready/enable_records instead of failed/stop_records.

Protocols◈ Members↗
FA-19266

Application schema-version exchange controller: ready / schema change · case 01

While ready, event schema_change produces ready/send_records instead of described/pause_describe.

Protocols● Open access↗
FA-19267

Application schema-version exchange controller: ready / schema change · case 02

While ready, event schema_change produces ready/send_records instead of described/pause_describe.

Protocols◈ Members↗
FA-19268

Application schema-version exchange controller: ready / schema change · case 03

While ready, event schema_change produces ready/send_records instead of described/pause_describe.

Protocols◈ Members↗
FA-19269

Application schema-version exchange controller: ready / schema change · case 04

While ready, event schema_change produces ready/send_records instead of described/pause_describe.

Protocols◈ Members↗
FA-19270

Application schema-version exchange controller: ready / schema change · case 05

While ready, event schema_change produces ready/send_records instead of described/pause_describe.

Protocols◈ Members↗
FA-19271

Application schema-version exchange controller: ready / record · case 01

While ready, event record produces ready/decode_latest instead of ready/decode_agreed.

Protocols● Open access↗
FA-19272

Application schema-version exchange controller: ready / record · case 02

While ready, event record produces ready/decode_latest instead of ready/decode_agreed.

Protocols◈ Members↗
FA-19273

Application schema-version exchange controller: ready / record · case 03

While ready, event record produces ready/decode_latest instead of ready/decode_agreed.

Protocols◈ Members↗
FA-19274

Application schema-version exchange controller: ready / record · case 04

While ready, event record produces ready/decode_latest instead of ready/decode_agreed.

Protocols◈ Members↗
FA-19275

Application schema-version exchange controller: ready / record · case 05

While ready, event record produces ready/decode_latest instead of ready/decode_agreed.

Protocols◈ Members↗
FA-19276

Application schema-version exchange controller: unset / record · case 01

While unset, event record produces ready/decode_default instead of unset/reject_untyped.

Protocols● Open access↗
FA-19277

Application schema-version exchange controller: unset / record · case 02

While unset, event record produces ready/decode_default instead of unset/reject_untyped.

Protocols◈ Members↗
FA-19278

Application schema-version exchange controller: unset / record · case 03

While unset, event record produces ready/decode_default instead of unset/reject_untyped.

Protocols◈ Members↗
FA-19279

Application schema-version exchange controller: unset / record · case 04

While unset, event record produces ready/decode_default instead of unset/reject_untyped.

Protocols◈ Members↗
FA-19280

Application schema-version exchange controller: unset / record · case 05

While unset, event record produces ready/decode_default instead of unset/reject_untyped.

Protocols◈ Members↗
FA-19281

Application schema-version exchange controller: failed / fresh description · case 01

While failed, event fresh_description produces failed/stop_records instead of described/send_schema_id.

Protocols● Open access↗
FA-19282

Application schema-version exchange controller: failed / fresh description · case 02

While failed, event fresh_description produces failed/stop_records instead of described/send_schema_id.

Protocols◈ Members↗
FA-19283

Application schema-version exchange controller: failed / fresh description · case 03

While failed, event fresh_description produces failed/stop_records instead of described/send_schema_id.

Protocols◈ Members↗
FA-19284

Application schema-version exchange controller: failed / fresh description · case 04

While failed, event fresh_description produces failed/stop_records instead of described/send_schema_id.

Protocols◈ Members↗
FA-19285

Application schema-version exchange controller: failed / fresh description · case 05

While failed, event fresh_description produces failed/stop_records instead of described/send_schema_id.

Protocols◈ Members↗
FA-19286

Application schema-version exchange controller: ready / duplicate definition · case 01

While ready, event duplicate_definition produces defining/replace_schema instead of ready/ack_existing.

Protocols● Open access↗
FA-19287

Application schema-version exchange controller: ready / duplicate definition · case 02

While ready, event duplicate_definition produces defining/replace_schema instead of ready/ack_existing.

Protocols◈ Members↗
FA-19288

Application schema-version exchange controller: ready / duplicate definition · case 03

While ready, event duplicate_definition produces defining/replace_schema instead of ready/ack_existing.

Protocols◈ Members↗
FA-19289

Application schema-version exchange controller: ready / duplicate definition · case 04

While ready, event duplicate_definition produces defining/replace_schema instead of ready/ack_existing.

Protocols◈ Members↗
FA-19290

Application schema-version exchange controller: ready / duplicate definition · case 05

While ready, event duplicate_definition produces defining/replace_schema instead of ready/ack_existing.

Protocols◈ Members↗
FA-19291

Compression dictionary installation controller: empty / offer · case 01

While empty, event offer produces active/compress instead of offered/send_fingerprint.

Protocols● Open access↗
FA-19292

Compression dictionary installation controller: empty / offer · case 02

While empty, event offer produces active/compress instead of offered/send_fingerprint.

Protocols◈ Members↗
FA-19293

Compression dictionary installation controller: empty / offer · case 03

While empty, event offer produces active/compress instead of offered/send_fingerprint.

Protocols◈ Members↗
FA-19294

Compression dictionary installation controller: empty / offer · case 04

While empty, event offer produces active/compress instead of offered/send_fingerprint.

Protocols◈ Members↗
FA-19295

Compression dictionary installation controller: empty / offer · case 05

While empty, event offer produces active/compress instead of offered/send_fingerprint.

Protocols◈ Members↗
FA-19296

Compression dictionary installation controller: offered / cache hit · case 01

While offered, event cache_hit produces installing/send_dictionary instead of active/select_cached.

Protocols● Open access↗
FA-19297

Compression dictionary installation controller: offered / cache hit · case 02

While offered, event cache_hit produces installing/send_dictionary instead of active/select_cached.

Protocols◈ Members↗
FA-19298

Compression dictionary installation controller: offered / cache hit · case 03

While offered, event cache_hit produces installing/send_dictionary instead of active/select_cached.

Protocols◈ Members↗
FA-19299

Compression dictionary installation controller: offered / cache hit · case 04

While offered, event cache_hit produces installing/send_dictionary instead of active/select_cached.

Protocols◈ Members↗
FA-19300

Compression dictionary installation controller: offered / cache hit · case 05

While offered, event cache_hit produces installing/send_dictionary instead of active/select_cached.

Protocols◈ 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 ↗