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

Deployment promotion gate: Release freezes do not prevent promotion · case 01

Release freezes do not prevent promotion.

Deployment models● Open access↗
FA-10102

Deployment promotion gate: Release freezes do not prevent promotion · case 02

Release freezes do not prevent promotion.

Deployment models◈ Members↗
FA-10103

Deployment promotion gate: Release freezes do not prevent promotion · case 03

Release freezes do not prevent promotion.

Deployment models◈ Members↗
FA-10104

Deployment promotion gate: Release freezes do not prevent promotion · case 04

Release freezes do not prevent promotion.

Deployment models◈ Members↗
FA-10105

Deployment promotion gate: Release freezes do not prevent promotion · case 05

Release freezes do not prevent promotion.

Deployment models◈ Members↗
FA-10106

Deployment drift report: Image changes are absent from the rollout plan · case 01

Image changes are absent from the rollout plan.

Deployment models● Open access↗
FA-10107

Deployment drift report: Image changes are absent from the rollout plan · case 02

Image changes are absent from the rollout plan.

Deployment models◈ Members↗
FA-10108

Deployment drift report: Image changes are absent from the rollout plan · case 03

Image changes are absent from the rollout plan.

Deployment models◈ Members↗
FA-10109

Deployment drift report: Image changes are absent from the rollout plan · case 04

Image changes are absent from the rollout plan.

Deployment models◈ Members↗
FA-10110

Deployment drift report: Image changes are absent from the rollout plan · case 05

Image changes are absent from the rollout plan.

Deployment models◈ Members↗
FA-10111

Deployment drift report: Environment value changes are ignored · case 01

Environment value changes are ignored.

Deployment models● Open access↗
FA-10112

Deployment drift report: Environment value changes are ignored · case 02

Environment value changes are ignored.

Deployment models◈ Members↗
FA-10113

Deployment drift report: Environment value changes are ignored · case 03

Environment value changes are ignored.

Deployment models◈ Members↗
FA-10114

Deployment drift report: Environment value changes are ignored · case 04

Environment value changes are ignored.

Deployment models◈ Members↗
FA-10115

Deployment drift report: Environment value changes are ignored · case 05

Environment value changes are ignored.

Deployment models◈ Members↗
FA-10116

Deployment drift report: Replica count changes are ignored · case 01

Replica count changes are ignored.

Deployment models● Open access↗
FA-10117

Deployment drift report: Replica count changes are ignored · case 02

Replica count changes are ignored.

Deployment models◈ Members↗
FA-10118

Deployment drift report: Replica count changes are ignored · case 03

Replica count changes are ignored.

Deployment models◈ Members↗
FA-10119

Deployment drift report: Replica count changes are ignored · case 04

Replica count changes are ignored.

Deployment models◈ Members↗
FA-10120

Deployment drift report: Replica count changes are ignored · case 05

Replica count changes are ignored.

Deployment models◈ Members↗
FA-10121

Deployment drift report: Reordered command arguments are treated as unchanged · case 01

Reordered command arguments are treated as unchanged.

Deployment models● Open access↗
FA-10122

Deployment drift report: Reordered command arguments are treated as unchanged · case 02

Reordered command arguments are treated as unchanged.

Deployment models◈ Members↗
FA-10123

Deployment drift report: Reordered command arguments are treated as unchanged · case 03

Reordered command arguments are treated as unchanged.

Deployment models◈ Members↗
FA-10124

Deployment drift report: Reordered command arguments are treated as unchanged · case 04

Reordered command arguments are treated as unchanged.

Deployment models◈ Members↗
FA-10125

Deployment drift report: Reordered command arguments are treated as unchanged · case 05

Reordered command arguments are treated as unchanged.

Deployment models◈ Members↗
FA-10126

Deployment drift report: Resource limit changes are ignored · case 01

Resource limit changes are ignored.

Deployment models● Open access↗
FA-10127

Deployment drift report: Resource limit changes are ignored · case 02

Resource limit changes are ignored.

Deployment models◈ Members↗
FA-10128

Deployment drift report: Resource limit changes are ignored · case 03

Resource limit changes are ignored.

Deployment models◈ Members↗
FA-10129

Deployment drift report: Resource limit changes are ignored · case 04

Resource limit changes are ignored.

Deployment models◈ Members↗
FA-10130

Deployment drift report: Resource limit changes are ignored · case 05

Resource limit changes are ignored.

Deployment models◈ Members↗
FA-10131

Replica rollout status: Invalid specifications appear ready · case 01

Invalid specifications appear ready.

Deployment models● Open access↗
FA-10132

Replica rollout status: Invalid specifications appear ready · case 02

Invalid specifications appear ready.

Deployment models◈ Members↗
FA-10133

Replica rollout status: Invalid specifications appear ready · case 03

Invalid specifications appear ready.

Deployment models◈ Members↗
FA-10134

Replica rollout status: Invalid specifications appear ready · case 04

Invalid specifications appear ready.

Deployment models◈ Members↗
FA-10135

