“Which mission functions survive the loss of this node, and which only appear to?”
For armed forces, intelligence agencies and the defense industry, this question reaches someone who has to answer it — and defend the answer when it is challenged. Certainty here means knowing which functions the examined dependencies actually support — not which only appear to survive.
Appearing to survive is not surviving.
The dependencies show the difference.
What SDX contributes. The examined dependencies and the functional limits that follow from them.
Post-incident damage evidence is treated here: evidenced change, separated from assumptions about cause. Kept apart before the decision, not after it.
What you receive.
The finding, as a document.
The finding and the chain that produced it, as a document — with its derivation and its limits. What remains unresolved stays visible.
SDX sources what the question needs. Where the question rests on your own collection, it arrives by agreed handover — never by connection.
Not a function that only appears to survive.
Not an assumption about cause.
Not an AI that decides.
The functional limits that follow from the examined dependencies.
Your sensors, your analytics and your analysts keep their work. The decision remains with human and institutional authority.