Hostile Environment Twin
Deterministic Scenario Twin for Hostile Vectors
Drone operators in contested or hazardous environments need to evaluate mission viability against compound hostile scenarios before committing assets. The SHET engine (M228) models ten hostile vector kinds — WIND_GUST, WEATHER_DEGRADATION, JAMMER_ACTIVATION, SPOOF_INJECTION, BVLOS_LINK_LOSS, GEOFENCE_BREACH_ATTEMPT, VARROA_SURGE, PEST_OUTBREAK, STRUCTURAL_DEFORMATION, THERMAL_SENSOR_FAILURE — and computes a deterministic risk score and mission continuability verdict using transparent domain-weighted arithmetic.
Capability specification
- 01
Ten hostile vector kinds covering environmental, electronic warfare, biological, and structural threats
- 02
Per-sector domain impact: each vector kind carries declared weights per operational domain
- 03
Risk score = mean of domain impacts, clamped to [0, 1]
- 04
Mission continuability: NOT veto AND risk below 0.75; empty vectors yield 0.0 risk and continuable=True
- 05
Veto emission: any vector with domain impact >= 0.50 triggers mission veto
- 06
49-test green suite covering boundary conditions, veto logic, and KURAL 23 data constraints
How it works
Scenario Composition
An operator composes a hostile scenario by selecting one or more vector kinds and assigning intensity values in [0, 1]. The scenario is KSL-signed and submitted to the twin engine.
Deterministic Outcome Computation
For each vector, domain impact is computed as intensity × domain_weight, clamped to [0, 1]. Risk score is the mean of all domain impacts. A veto is emitted if any single domain impact reaches 0.50.
Continuability Verdict
Mission continuability is True only when no veto has been emitted AND the overall risk score is below 0.75. The verdict, risk score, veto flag, and per-vector impacts are written to the chain-hashed outcome ledger.
Standards we follow
- STD-01
ICAO Annex 19 — Safety Management Systems (risk assessment alignment)
- STD-02
EASA Wind Limitation standards (WIND_GUST vector reference)
- STD-03
WHO PAHO Integrated Pest Management guidelines (VARROA_SURGE, PEST_OUTBREAK vector reference)
- STD-04
NIST FIPS 180-4 — Secure Hash Standard (outcome chain hash, SHA-256)
Areas served
This capability is deployed across 14 operational regions. Regulatory alignment details vary by jurisdiction — consult engineering for jurisdiction-specific deployment guidance.
Frequently asked questions
Does the hostile twin engine issue countermeasures against jamming or spoofing?
No. The SHET engine models scenario outcomes deterministically — it does not issue electronic countermeasures, activate jamming responses, or direct any offensive action. This is a structural constraint enforced by KURAL 16 (white-hat only). The engine produces a risk verdict and veto flag; autonomous defence responses, if any, are delegated to the LSIA immunity engine and the operator.
What does empty hostile vectors mean in the model?
When a scenario is composed with no hostile vectors, the risk score is exactly 0.0 and mission continuability is True. This boundary condition is enforced by the engine and verified by test. It represents a baseline scenario with no modelled threat vectors — not an assertion that no real-world threats exist.
Talk to engineering
For capability evaluation, integration guidance, and deployment scoping, submit a brief to the engineering team.
Submit engineering brief