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

Compose explicit redirect policy decisions with veto precedence and reason retention: all veto reasons · case 01

Compose explicit redirect policy decisions with veto precedence and reason retention: the all veto reasons branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29202

Compose explicit redirect policy decisions with veto precedence and reason retention: all veto reasons · case 02

Compose explicit redirect policy decisions with veto precedence and reason retention: the all veto reasons branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29203

Compose explicit redirect policy decisions with veto precedence and reason retention: all veto reasons · case 03

Compose explicit redirect policy decisions with veto precedence and reason retention: the all veto reasons branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29204

Compose explicit redirect policy decisions with veto precedence and reason retention: all veto reasons · case 04

Compose explicit redirect policy decisions with veto precedence and reason retention: the all veto reasons branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29205

Compose explicit redirect policy decisions with veto precedence and reason retention: all veto reasons · case 05

Compose explicit redirect policy decisions with veto precedence and reason retention: the all veto reasons branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29206

Compose explicit redirect policy decisions with veto precedence and reason retention: inspection required before follow · case 01

Compose explicit redirect policy decisions with veto precedence and reason retention: the inspection required before follow branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29207

Compose explicit redirect policy decisions with veto precedence and reason retention: inspection required before follow · case 02

Compose explicit redirect policy decisions with veto precedence and reason retention: the inspection required before follow branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29208

Compose explicit redirect policy decisions with veto precedence and reason retention: inspection required before follow · case 03

Compose explicit redirect policy decisions with veto precedence and reason retention: the inspection required before follow branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29209

Compose explicit redirect policy decisions with veto precedence and reason retention: inspection required before follow · case 04

Compose explicit redirect policy decisions with veto precedence and reason retention: the inspection required before follow branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29210

Compose explicit redirect policy decisions with veto precedence and reason retention: inspection required before follow · case 05

Compose explicit redirect policy decisions with veto precedence and reason retention: the inspection required before follow branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29211

Compose explicit redirect policy decisions with veto precedence and reason retention: override does not enable error mode · case 01

Compose explicit redirect policy decisions with veto precedence and reason retention: the override does not enable error mode branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29212

Compose explicit redirect policy decisions with veto precedence and reason retention: override does not enable error mode · case 02

Compose explicit redirect policy decisions with veto precedence and reason retention: the override does not enable error mode branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29213

Compose explicit redirect policy decisions with veto precedence and reason retention: override does not enable error mode · case 03

Compose explicit redirect policy decisions with veto precedence and reason retention: the override does not enable error mode branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29214

Compose explicit redirect policy decisions with veto precedence and reason retention: override does not enable error mode · case 04

Compose explicit redirect policy decisions with veto precedence and reason retention: the override does not enable error mode branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29215

Compose explicit redirect policy decisions with veto precedence and reason retention: override does not enable error mode · case 05

Compose explicit redirect policy decisions with veto precedence and reason retention: the override does not enable error mode branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29216

Compose explicit redirect policy decisions with veto precedence and reason retention: manual veto still visible · case 01

Compose explicit redirect policy decisions with veto precedence and reason retention: the manual veto still visible branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29217

Compose explicit redirect policy decisions with veto precedence and reason retention: manual veto still visible · case 02

Compose explicit redirect policy decisions with veto precedence and reason retention: the manual veto still visible branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29218

Compose explicit redirect policy decisions with veto precedence and reason retention: manual veto still visible · case 03

Compose explicit redirect policy decisions with veto precedence and reason retention: the manual veto still visible branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29219

Compose explicit redirect policy decisions with veto precedence and reason retention: manual veto still visible · case 04

Compose explicit redirect policy decisions with veto precedence and reason retention: the manual veto still visible branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29220

Compose explicit redirect policy decisions with veto precedence and reason retention: manual veto still visible · case 05

Compose explicit redirect policy decisions with veto precedence and reason retention: the manual veto still visible branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29221

Compose explicit redirect policy decisions with veto precedence and reason retention: decision reasons ordered · case 01

Compose explicit redirect policy decisions with veto precedence and reason retention: the decision reasons ordered branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29222

Compose explicit redirect policy decisions with veto precedence and reason retention: decision reasons ordered · case 02

Compose explicit redirect policy decisions with veto precedence and reason retention: the decision reasons ordered branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29223

Compose explicit redirect policy decisions with veto precedence and reason retention: decision reasons ordered · case 03

Compose explicit redirect policy decisions with veto precedence and reason retention: the decision reasons ordered branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29224

