FA-29245 / HTTP redirects / Member archive

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.

Member previewVariant 5 · 3 implementations · 7 checks per implementation

Case contract

Retain redirect-edge provenance when materializing a chain audit record. 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 1	`{"decision": [["/b", "/c"], ["/b", "/c"], true, true, true, 1, 1, false, true, [301, 302]], "request": "/requests/5/0"}`	`{"decision": [["/a", "/b"], ["/b", "/c"], true, true, true, 1, 1, false, true, [301, 302]], "request": "/requests/5/0"}`	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.