Look beyond the moving dot
A demonstration of navigation without satellite signals naturally directs attention to the route: did the vehicle know where it was going? A second question deserves equal space in the report: what supplied the time? Positioning, navigation and timing are grouped together for a reason, but evidence about one function does not automatically establish the resilience of the others.
GPS.gov describes satellite timing as a service used to synchronize communications systems, electricity networks and financial infrastructure. These are civilian examples of dependence on a shared time reference. Their relevance to defense reporting is conceptual: a headline about an alternative position estimate should identify which functions were demonstrated, rather than imply that every connected system has become independent of satellite timing.
Separate the clock from the delivery path
NIST's explanation of one-way time transfer distinguishes the time reference from the signal carrying it. A signal takes time to travel, so a receiver seeking accurate time must account for that delay. The explanation also distinguishes time transfer, which requires knowing the absolute delay, from frequency transfer, for which variations in delay are central.
For readers, the useful lesson is to ask what a quoted performance number measures. Agreement with an external time standard, stability over an interval and continuity of a service are related but different claims. A statement that a clock stayed stable should not silently become a statement that its time was accurate to a particular standard. The announcement needs to name both the quantity and the reference.
Holdover describes a condition
NIST defines holdover as the condition in which a clock has lost its controlling reference and relies on its local oscillator, potentially aided by information acquired earlier. That means a system can continue producing time after losing an external input. The term alone does not specify how long the output remains suitable for a particular application.
A useful public test report would therefore state the interruption's duration and the acceptable timing error, alongside the measured result. It should also explain whether the device was already synchronized before the test began. Those are questions about the evidence, not demands to expose a system's sensitive implementation. An unspecified holdover claim remains an unspecified capability, even when the demonstration itself is credible.
Read the restart condition
A historical experiment makes this distinction tangible. In September 2016, NIST reported research with the US Naval Observatory using commercial fiber networks to transfer time. The experiment met its stability goal while the connection remained intact, but unequal delays in the two directions prevented it from meeting its stated accuracy goal without calibration.
NIST also reported that re-establishing the circuit after a network or power interruption would require GPS or another time reference for recalibration. This was a bounded research result, not a verdict on every fiber timing service. It illustrates why independence during continued operation and independence during startup or recovery should be treated as separate claims. A backup's delivery medium alone cannot establish all of its dependencies.
Ask what the demonstration leaves open
The 2023 revision of NIST's Foundational PNT Profile treats disruption and manipulation as risks to systems using PNT information. That broader framing matters when assessing an announcement: losing an input and accepting an incorrect input are different situations. Evidence from one should not be presented as complete evidence for the other.
Our editorial test is straightforward. Identify the function demonstrated, the reference used to assess it, the period tested and any conditions needed to begin or resume operation. Where the public account is silent, retain the uncertainty. A credible resilience story can be narrow. Its value comes from showing exactly which dependency has been reduced and which questions remain for later evidence.
Sources reviewed on 26 September 2026. The fiber-network example is explicitly a 2016 experiment; the NIST profile cited is its 2023 revision, not a claim about the latest revision. Civilian timing applications illustrate a dependency distinction and are not evidence of any particular military platform's architecture. The proposed reading questions are editorial interpretation.
Read the evidence.
- 01GPS and Telling TimeGPS.gov
- 02One Way GNSS Time TransferNational Institute of Standards and Technology
- 03Holdover — NIST Computer Security Resource Center GlossaryNational Institute of Standards and Technology
- 04NIST and Navy Tests Suggest Telecom Networks Could Back Up GPS Time SignalsNational Institute of Standards and Technology · 8 Sept 2016
- 05Foundational PNT Profile: Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing Services — Revision 1National Institute of Standards and Technology · 31 Jan 2023