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

Canonicalize a directory URL after resource lookup without redirecting regular files: query survives directory redirect · case 01

Canonicalize a directory URL after resource lookup without redirecting regular files: the query survives directory redirect branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29102

Canonicalize a directory URL after resource lookup without redirecting regular files: query survives directory redirect · case 02

Canonicalize a directory URL after resource lookup without redirecting regular files: the query survives directory redirect branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29103

Canonicalize a directory URL after resource lookup without redirecting regular files: query survives directory redirect · case 03

Canonicalize a directory URL after resource lookup without redirecting regular files: the query survives directory redirect branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29104

Canonicalize a directory URL after resource lookup without redirecting regular files: query survives directory redirect · case 04

Canonicalize a directory URL after resource lookup without redirecting regular files: the query survives directory redirect branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29105

Canonicalize a directory URL after resource lookup without redirecting regular files: query survives directory redirect · case 05

Canonicalize a directory URL after resource lookup without redirecting regular files: the query survives directory redirect branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29106

Canonicalize a directory URL after resource lookup without redirecting regular files: index filename match · case 01

Canonicalize a directory URL after resource lookup without redirecting regular files: the index filename match branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29107

Canonicalize a directory URL after resource lookup without redirecting regular files: index filename match · case 02

Canonicalize a directory URL after resource lookup without redirecting regular files: the index filename match branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29108

Canonicalize a directory URL after resource lookup without redirecting regular files: index filename match · case 03

Canonicalize a directory URL after resource lookup without redirecting regular files: the index filename match branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29109

Canonicalize a directory URL after resource lookup without redirecting regular files: index filename match · case 04

Canonicalize a directory URL after resource lookup without redirecting regular files: the index filename match branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29110

Canonicalize a directory URL after resource lookup without redirecting regular files: index filename match · case 05

Canonicalize a directory URL after resource lookup without redirecting regular files: the index filename match branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29111

Canonicalize a directory URL after resource lookup without redirecting regular files: parent for index removal · case 01

Canonicalize a directory URL after resource lookup without redirecting regular files: the parent for index removal branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29112

Canonicalize a directory URL after resource lookup without redirecting regular files: parent for index removal · case 02

Canonicalize a directory URL after resource lookup without redirecting regular files: the parent for index removal branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29113

Canonicalize a directory URL after resource lookup without redirecting regular files: parent for index removal · case 03

Canonicalize a directory URL after resource lookup without redirecting regular files: the parent for index removal branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29114

Canonicalize a directory URL after resource lookup without redirecting regular files: parent for index removal · case 04

Canonicalize a directory URL after resource lookup without redirecting regular files: the parent for index removal branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29115

Canonicalize a directory URL after resource lookup without redirecting regular files: parent for index removal · case 05

Canonicalize a directory URL after resource lookup without redirecting regular files: the parent for index removal branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29116

Canonicalize a directory URL after resource lookup without redirecting regular files: already served no redirect · case 01

Canonicalize a directory URL after resource lookup without redirecting regular files: the already served no redirect branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29117

Canonicalize a directory URL after resource lookup without redirecting regular files: already served no redirect · case 02

Canonicalize a directory URL after resource lookup without redirecting regular files: the already served no redirect branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29118

Canonicalize a directory URL after resource lookup without redirecting regular files: already served no redirect · case 03

Canonicalize a directory URL after resource lookup without redirecting regular files: the already served no redirect branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29119

Canonicalize a directory URL after resource lookup without redirecting regular files: already served no redirect · case 04

Canonicalize a directory URL after resource lookup without redirecting regular files: the already served no redirect branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29120

Canonicalize a directory URL after resource lookup without redirecting regular files: already served no redirect · case 05

Canonicalize a directory URL after resource lookup without redirecting regular files: the already served no redirect branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29121

Canonicalize a directory URL after resource lookup without redirecting regular files: lookup before canonicalization · case 01

Canonicalize a directory URL after resource lookup without redirecting regular files: the lookup before canonicalization branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29122

Canonicalize a directory URL after resource lookup without redirecting regular files: lookup before canonicalization · case 02

Canonicalize a directory URL after resource lookup without redirecting regular files: the lookup before canonicalization branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29123

Canonicalize a directory URL after resource lookup without redirecting regular files: lookup before canonicalization · case 03

