Same symptom. Different cause.
Confidence drops while delivery looks normal
False MotionVector Lantern
Same confidence drop. The measurements may still be good.
Fusion confidence falls if a bad label stays in, even though the values themselves are usable.
DEMONSTRATION SCENARIO
This is a demonstration scenario. It is not a live demonstration and does not report an executed result.
Several sources feed one track. Delivery is healthy. Values from the suspect source still look physically usable.
Confidence falls. Delivery stays normal. The screen matches False Motion.
The same confidence loss can be a skewed source time, a maneuver the catalog missed, a policy change, or a navigation fault. Rewriting time and updating the catalog are not interchangeable.
Rewriting timestamps, or rolling back policy, should not count until the distinction says which fault is real.
V8Y must distinguish a bad time label, a missed maneuver, a policy change, and a navigation fault. Those repairs are not interchangeable.
Confidence keeps falling if that source stays in the fusion.
Not recovery
Success is not a rewritten clock or a policy change.
Recovery
Success is that uncertainty recovers, the policy stays unchanged, and the raw measurements are kept.
Observed results
No executed results are published for this thread.
These are the conditions the evaluation would test. They are not reported results.
A synthetic demonstration of this confidence loss, paired with False Motion so the two readings can be told apart. It is not a reconstruction of a navigation-deception event.
Same symptom. Different cause.
Confidence drops while delivery looks normal
False MotionCompare with False Motion. The two readings are not interchangeable.
Does your environment face a similar problem?
The request keeps this mission and thread. It is not a claim that the demonstration has been validated in your environment.
The printable flyer is being revised and is not available for download.