FA-19389 / Protocols / Member archive

Checkpoint transfer boundary controller: idle / chunk · case 04

While idle, event chunk produces receiving/write_staging instead of idle/reject_unoffered.

Member previewVariant 4 · 3 implementations · 14 checks per implementation

Case contract

For the stipulated Checkpoint transfer boundary controller, initialize the explicitly shown resource registers from seed (1..5), then consume classified events sequentially. After each event return a deep snapshot of phase, resource registers, and cumulative emitted control frames. The explicit ten phase/event rules and their resource effects define admission and response semantics. Unlisted events preserve phase and emit rejection. Payload is the consecutive integers seed through 2*seed+1. Empty event input returns no observations.

Why this case matters

Incorrect event admission now changes concrete queued data, resource ownership, or emitted protocol frames and subsequent trace behavior.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
idle/chunk	`[{"frames": [], "phase": "receiving", "registers": {"activations": 0, "allocated": false, "live": [2], "staging": [3, 4, 5, 6, 7, 8, 9], "verified": false}}]`	`[{"frames": [["UNSOLICITED_CHUNK", 4]], "phase": "idle", "registers": {"activations": 0, "allocated": false, "live": [2], "staging": [3], "verified": false}}]`	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.