Canonicalize a directory URL after resource lookup without redirecting regular files: the lookup before canonicalization branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29124

Canonicalize a directory URL after resource lookup without redirecting regular files: lookup before canonicalization · case 04

Canonicalize a directory URL after resource lookup without redirecting regular files: the lookup before canonicalization branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29125

Canonicalize a directory URL after resource lookup without redirecting regular files: lookup before canonicalization · case 05

Canonicalize a directory URL after resource lookup without redirecting regular files: the lookup before canonicalization branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29126

Canonicalize a directory URL after resource lookup without redirecting regular files: root directory not empty · case 01

Canonicalize a directory URL after resource lookup without redirecting regular files: the root directory not empty branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29127

Canonicalize a directory URL after resource lookup without redirecting regular files: root directory not empty · case 02

Canonicalize a directory URL after resource lookup without redirecting regular files: the root directory not empty branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29128

Canonicalize a directory URL after resource lookup without redirecting regular files: root directory not empty · case 03

Canonicalize a directory URL after resource lookup without redirecting regular files: the root directory not empty branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29129

Canonicalize a directory URL after resource lookup without redirecting regular files: root directory not empty · case 04

Canonicalize a directory URL after resource lookup without redirecting regular files: the root directory not empty branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29130

Canonicalize a directory URL after resource lookup without redirecting regular files: root directory not empty · case 05

Canonicalize a directory URL after resource lookup without redirecting regular files: the root directory not empty branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29131

Canonicalize a directory URL after resource lookup without redirecting regular files: basename preserves extension · case 01

Canonicalize a directory URL after resource lookup without redirecting regular files: the basename preserves extension branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29132

Canonicalize a directory URL after resource lookup without redirecting regular files: basename preserves extension · case 02

Canonicalize a directory URL after resource lookup without redirecting regular files: the basename preserves extension branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29133

Canonicalize a directory URL after resource lookup without redirecting regular files: basename preserves extension · case 03

Canonicalize a directory URL after resource lookup without redirecting regular files: the basename preserves extension branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29134

Canonicalize a directory URL after resource lookup without redirecting regular files: basename preserves extension · case 04

Canonicalize a directory URL after resource lookup without redirecting regular files: the basename preserves extension branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29135

Canonicalize a directory URL after resource lookup without redirecting regular files: basename preserves extension · case 05

Canonicalize a directory URL after resource lookup without redirecting regular files: the basename preserves extension branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29136

Canonicalize a directory URL after resource lookup without redirecting regular files: index path join · case 01

Canonicalize a directory URL after resource lookup without redirecting regular files: the index path join branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29137

Canonicalize a directory URL after resource lookup without redirecting regular files: index path join · case 02

Canonicalize a directory URL after resource lookup without redirecting regular files: the index path join branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29138

Canonicalize a directory URL after resource lookup without redirecting regular files: index path join · case 03

Canonicalize a directory URL after resource lookup without redirecting regular files: the index path join branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29139

Canonicalize a directory URL after resource lookup without redirecting regular files: index path join · case 04

Canonicalize a directory URL after resource lookup without redirecting regular files: the index path join branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29140

Canonicalize a directory URL after resource lookup without redirecting regular files: index path join · case 05

Canonicalize a directory URL after resource lookup without redirecting regular files: the index path join branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29141

Extract redirect route captures under an explicit segment-matching grammar: capture after prefix · case 01

Extract redirect route captures under an explicit segment-matching grammar: the capture after prefix branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29142

Extract redirect route captures under an explicit segment-matching grammar: capture after prefix · case 02

Extract redirect route captures under an explicit segment-matching grammar: the capture after prefix branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29143

Extract redirect route captures under an explicit segment-matching grammar: capture after prefix · case 03

Extract redirect route captures under an explicit segment-matching grammar: the capture after prefix branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29144

Extract redirect route captures under an explicit segment-matching grammar: capture after prefix · case 04

Extract redirect route captures under an explicit segment-matching grammar: the capture after prefix branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29145

Extract redirect route captures under an explicit segment-matching grammar: capture after prefix · case 05

Extract redirect route captures under an explicit segment-matching grammar: the capture after prefix branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29146

Extract redirect route captures under an explicit segment-matching grammar: segment wildcard not slash · case 01

Extract redirect route captures under an explicit segment-matching grammar: the segment wildcard not slash branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29147

