FIELD RELAY / CASE STUDY
Making messy order exports reviewable.
A fictional operations desk receives partner CSVs that use different headers and sometimes repeat, conflict, or corrupt an order. The question is whether a person can see what will happen before a destination is touched.
Decision design
An adapter maps each partner’s headers. Validation keeps the physical source row and raw cells. A partner plus order ID is the business key: exact duplicates are suppressed, while every conflicting or invalid variant is held. Region rules select a destination; Central and high-value orders wait for a local approval.
Replay experiment
Choose Northstar, validate, inject an outage, then deliver. Turn the outage off and retry. A stable key and fingerprint produce one simulated delivery; replay produces a visible skip. Change a delivered payload and it is held rather than inherited as a retry.
Failure found in testing
Early versions treated a capped event list as the delivery registry. After enough events, an old successful order could be forgotten. The workbench now keeps a memory-only session registry separate from its 500-event display.
Operational boundary
This demo has no vendors, accounts, storage, network uploads, authentication, or real delivery. It is a local, inspectable simulation.