A visit’s identity is minted by the console and its attribution by the server

Context

A navigation report may be delivered repeatedly over an unreliable connection.

Decision

Let the client identify the occurrence and the server establish attribution. Resolve the target under current authority before inserting or returning a duplicate.

Alternatives Considered

Person-and-record matching loses later visits. Client-supplied attribution cannot provide a trustworthy server account.

Consequences

Occurrence identity makes retransmission repeatable without letting clients choose the event’s author.