Extract redirect route captures under an explicit segment-matching grammar: segment wildcard not slash · case 02

Extract redirect route captures under an explicit segment-matching grammar: the segment wildcard not slash branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29148

Extract redirect route captures under an explicit segment-matching grammar: segment wildcard not slash · case 03

Extract redirect route captures under an explicit segment-matching grammar: the segment wildcard not slash branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29149

Extract redirect route captures under an explicit segment-matching grammar: segment wildcard not slash · case 04

Extract redirect route captures under an explicit segment-matching grammar: the segment wildcard not slash branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29150

Extract redirect route captures under an explicit segment-matching grammar: segment wildcard not slash · case 05

Extract redirect route captures under an explicit segment-matching grammar: the segment wildcard not slash branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29151

Extract redirect route captures under an explicit segment-matching grammar: greedy tail retains slashes · case 01

Extract redirect route captures under an explicit segment-matching grammar: the greedy tail retains slashes branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29152

Extract redirect route captures under an explicit segment-matching grammar: greedy tail retains slashes · case 02

Extract redirect route captures under an explicit segment-matching grammar: the greedy tail retains slashes branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29153

Extract redirect route captures under an explicit segment-matching grammar: greedy tail retains slashes · case 03

Extract redirect route captures under an explicit segment-matching grammar: the greedy tail retains slashes branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29154

Extract redirect route captures under an explicit segment-matching grammar: greedy tail retains slashes · case 04

Extract redirect route captures under an explicit segment-matching grammar: the greedy tail retains slashes branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29155

Extract redirect route captures under an explicit segment-matching grammar: greedy tail retains slashes · case 05

Extract redirect route captures under an explicit segment-matching grammar: the greedy tail retains slashes branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29156

Extract redirect route captures under an explicit segment-matching grammar: case setting prefix · case 01

Extract redirect route captures under an explicit segment-matching grammar: the case setting prefix branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29157

Extract redirect route captures under an explicit segment-matching grammar: case setting prefix · case 02

Extract redirect route captures under an explicit segment-matching grammar: the case setting prefix branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29158

Extract redirect route captures under an explicit segment-matching grammar: case setting prefix · case 03

Extract redirect route captures under an explicit segment-matching grammar: the case setting prefix branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29159

Extract redirect route captures under an explicit segment-matching grammar: case setting prefix · case 04

Extract redirect route captures under an explicit segment-matching grammar: the case setting prefix branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29160

Extract redirect route captures under an explicit segment-matching grammar: case setting prefix · case 05

Extract redirect route captures under an explicit segment-matching grammar: the case setting prefix branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29161

Extract redirect route captures under an explicit segment-matching grammar: terminal empty segment kept · case 01

Extract redirect route captures under an explicit segment-matching grammar: the terminal empty segment kept branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29162

Extract redirect route captures under an explicit segment-matching grammar: terminal empty segment kept · case 02

Extract redirect route captures under an explicit segment-matching grammar: the terminal empty segment kept branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29163

Extract redirect route captures under an explicit segment-matching grammar: terminal empty segment kept · case 03

Extract redirect route captures under an explicit segment-matching grammar: the terminal empty segment kept branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29164

Extract redirect route captures under an explicit segment-matching grammar: terminal empty segment kept · case 04

Extract redirect route captures under an explicit segment-matching grammar: the terminal empty segment kept branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29165

Extract redirect route captures under an explicit segment-matching grammar: terminal empty segment kept · case 05

Extract redirect route captures under an explicit segment-matching grammar: the terminal empty segment kept branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29166

Extract redirect route captures under an explicit segment-matching grammar: suffix empty means no strip · case 01

Extract redirect route captures under an explicit segment-matching grammar: the suffix empty means no strip branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29167

Extract redirect route captures under an explicit segment-matching grammar: suffix empty means no strip · case 02

Extract redirect route captures under an explicit segment-matching grammar: the suffix empty means no strip branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29168

Extract redirect route captures under an explicit segment-matching grammar: suffix empty means no strip · case 03

Extract redirect route captures under an explicit segment-matching grammar: the suffix empty means no strip branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29169

Extract redirect route captures under an explicit segment-matching grammar: suffix empty means no strip · case 04

Extract redirect route captures under an explicit segment-matching grammar: the suffix empty means no strip branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29170

Extract redirect route captures under an explicit segment-matching grammar: suffix empty means no strip · case 05

