FA-29205 / HTTP redirects / Member archive

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.

Member previewVariant 5 · 3 implementations · 7 checks per implementation

Case contract

Compose explicit redirect policy decisions with veto precedence and reason retention. The explicit fixture inputs and outputs define a bounded offline policy; request identity must accompany the decision.

Why this case matters

Models a redirect controller decision before following a target or exposing a redirect result.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
fixture 4	`{"decision": [false, "host", ["host"], true, true, false, ["host", "port"], true, 2, false], "request": "/requests/5/3"}`	`{"decision": [false, "host", ["host", "port"], true, true, false, ["host", "port"], true, 2, false], "request": "/requests/5/3"}`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.