Compose explicit redirect policy decisions with veto precedence and reason retention: decision reasons ordered · case 04

Compose explicit redirect policy decisions with veto precedence and reason retention: the decision reasons ordered branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29225

Compose explicit redirect policy decisions with veto precedence and reason retention: decision reasons ordered · case 05

Compose explicit redirect policy decisions with veto precedence and reason retention: the decision reasons ordered branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29226

Compose explicit redirect policy decisions with veto precedence and reason retention: missing target preempts override · case 01

Compose explicit redirect policy decisions with veto precedence and reason retention: the missing target preempts override branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29227

Compose explicit redirect policy decisions with veto precedence and reason retention: missing target preempts override · case 02

Compose explicit redirect policy decisions with veto precedence and reason retention: the missing target preempts override branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29228

Compose explicit redirect policy decisions with veto precedence and reason retention: missing target preempts override · case 03

Compose explicit redirect policy decisions with veto precedence and reason retention: the missing target preempts override branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29229

Compose explicit redirect policy decisions with veto precedence and reason retention: missing target preempts override · case 04

Compose explicit redirect policy decisions with veto precedence and reason retention: the missing target preempts override branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29230

Compose explicit redirect policy decisions with veto precedence and reason retention: missing target preempts override · case 05

Compose explicit redirect policy decisions with veto precedence and reason retention: the missing target preempts override branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29231

Compose explicit redirect policy decisions with veto precedence and reason retention: veto count · case 01

Compose explicit redirect policy decisions with veto precedence and reason retention: the veto count branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29232

Compose explicit redirect policy decisions with veto precedence and reason retention: veto count · case 02

Compose explicit redirect policy decisions with veto precedence and reason retention: the veto count branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29233

Compose explicit redirect policy decisions with veto precedence and reason retention: veto count · case 03

Compose explicit redirect policy decisions with veto precedence and reason retention: the veto count branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29234

Compose explicit redirect policy decisions with veto precedence and reason retention: veto count · case 04

Compose explicit redirect policy decisions with veto precedence and reason retention: the veto count branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29235

Compose explicit redirect policy decisions with veto precedence and reason retention: veto count · case 05

Compose explicit redirect policy decisions with veto precedence and reason retention: the veto count branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29236

Compose explicit redirect policy decisions with veto precedence and reason retention: inspection state not success · case 01

Compose explicit redirect policy decisions with veto precedence and reason retention: the inspection state not success branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29237

Compose explicit redirect policy decisions with veto precedence and reason retention: inspection state not success · case 02

Compose explicit redirect policy decisions with veto precedence and reason retention: the inspection state not success branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29238

Compose explicit redirect policy decisions with veto precedence and reason retention: inspection state not success · case 03

Compose explicit redirect policy decisions with veto precedence and reason retention: the inspection state not success branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29239

Compose explicit redirect policy decisions with veto precedence and reason retention: inspection state not success · case 04

Compose explicit redirect policy decisions with veto precedence and reason retention: the inspection state not success branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29240

Compose explicit redirect policy decisions with veto precedence and reason retention: inspection state not success · case 05

Compose explicit redirect policy decisions with veto precedence and reason retention: the inspection state not success branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29241

Retain redirect-edge provenance when materializing a chain audit record: edge source sequence · case 01

Retain redirect-edge provenance when materializing a chain audit record: the edge source sequence branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29242

Retain redirect-edge provenance when materializing a chain audit record: edge source sequence · case 02

Retain redirect-edge provenance when materializing a chain audit record: the edge source sequence branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29243

Retain redirect-edge provenance when materializing a chain audit record: edge source sequence · case 03

Retain redirect-edge provenance when materializing a chain audit record: the edge source sequence branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29244

Retain redirect-edge provenance when materializing a chain audit record: edge source sequence · case 04

Retain redirect-edge provenance when materializing a chain audit record: the edge source sequence branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29245

Retain redirect-edge provenance when materializing a chain audit record: edge source sequence · case 05

Retain redirect-edge provenance when materializing a chain audit record: the edge source sequence branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29246

Retain redirect-edge provenance when materializing a chain audit record: edge target sequence · case 01

Retain redirect-edge provenance when materializing a chain audit record: the edge target sequence branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29247

Retain redirect-edge provenance when materializing a chain audit record: edge target sequence · case 02

Retain redirect-edge provenance when materializing a chain audit record: the edge target sequence branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29248

