SDX DEFENSE Discuss your first use case
KnowledgeSDX Defense

Nine questions.

One executable derivation.

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.

01–04 / 09Use cases

Adversary activity.

01 / 09Adversary activity

Drone reconnaissance

“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.

02 / 09Adversary activity

Subsurface facility assessment

“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.

03 / 09Adversary activity

Force buildup

“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.

04 / 09Adversary activity

Troop movement

“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.

05–07 / 09Use cases

Readiness under contest.

05 / 09Readiness under contest

Platform readiness

“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.

06 / 09Readiness under contest

Communications resilience

“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.

07 / 09Readiness under contest

Mission continuity

“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.

08–09 / 09Use cases

Attribution & verification.

08 / 09Attribution & verification

Maritime infrastructure incident

“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.

09 / 09Attribution & verification

Arms control verification support

“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.

Bring one unclassified intelligence question.

Not a sensitive dataset.

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.

Legal Notice / Privacy

1. Data controller and website operator
SDX Defense is operated by Scalarfield Dynamics S.r.l. (in formation).

Scalarfield Dynamics S.r.l.
Via San Martino 72
84050 Laureana Cilento, Italy

Represented by its shareholders:
Marcello Raffaele Avagliano
Prof. Dr. Sascha Kreiskott

Method and scientific review

Marcello Raffaele Avagliano — Founder, Managing Director and Method Architect
Conceived and developed the SDX methodology.
Deterministic mathematical modelling · Evidence-chain architecture · Algorithm design · Statistical inference · Reproducible analytical methods · Software architecture · Institutional governance

Prof. Dr. Sascha Kreiskott — Co-Founder and Scientific Reviewer
Reviews and challenges assumptions, methods and findings.
Scientific review · Methodological challenge · Scientific reproducibility · Experimental physics · Data protection · Technology governance

Contact: info@sdx-defense.com

2. Categories of personal data processed
a) Server log data: IP address, browser user-agent, timestamp, requested resource. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in operating and securing the website). Retention: maximum 30 days, then deletion or aggregation.
b) Email correspondence: any data voluntarily provided when contacting info@sdx-defense.com. Legal basis: Art. 6(1)(b) GDPR (pre-contractual measures) or Art. 6(1)(f) GDPR (legitimate interest in responding to inquiries). Retention: as long as necessary for the inquiry, then archived for 24 months in line with standard business correspondence practice.

3. Recipients
No personal data is shared with third parties except as required by law, as necessary for hosting infrastructure, or as set out in this section. The hosting provider acts as data processor under Art. 28 GDPR.

This website displays a compliance badge whose image file is retrieved from eab-compliance.eu, operated by EAB Compliance (European AI Bureau), established in the European Union. When a page is loaded, your IP address, browser user-agent, referring URL and the time of the request are transmitted to that server and processed there under its own responsibility. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in displaying the compliance programme this website participates in). Apart from this, no content is loaded from third parties.

4. International transfers
No personal data is transferred outside the EEA. Should service providers operate outside the EEA in the future, transfers will occur under Standard Contractual Clauses approved by the European Commission.

5. Cookies
This website does not deploy cookies. No analytics, advertising, or third-party tracking technologies are used. The compliance badge described in section 3 is a static image; it is not embedded for analytics or tracking purposes.

6. Rights of the data subject
Under Art. 15–22 GDPR you have the right to access, rectification, erasure, restriction, data portability, and objection. Requests may be sent to info@sdx-defense.com.

7. Right to lodge a complaint
You have the right to lodge a complaint with the Garante per la Protezione dei Dati Personali (www.garanteprivacy.it).

8. Changes
This policy will be updated as the legal structure of Scalarfield Dynamics S.r.l. evolves.