For armed forces, intelligence agencies and the defense industry, every requirement reaches someone who has to answer it — and defend the answer when it is challenged. These are the shapes SDX Defense is built to take: what is tasked, and what reaches the brief.
Each is the shape of a mandate: a question you bring, with its derivation and its limits as the answer. Your sensors, your analytics and your analysts keep their work. The derivation is the step that is added.
“Does the collect support the conclusion that this position was reoccupied — and what else would produce the same signature?”
What SDX contributes. Released UAS collect evaluated against a defined requirement, drawing on further suitable evidence where available. Delivered: a bounded finding on what changed, with its derivation and the explanations it leaves open.
Outside the scope. SDX does not operate or task drones.
“Which statements about a hardened or underground facility does the available evidence support, and which explanations remain open?”
What SDX contributes. Observed change, supported explanation and unsupported extension are kept apart.
The modelled scenario on the home page shows this shape of finding. Modelled scenario · synthetic values · not a run output.
“Does the observed pattern support sustained buildup, or is it consistent with routine rotation?”
What SDX contributes. A defined change requirement evaluated against the released collection.
Evidenced change stays separable from assumptions about capacity, use and intent.
“Does the evidence support that this formation moved — or only that equipment of this type was seen in both locations?”
What SDX contributes. The observations evaluated against a stated movement hypothesis. What the evidence supports about identity, continuity and timing stays separable from what remains assumption.
Outside the scope. No unit identification from signature alone, no tracking, and no prediction of destination or intent.
“Which readiness statements can we declare up the chain — and defend when the inspection asks for the basis?”
What SDX contributes. A reproducible evidence state against explicitly agreed technical criteria. Evidenced, assumed and unverified preconditions stay distinguishable.
Outside the scope. Not an operational release.
“Do these paths stay independent when one bearer is denied — or do they collapse onto a single point?”
What SDX contributes. Provided test and configuration data evaluated together against a defined independence criterion under stated denial conditions. Delivered: one traceable finding instead of isolated test results.
Outside the scope. SDX evaluates the evidence you hold. It does not generate the denial condition and does not test the equipment.
“Which mission functions survive the loss of this node, and which only appear to?”
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.
“What does the evidence support about this incident — and where does it stop short of attribution?”
What SDX contributes. Change, possible cause and responsibility are kept explicitly apart.
Outside the scope. No automatic attribution to a vessel, an organization or a state.
“Which agreed technical states or changes are evidenced by the released observation and inspection data?”
What SDX contributes. A verifiable technical contribution to a verification task.
Outside the scope. Not a confirmation of full treaty compliance, and no replacement for the responsible institutional assessment.
Start with an abstract description. Together we define where a deterministic evidence layer could contribute and what a credible test must demonstrate. The decision remains with human and institutional authority.