Description
Compare defensive log timestamps after subtracting a supplied clock offset.
Defensive administrative records connect notices, approvals, owners, policy versions and declared clock conventions. A signed-off label or an active-owner flag describes supplied records rather than granting access or authenticating a control. Clock offsets require an explicit sign and common epoch before timestamps can be compared as an ordered log.
Compare defensive log timestamps after subtracting a supplied clock offset.
When to use this tool
Use Defensive Log Clock Order Pair when you already have firstTimestampSeconds, secondTimestampSeconds, suppliedSecondClockOffset and need to compare defensive log timestamps after subtracting a supplied clock offset.
How to use the tool and how it works
- Enter firstTimestampSeconds, secondTimestampSeconds, suppliedSecondClockOffset. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read normalizedSecondSeconds, signedGapSeconds, ordered. Inspect ordered before interpreting the associated values.
Normalize second=secondTimestampSeconds-suppliedSecondClockOffset; gap=normalizedSecond-first and ordered means gap>=0.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| firstTimestampSeconds | First Timestamp Seconds | Required. Finite number. |
| secondTimestampSeconds | Second Timestamp Seconds | Required. Finite number. |
| suppliedSecondClockOffset | Seconds subtracted from the second timestamp to normalize it to the first clock. | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| normalizedSecondSeconds | Normalized Second Seconds | Required. Finite number. |
| signedGapSeconds | Signed Gap Seconds | Required. Finite number. |
| ordered | Ordered | Required. Boolean. |
{
"input": {
"firstTimestampSeconds": 100,
"secondTimestampSeconds": 115,
"suppliedSecondClockOffset": 5
},
"output": {
"normalizedSecondSeconds": 110,
"signedGapSeconds": 10,
"ordered": true
}
}Limitations and assumptions
- Clock sign and common epoch are caller assumptions; no clock synchronization, event authenticity or causal order is established.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Check original notices, controlled policy versions and current role records when assessing authorship or ownership. For event ordering, reconcile documented clock offsets and timestamp precision against the original logs; this helper does not authenticate or synchronize them.
References
Similar or alternative tools
- Drill Observation Time Precision
Qualify explicit drill observation timestamp text by reported precision.
- Travel Booking Local Time Offset Field
Preserve booking-local time text and its supplied offset label.