Why a single timestamp breaks real-time aggregation

«During volatile moves, the aggregator could show a "consensus" order book that never existed on any exchange at any single instant. The bug: one timestamp field hiding three different "nows", one per venue. I learned th...»