Replica rollout status: Invalid specifications appear ready · case 05

Invalid specifications appear ready.

Deployment models◈ Members↗
FA-10136

Replica rollout status: Failed replicas do not degrade rollout · case 01

Failed replicas do not degrade rollout.

Deployment models● Open access↗
FA-10137

Replica rollout status: Failed replicas do not degrade rollout · case 02

Failed replicas do not degrade rollout.

Deployment models◈ Members↗
FA-10138

Replica rollout status: Failed replicas do not degrade rollout · case 03

Failed replicas do not degrade rollout.

Deployment models◈ Members↗
FA-10139

Replica rollout status: Failed replicas do not degrade rollout · case 04

Failed replicas do not degrade rollout.

Deployment models◈ Members↗
FA-10140

Replica rollout status: Failed replicas do not degrade rollout · case 05

Failed replicas do not degrade rollout.

Deployment models◈ Members↗
FA-10141

Replica rollout status: Stale controller observations appear current · case 01

Stale controller observations appear current.

Deployment models● Open access↗
FA-10142

Replica rollout status: Stale controller observations appear current · case 02

Stale controller observations appear current.

Deployment models◈ Members↗
FA-10143

Replica rollout status: Stale controller observations appear current · case 03

Stale controller observations appear current.

Deployment models◈ Members↗
FA-10144

Replica rollout status: Stale controller observations appear current · case 04

Stale controller observations appear current.

Deployment models◈ Members↗
FA-10145

Replica rollout status: Stale controller observations appear current · case 05

Stale controller observations appear current.

Deployment models◈ Members↗
FA-10146

Replica rollout status: Old-revision replicas count as updated · case 01

Old-revision replicas count as updated.

Deployment models● Open access↗
FA-10147

Replica rollout status: Old-revision replicas count as updated · case 02

Old-revision replicas count as updated.

Deployment models◈ Members↗
FA-10148

Replica rollout status: Old-revision replicas count as updated · case 03

Old-revision replicas count as updated.

Deployment models◈ Members↗
FA-10149

Replica rollout status: Old-revision replicas count as updated · case 04

Old-revision replicas count as updated.

Deployment models◈ Members↗
FA-10150

Replica rollout status: Old-revision replicas count as updated · case 05

Old-revision replicas count as updated.

Deployment models◈ Members↗
FA-10151

Replica rollout status: Unavailable replicas count toward readiness · case 01

Unavailable replicas count toward readiness.

Deployment models● Open access↗
FA-10152

Replica rollout status: Unavailable replicas count toward readiness · case 02

Unavailable replicas count toward readiness.

Deployment models◈ Members↗
FA-10153

Replica rollout status: Unavailable replicas count toward readiness · case 03

Unavailable replicas count toward readiness.

Deployment models◈ Members↗
FA-10154

Replica rollout status: Unavailable replicas count toward readiness · case 04

Unavailable replicas count toward readiness.

Deployment models◈ Members↗
FA-10155

Replica rollout status: Unavailable replicas count toward readiness · case 05

Unavailable replicas count toward readiness.

Deployment models◈ Members↗
FA-10156

Rollback revision selection: The active or a future revision is selected for rollback · case 01

The active or a future revision is selected for rollback.

Deployment models● Open access↗
FA-10157

Rollback revision selection: The active or a future revision is selected for rollback · case 02

The active or a future revision is selected for rollback.

Deployment models◈ Members↗
FA-10158

Rollback revision selection: The active or a future revision is selected for rollback · case 03

The active or a future revision is selected for rollback.

Deployment models◈ Members↗
FA-10159

Rollback revision selection: The active or a future revision is selected for rollback · case 04

The active or a future revision is selected for rollback.

Deployment models◈ Members↗
FA-10160

Rollback revision selection: The active or a future revision is selected for rollback · case 05

The active or a future revision is selected for rollback.

Deployment models◈ Members↗
FA-10161

Rollback revision selection: A failed release becomes the rollback target · case 01

A failed release becomes the rollback target.

Deployment models● Open access↗
FA-10162

Rollback revision selection: A failed release becomes the rollback target · case 02

A failed release becomes the rollback target.

Deployment models◈ Members↗
FA-10163

Rollback revision selection: A failed release becomes the rollback target · case 03

A failed release becomes the rollback target.

Deployment models◈ Members↗
FA-10164

Rollback revision selection: A failed release becomes the rollback target · case 04

A failed release becomes the rollback target.

Deployment models◈ Members↗
FA-10165

Rollback revision selection: A failed release becomes the rollback target · case 05

A failed release becomes the rollback target.

Deployment models◈ Members↗
FA-10166

Rollback revision selection: A garbage-collected revision is selected · case 01

A garbage-collected revision is selected.

Deployment models● Open access↗
FA-10167

Rollback revision selection: A garbage-collected revision is selected · case 02

A garbage-collected revision is selected.

Deployment models◈ Members↗
FA-10168

Rollback revision selection: A garbage-collected revision is selected · case 03

