FA-29253 / HTTP redirects / Member archive
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.
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 fixtureThis sample comes from the broken implementation of a controlled reproducer.
| Boundary fixture | Actual | Expected | Outcome |
|---|---|---|---|
| fixture 6 | {"decision": [["/a", "/x"], ["/b", "/c"], true, true, true, 1, 1, false, false, [301, 302]], "request": "/requests/3/5"} | {"decision": [["/a", "/x"], ["/b", "/c"], false, true, true, 1, 1, false, false, [301, 302]], "request": "/requests/3/5"} | 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.
Sign in to the archive ↗