Retain redirect-edge provenance when materializing a chain audit record: edge target sequence · case 03

Retain redirect-edge provenance when materializing a chain audit record: the edge target sequence branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29249

Retain redirect-edge provenance when materializing a chain audit record: edge target sequence · case 04

Retain redirect-edge provenance when materializing a chain audit record: the edge target sequence branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29250

Retain redirect-edge provenance when materializing a chain audit record: edge target sequence · case 05

Retain redirect-edge provenance when materializing a chain audit record: the edge target sequence branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29251

Retain redirect-edge provenance when materializing a chain audit record: continuity validation · case 01

Retain redirect-edge provenance when materializing a chain audit record: the continuity validation branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29252

Retain redirect-edge provenance when materializing a chain audit record: continuity validation · case 02

Retain redirect-edge provenance when materializing a chain audit record: the continuity validation branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29253

Retain redirect-edge provenance when materializing a chain audit record: continuity validation · case 03

Retain redirect-edge provenance when materializing a chain audit record: the continuity validation branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29254

Retain redirect-edge provenance when materializing a chain audit record: continuity validation · case 04

Retain redirect-edge provenance when materializing a chain audit record: the continuity validation branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29255

Retain redirect-edge provenance when materializing a chain audit record: continuity validation · case 05

Retain redirect-edge provenance when materializing a chain audit record: the continuity validation branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29256

Retain redirect-edge provenance when materializing a chain audit record: first source original · case 01

Retain redirect-edge provenance when materializing a chain audit record: the first source original branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29257

Retain redirect-edge provenance when materializing a chain audit record: first source original · case 02

Retain redirect-edge provenance when materializing a chain audit record: the first source original branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29258

Retain redirect-edge provenance when materializing a chain audit record: first source original · case 03

Retain redirect-edge provenance when materializing a chain audit record: the first source original branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29259

Retain redirect-edge provenance when materializing a chain audit record: first source original · case 04

Retain redirect-edge provenance when materializing a chain audit record: the first source original branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29260

Retain redirect-edge provenance when materializing a chain audit record: first source original · case 05

Retain redirect-edge provenance when materializing a chain audit record: the first source original branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29261

Retain redirect-edge provenance when materializing a chain audit record: terminal target consistency · case 01

Retain redirect-edge provenance when materializing a chain audit record: the terminal target consistency branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29262

Retain redirect-edge provenance when materializing a chain audit record: terminal target consistency · case 02

Retain redirect-edge provenance when materializing a chain audit record: the terminal target consistency branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29263

Retain redirect-edge provenance when materializing a chain audit record: terminal target consistency · case 03

Retain redirect-edge provenance when materializing a chain audit record: the terminal target consistency branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29264

Retain redirect-edge provenance when materializing a chain audit record: terminal target consistency · case 04

Retain redirect-edge provenance when materializing a chain audit record: the terminal target consistency branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29265

Retain redirect-edge provenance when materializing a chain audit record: terminal target consistency · case 05

Retain redirect-edge provenance when materializing a chain audit record: the terminal target consistency branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29266

Retain redirect-edge provenance when materializing a chain audit record: cached edge count · case 01

Retain redirect-edge provenance when materializing a chain audit record: the cached edge count branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29267

Retain redirect-edge provenance when materializing a chain audit record: cached edge count · case 02

Retain redirect-edge provenance when materializing a chain audit record: the cached edge count branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29268

Retain redirect-edge provenance when materializing a chain audit record: cached edge count · case 03

Retain redirect-edge provenance when materializing a chain audit record: the cached edge count branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29269

Retain redirect-edge provenance when materializing a chain audit record: cached edge count · case 04

Retain redirect-edge provenance when materializing a chain audit record: the cached edge count branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29270

Retain redirect-edge provenance when materializing a chain audit record: cached edge count · case 05

Retain redirect-edge provenance when materializing a chain audit record: the cached edge count branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29271

Retain redirect-edge provenance when materializing a chain audit record: network edge count · case 01

Retain redirect-edge provenance when materializing a chain audit record: the network edge count branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29272

Retain redirect-edge provenance when materializing a chain audit record: network edge count · case 02

Retain redirect-edge provenance when materializing a chain audit record: the network edge count branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29273

Retain redirect-edge provenance when materializing a chain audit record: network edge count · case 03

Retain redirect-edge provenance when materializing a chain audit record: the network edge count branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29274

Retain redirect-edge provenance when materializing a chain audit record: network edge count · case 04