A garbage-collected revision is selected.

Deployment models◈ Members↗
FA-10169

Rollback revision selection: A garbage-collected revision is selected · case 04

A garbage-collected revision is selected.

Deployment models◈ Members↗
FA-10170

Rollback revision selection: A garbage-collected revision is selected · case 05

A garbage-collected revision is selected.

Deployment models◈ Members↗
FA-10171

Rollback revision selection: Rollback chooses a revision incompatible with current data · case 01

Rollback chooses a revision incompatible with current data.

Deployment models● Open access↗
FA-10172

Rollback revision selection: Rollback chooses a revision incompatible with current data · case 02

Rollback chooses a revision incompatible with current data.

Deployment models◈ Members↗
FA-10173

Rollback revision selection: Rollback chooses a revision incompatible with current data · case 03

Rollback chooses a revision incompatible with current data.

Deployment models◈ Members↗
FA-10174

Rollback revision selection: Rollback chooses a revision incompatible with current data · case 04

Rollback chooses a revision incompatible with current data.

Deployment models◈ Members↗
FA-10175

Rollback revision selection: Rollback chooses a revision incompatible with current data · case 05

Rollback chooses a revision incompatible with current data.

Deployment models◈ Members↗
FA-10176

Rollback revision selection: Rollback unnecessarily selects the oldest release · case 01

Rollback unnecessarily selects the oldest release.

Deployment models● Open access↗
FA-10177

Rollback revision selection: Rollback unnecessarily selects the oldest release · case 02

Rollback unnecessarily selects the oldest release.

Deployment models◈ Members↗
FA-10178

Rollback revision selection: Rollback unnecessarily selects the oldest release · case 03

Rollback unnecessarily selects the oldest release.

Deployment models◈ Members↗
FA-10179

Rollback revision selection: Rollback unnecessarily selects the oldest release · case 04

Rollback unnecessarily selects the oldest release.

Deployment models◈ Members↗
FA-10180

Rollback revision selection: Rollback unnecessarily selects the oldest release · case 05

Rollback unnecessarily selects the oldest release.

Deployment models◈ Members↗
FA-10181

Release retention selection: The active release can be garbage-collected · case 01

The active release can be garbage-collected.

Deployment models● Open access↗
FA-10182

Release retention selection: The active release can be garbage-collected · case 02

The active release can be garbage-collected.

Deployment models◈ Members↗
FA-10183

Release retention selection: The active release can be garbage-collected · case 03

The active release can be garbage-collected.

Deployment models◈ Members↗
FA-10184

Release retention selection: The active release can be garbage-collected · case 04

The active release can be garbage-collected.

Deployment models◈ Members↗
FA-10185

Release retention selection: The active release can be garbage-collected · case 05

The active release can be garbage-collected.

Deployment models◈ Members↗
FA-10186

Release retention selection: Explicitly pinned releases are deleted · case 01

Explicitly pinned releases are deleted.

Deployment models● Open access↗
FA-10187

Release retention selection: Explicitly pinned releases are deleted · case 02

Explicitly pinned releases are deleted.

Deployment models◈ Members↗
FA-10188

Release retention selection: Explicitly pinned releases are deleted · case 03

Explicitly pinned releases are deleted.

Deployment models◈ Members↗
FA-10189

Release retention selection: Explicitly pinned releases are deleted · case 04

Explicitly pinned releases are deleted.

Deployment models◈ Members↗
FA-10190

Release retention selection: Explicitly pinned releases are deleted · case 05

Explicitly pinned releases are deleted.

Deployment models◈ Members↗
FA-10191

Release retention selection: Failed releases consume successful retention slots · case 01

Failed releases consume successful retention slots.

Deployment models● Open access↗
FA-10192

Release retention selection: Failed releases consume successful retention slots · case 02

Failed releases consume successful retention slots.

Deployment models◈ Members↗
FA-10193

Release retention selection: Failed releases consume successful retention slots · case 03

Failed releases consume successful retention slots.

Deployment models◈ Members↗
FA-10194

Release retention selection: Failed releases consume successful retention slots · case 04

Failed releases consume successful retention slots.

Deployment models◈ Members↗
FA-10195

Release retention selection: Failed releases consume successful retention slots · case 05

Failed releases consume successful retention slots.

Deployment models◈ Members↗
FA-10196

Release retention selection: Old releases displace newer successful releases · case 01

Old releases displace newer successful releases.

Deployment models● Open access↗
FA-10197

Release retention selection: Old releases displace newer successful releases · case 02

Old releases displace newer successful releases.

Deployment models◈ Members↗
FA-10198

Release retention selection: Old releases displace newer successful releases · case 03

Old releases displace newer successful releases.

Deployment models◈ Members↗
FA-10199

Release retention selection: Old releases displace newer successful releases · case 04

Old releases displace newer successful releases.

Deployment models◈ Members↗
FA-10200

Release retention selection: Old releases displace newer successful releases · case 05

Old releases displace newer successful releases.

Deployment models◈ 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 ↗