FA-45769 / Data systems / Member archive

Exchange silently routes unmapped keys to receiver zero · case 04

Exchange silently routes unmapped keys to receiver zero.

Member previewVariant 4 · 3 implementations · 7 checks per implementation

Case contract

Route [id,key,payload] rows into fixed receiver partitions using a supplied key-to-partition table. Null keys use the explicit null partition; unmapped non-null keys produce UNMAPPED side output. Preserve source order within each receiver, retain empty receivers, and preserve repeated rows.

Why this case matters

A bounded deterministic data engine model makes representation and changelog faults reproducible.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
unmapped	`[[[[10, 4]], []], []]`	`[[[], []], [[10, "UNMAPPED"]]]`	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.