FA-7119 / Network routing / Member archive

Route header constraint distinguishes existence from truthiness · case 04

Route header constraint distinguishes existence from truthiness.

Member previewVariant 4 · 3 implementations · 4 checks per implementation

Case contract

Given headers, key, route header constraint distinguishes existence from truthiness. Return the protocol decision or transformed value; fields are validated and fixtures state boundary outcomes.

Why this case matters

This deterministic network routing model isolates the route-header-constraint-distinguishes-existence-from-truthiness policy at a network component boundary.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
fixture 1	`false`	`true`	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.