Which of these actually happened first SKEW
A phone crosses a border. A laptop is four minutes fast. A recorder never had its clock set. Sort those three by the time column and the order you get is fiction.
The devices
The declared zone is what the device says its times are in, which is a separate fact from whether the clock is right. The tick is the smallest unit it records: a recorder that writes whole minutes cannot tell you anything finer, and that limit is carried through to every answer.
The anchors
An anchor is one real event that two devices both recorded: a call in the handset log and in the switch record, a person through a door on the access system and on the camera. One anchor fixes the difference between two clocks exactly; a chain of them reaches everything the chain touches, and nothing else.
The events
The clocks, solved
Whether the anchors agree
What changed
The timeline, corrected
The working
How it works
Sort their events by time and the order can be wrong. SKEW corrects each device using anchors, events that two devices both recorded, estimates drift, and reports which events changed order and which pairs are too close to separate. The timeline data stays in this tab.
Questions people ask about SKEW
What is an anchor?
One real event that two devices both recorded. A call that is in the handset log and in the switch record. A person going through a door that is on the access system and on the camera. Because it is one instant seen twice, the difference between the two readings is the difference between the two clocks, exactly, with nothing to estimate.
What happens to a device with no anchor?
It is named and left out. A clock nothing pins has times that mean nothing relative to the others, and sorting it into the list anyway is the exact error this page exists to prevent. Finding one event that device shares with another is usually easy once you know that is what is needed.
Why does it matter which events changed order?
Because that is usually the case. Two things that looked sequential turn out not to be, or turn out to be the other way round, and a timeline built by sorting a spreadsheet column had them wrong. Those pairs are listed on their own rather than left to be spotted in a long table.
Why report pairs that cannot be separated?
Because saying so is a finding and guessing is not. Clocks have a tick and anchors have a residual, so every corrected time has a band around it. Where two bands overlap, the order of those two events cannot be stated from this evidence, and stating it anyway is how a timeline comes apart under cross-examination.
What is the drift figure?
Where two anchors join the same pair of clocks at different times and disagree, the disagreement is a rate. The page reports it in seconds a day and carries the residual into the uncertainty on every event from those devices, rather than averaging it into silence.
Doing this often? OBSCURA Case builds the chronology from the documents themselves, each event pinned to its source. Everything is US$5 a month or US$48 a year.