Card rules · 2026-10-29
The Same Displayed Second Does Not Prove Simultaneous Actions
Two devices can display 10:00:01 for different events. If the display records only whole seconds, it cannot establish the finer ordering within that second.
Two devices can display 10:00:01 for different events. If the display records only whole seconds, it cannot establish the finer ordering within that second.
Which clock is relevant?
A rule might use an acceptance sequence rather than a device's displayed time. Another teaching procedure might recognise a defined simultaneous window. These are different ordering models. Neither should be invented after looking at which participant benefits.
Also distinguish sending from receipt and acceptance. A message sent first need not appear first on every screen. Without the required record, the correct description may simply be that the visible timestamps cannot resolve the order.
What a fair explanation preserves
Keep both action identifiers, their recorded statuses and the precision of the available times. If the rules supply a tie-handling procedure, explain it as written. Do not add an unofficial advantage based on a participant's name, screen position or local display order.
Two whole-second labels cannot settle the finer ordering of events inside that second. Use the accepted event order when it is available. Without it, the matching labels leave the order unresolved rather than proving a tie.
Precision can hide a real gap
Events recorded at 10:00:01.100 and 10:00:01.900 differ by 0.800 seconds. A whole-second display can show both as 10:00:01. If the detailed records are unavailable, do not invent those decimal values; this example only demonstrates why identical coarse labels do not establish equality. The accepted ordering still needs the relevant event record.