Retain redirect-edge provenance when materializing a chain audit record: the network edge count branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29275

Retain redirect-edge provenance when materializing a chain audit record: network edge count · case 05

Retain redirect-edge provenance when materializing a chain audit record: the network edge count branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29276

Retain redirect-edge provenance when materializing a chain audit record: permanent entire chain · case 01

Retain redirect-edge provenance when materializing a chain audit record: the permanent entire chain branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29277

Retain redirect-edge provenance when materializing a chain audit record: permanent entire chain · case 02

Retain redirect-edge provenance when materializing a chain audit record: the permanent entire chain branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29278

Retain redirect-edge provenance when materializing a chain audit record: permanent entire chain · case 03

Retain redirect-edge provenance when materializing a chain audit record: the permanent entire chain branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29279

Retain redirect-edge provenance when materializing a chain audit record: permanent entire chain · case 04

Retain redirect-edge provenance when materializing a chain audit record: the permanent entire chain branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29280

Retain redirect-edge provenance when materializing a chain audit record: permanent entire chain · case 05

Retain redirect-edge provenance when materializing a chain audit record: the permanent entire chain branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29281

Retain redirect-edge provenance when materializing a chain audit record: success independent of hops · case 01

Retain redirect-edge provenance when materializing a chain audit record: the success independent of hops branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29282

Retain redirect-edge provenance when materializing a chain audit record: success independent of hops · case 02

Retain redirect-edge provenance when materializing a chain audit record: the success independent of hops branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29283

Retain redirect-edge provenance when materializing a chain audit record: success independent of hops · case 03

Retain redirect-edge provenance when materializing a chain audit record: the success independent of hops branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29284

Retain redirect-edge provenance when materializing a chain audit record: success independent of hops · case 04

Retain redirect-edge provenance when materializing a chain audit record: the success independent of hops branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29285

Retain redirect-edge provenance when materializing a chain audit record: success independent of hops · case 05

Retain redirect-edge provenance when materializing a chain audit record: the success independent of hops branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29286

Retain redirect-edge provenance when materializing a chain audit record: status sequence preserved · case 01

Retain redirect-edge provenance when materializing a chain audit record: the status sequence preserved branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29287

Retain redirect-edge provenance when materializing a chain audit record: status sequence preserved · case 02

Retain redirect-edge provenance when materializing a chain audit record: the status sequence preserved branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29288

Retain redirect-edge provenance when materializing a chain audit record: status sequence preserved · case 03

Retain redirect-edge provenance when materializing a chain audit record: the status sequence preserved branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29289

Retain redirect-edge provenance when materializing a chain audit record: status sequence preserved · case 04

Retain redirect-edge provenance when materializing a chain audit record: the status sequence preserved branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29290

Retain redirect-edge provenance when materializing a chain audit record: status sequence preserved · case 05

Retain redirect-edge provenance when materializing a chain audit record: the status sequence preserved branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29291

Report redirect failures with the failing phase and completed request context: phase preserved · case 01

Report redirect failures with the failing phase and completed request context: the phase preserved branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29292

Report redirect failures with the failing phase and completed request context: phase preserved · case 02

Report redirect failures with the failing phase and completed request context: the phase preserved branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29293

Report redirect failures with the failing phase and completed request context: phase preserved · case 03

Report redirect failures with the failing phase and completed request context: the phase preserved branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29294

Report redirect failures with the failing phase and completed request context: phase preserved · case 04

Report redirect failures with the failing phase and completed request context: the phase preserved branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29295

Report redirect failures with the failing phase and completed request context: phase preserved · case 05

Report redirect failures with the failing phase and completed request context: the phase preserved branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29296

Report redirect failures with the failing phase and completed request context: original request retained · case 01

Report redirect failures with the failing phase and completed request context: the original request retained branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29297

Report redirect failures with the failing phase and completed request context: original request retained · case 02

Report redirect failures with the failing phase and completed request context: the original request retained branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29298

Report redirect failures with the failing phase and completed request context: original request retained · case 03

Report redirect failures with the failing phase and completed request context: the original request retained branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29299

Report redirect failures with the failing phase and completed request context: original request retained · case 04

Report redirect failures with the failing phase and completed request context: the original request retained branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29300

Report redirect failures with the failing phase and completed request context: original request retained · case 05

Report redirect failures with the failing phase and completed request context: the original request retained branch emits an incorrect decision.

HTTP redirects◈ 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 ↗