FA-7167 / Network routing / Member archive

Route priority is secondary to match specificity · case 02

Route priority is secondary to match specificity.

Member previewVariant 2 · 3 implementations · 4 checks per implementation

Case contract

Bounded offline decision model: route priority is secondary to match specificity. Inputs are already validated protocol fields; the explicit fixtures define the supported policy, not a complete protocol implementation.

Why this case matters

This deterministic network routing model isolates the route-priority-is-secondary-to-match-specificity 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	`"b"`	`"a"`	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.