FA-29258 / HTTP redirects / Member archive

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.

Member previewVariant 3 · 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 2	`{"decision": [[], [], true, false, true, 0, 0, false, true, []], "request": "/requests/3/1"}`	`{"decision": [[], [], true, true, true, 0, 0, false, true, []], "request": "/requests/3/1"}`	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.