Description
Restore an active-time exercise marker across one removed pause; affinity selects the wall-clock side of the collapsed pause.
Security records often depend on explicit counts, clock origins, status flags, and provenance dates. Checking their internal arithmetic can reveal a bookkeeping gap while leaving the underlying evidence and operational decisions for separate review.
Restore an active-time exercise marker across one removed pause; affinity selects the wall-clock side of the collapsed pause.
When to use this tool
Use it for drill inject marker clock affinity when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter markerTime, pauseStart, pauseEnd, affinity. Use the stated units and boundary conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read adjustedTime. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Restore a marker from active time to a wall-clock axis with one removed pause. Keep markers before pauseStart unchanged, add pause duration to later markers, and map an exact-boundary marker to pauseStart or pauseEnd according to affinity.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| markerTime | Marker Time | Required. Finite number. |
| pauseStart | Pause Start | Required. Finite number. |
| pauseEnd | Pause End | Required. Finite number. |
| affinity | Affinity | Required. Text; one of "before", "after"; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| adjustedTime | Adjusted Time | Required. Finite number. |
{
"input": {
"markerTime": 10,
"pauseStart": 10,
"pauseEnd": 20,
"affinity": "before"
},
"output": {
"adjustedTime": 10
}
}Limitations and assumptions
- This is an explicit collapsed-pause convention, not a generic timestamp correction. pauseEnd must not precede pauseStart and affinity must be before or after.
- The field tables describe structural bounds; the mechanics also state cross-field requirements. Malformed input shapes, disallowed keys, and invalid domains cause input errors. Results must remain finite and within the declared output contract. A successful false flag or zero placeholder is distinct from an error.
- Numeric arithmetic uses binary floating point. Exact comparisons have no hidden tolerance or decimal rounding; negative zero is exported as zero. Decimal-text integer operations retain the exactness specifically stated above.
Alternative or Complementary methods
For drill inject marker clock affinity, check the source records and the supplied rule before comparing the result with another method. Use a separate evidence or method review when arithmetic consistency alone cannot establish the required conclusion.
References
Similar or alternative tools
- Protective Drill Role Count Gap
Compare supplied nonoperational drill role counts with an explicit target.
- Advisory Publication Lag
Compare supplied public advisory timestamps without evaluating threats or recommending operational action.