Signal Anchor
Fading Link
The link still shows up. The mission traffic does not.
Command and reconnaissance tempo slip while the terminal still looks registered.
DEMONSTRATION SCENARIO
This is a demonstration scenario. It is not a live demonstration and does not report an executed result.
The situation
A satellite terminal is associated. Voice, video, and lighter traffic have all been usable.
The link stays up. Higher-rate mission traffic fails first. Lighter traffic may still move.
Why this is hard
A link that stays up can be a graded loss of service, a hard outage, a terminal wipe, or a payload fault. A modem that says up is not recovery.
Accepting modem-up, or restarting a healthy payload, should not count as restoring the mission class.
What the operator can see
- NormalTerminal associated
- VisibleHeavy traffic fails
- At riskMission class slips
What V8Y must determine
V8Y must distinguish graded bearer loss from a hard outage, a terminal wipe, and a payload fault, and judge recovery by the mission class of traffic.
What may happen next
If quality keeps falling, the mission class breaches while the terminal is still associated.
What counts as recovery
Not recovery
Success is not a modem that still says up.
Recovery
Success is that the mission’s own class of traffic meets its requirement.
Observed results
No executed results are published for this thread.
What this evaluation would test
- Graded loss, a hard outage, and a dead terminal kept apart.
- Heavier traffic failing before lighter traffic.
- Modem-up rejected as recovery.
- A payload fault kept as its own reading.
These are the conditions the evaluation would test. They are not reported results.
Operational basis
View operational basis and sources
Grounded in field reporting from the May 2024 Kharkiv fighting, where heavier satellite uses failed before lighter ones. Numeric thresholds here are synthetic. This is not a terminal-wipe incident.
Related threads
Compare with The Path, where the required flows fail together rather than by class.
Discuss evaluating this situation
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.