Yes, that is exactly the distinction I was trying to make.
Two events may share the same UTC instant, but that does not make them the same persisted event record. In KDS terms, the timestamp is part of the record context, while the event identity is derived from a broader canonical record context that includes source identity, source event key, payload hash, edition, and projection/replay context.
So the intent is not to redefine UTC ordering, but to formalize what makes a preserved event record stable and distinguishable across later projections.
Kind regards,
Dragan Škondrić
On May 26, 2026, at 3:23 PM, Dragan Škondrić via tz <tz@iana.org> wrote:
> A timestamp identifies an instant.
> A KDS event identity identifies a persisted event record.
>
> In other words, the timestamp remains one component of the record, but it is not the whole identity of the preserved event.
E.g., two people may have been born at the same UTC time, but they're two different people (even if they're identical twins), so the two births are two separate events,