How should uncertain event order be reported?¶

State the order as uncertain or partial rather than forcing a precise sequence. Equal timestamp precision, unaligned clocks and different event stages can prevent a reliable first-versus-second conclusion.

Technical dependency may establish only partial order¶

Sequence numbers, process ancestry, request-response links and transaction stages can show that one operation is upstream of another even when their displayed times match or appear reversed. The exact interval may remain unknown.

Source ordering also needs definition: it may reflect event creation, file writing or ingestion rather than real-world chronology.

Use wording that matches the support¶

Phrases such as “within the same recorded second”, “by this point” or “the records do not establish which occurred first” preserve the limit. Show materially different possible sequences and identify evidence that could resolve them.

Do not manufacture milliseconds or reorder equal values. If sequence affects causation, attribution or an alibi, carry the uncertainty into the main conclusion rather than hiding it in technical notes.