FA-7315 / Transport flow control / Member archive

Datagram truncation is reported separately from copied length · case 05

Datagram truncation is reported separately from copied length.

Member previewVariant 5 · 3 implementations · 4 checks per implementation

Case contract

Bounded offline decision model: datagram truncation is reported separately from copied length. Inputs are already validated protocol fields; the explicit fixtures define the supported policy, not a complete protocol implementation.

Why this case matters

This deterministic transport flow control model isolates the datagram-truncation-is-reported-separately-from-copied-length 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 4	`["", 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.