Extract redirect route captures under an explicit segment-matching grammar: the suffix empty means no strip branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29171

Extract redirect route captures under an explicit segment-matching grammar: literal period not wildcard · case 01

Extract redirect route captures under an explicit segment-matching grammar: the literal period not wildcard branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29172

Extract redirect route captures under an explicit segment-matching grammar: literal period not wildcard · case 02

Extract redirect route captures under an explicit segment-matching grammar: the literal period not wildcard branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29173

Extract redirect route captures under an explicit segment-matching grammar: literal period not wildcard · case 03

Extract redirect route captures under an explicit segment-matching grammar: the literal period not wildcard branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29174

Extract redirect route captures under an explicit segment-matching grammar: literal period not wildcard · case 04

Extract redirect route captures under an explicit segment-matching grammar: the literal period not wildcard branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29175

Extract redirect route captures under an explicit segment-matching grammar: literal period not wildcard · case 05

Extract redirect route captures under an explicit segment-matching grammar: the literal period not wildcard branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29176

Extract redirect route captures under an explicit segment-matching grammar: capture preserves empty tail · case 01

Extract redirect route captures under an explicit segment-matching grammar: the capture preserves empty tail branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29177

Extract redirect route captures under an explicit segment-matching grammar: capture preserves empty tail · case 02

Extract redirect route captures under an explicit segment-matching grammar: the capture preserves empty tail branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29178

Extract redirect route captures under an explicit segment-matching grammar: capture preserves empty tail · case 03

Extract redirect route captures under an explicit segment-matching grammar: the capture preserves empty tail branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29179

Extract redirect route captures under an explicit segment-matching grammar: capture preserves empty tail · case 04

Extract redirect route captures under an explicit segment-matching grammar: the capture preserves empty tail branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29180

Extract redirect route captures under an explicit segment-matching grammar: capture preserves empty tail · case 05

Extract redirect route captures under an explicit segment-matching grammar: the capture preserves empty tail branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29181

Extract redirect route captures under an explicit segment-matching grammar: route depth count · case 01

Extract redirect route captures under an explicit segment-matching grammar: the route depth count branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29182

Extract redirect route captures under an explicit segment-matching grammar: route depth count · case 02

Extract redirect route captures under an explicit segment-matching grammar: the route depth count branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29183

Extract redirect route captures under an explicit segment-matching grammar: route depth count · case 03

Extract redirect route captures under an explicit segment-matching grammar: the route depth count branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29184

Extract redirect route captures under an explicit segment-matching grammar: route depth count · case 04

Extract redirect route captures under an explicit segment-matching grammar: the route depth count branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29185

Extract redirect route captures under an explicit segment-matching grammar: route depth count · case 05

Extract redirect route captures under an explicit segment-matching grammar: the route depth count branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29186

Extract redirect route captures under an explicit segment-matching grammar: greedy capture availability · case 01

Extract redirect route captures under an explicit segment-matching grammar: the greedy capture availability branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29187

Extract redirect route captures under an explicit segment-matching grammar: greedy capture availability · case 02

Extract redirect route captures under an explicit segment-matching grammar: the greedy capture availability branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29188

Extract redirect route captures under an explicit segment-matching grammar: greedy capture availability · case 03

Extract redirect route captures under an explicit segment-matching grammar: the greedy capture availability branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29189

Extract redirect route captures under an explicit segment-matching grammar: greedy capture availability · case 04

Extract redirect route captures under an explicit segment-matching grammar: the greedy capture availability branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29190

Extract redirect route captures under an explicit segment-matching grammar: greedy capture availability · case 05

Extract redirect route captures under an explicit segment-matching grammar: the greedy capture availability branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29191

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

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

HTTP redirects● Open access↗
FA-29192

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

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

HTTP redirects◈ Members↗
FA-29193

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

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

HTTP redirects◈ Members↗
FA-29194

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

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

HTTP redirects◈ Members↗
FA-29195

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

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

HTTP redirects◈ Members↗
FA-29196

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

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

HTTP redirects● Open access↗
FA-29197

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

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

HTTP redirects◈ Members↗
FA-29198

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

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

HTTP redirects◈ Members↗
FA-29199

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

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

HTTP redirects◈ Members↗
FA-29200

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

Compose explicit redirect policy decisions with veto precedence and reason retention: the first rejection reason 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 ↗