# Cross-Domain Validation The same unmodified [[Common Trust Core]] was validated across four independent industrial-control datasets, each a different physical process: | Domain | What it is | | --- | --- | | **SWRO** | Seawater reverse-osmosis desalination | | **WADI** | Water distribution testbed | | **HAI 21.03** | Hardware-in-the-loop control testbed | | **SWaT** | Secure Water Treatment testbed | > [!success] Headline result > The [[Pressure Baseline Drift|R5/R5b]] check separated anomalous from normal behaviour by **1,262×** on SWaT and **1,188×** on HAI — with the *same core*, varying only the [[Profile-Based Portability|site profile]]. The strategic weight of cross-domain validation is that it upgrades the claim from "works on our demo" to "works on the same artefact across four physically distinct systems." On the [[Evidence Hierarchy]] this is strong, reproducible, multi-domain evidence — though still pilot/testbed data, not yet a [[Deployment Path|production enforcement deployment]]. Water-heavy validation also aligns with the [[Integrity Kernel MOC|go-to-market]]: desalination and water utilities are a natural beachhead, especially in [[Sovereign AI Positioning|GCC critical infrastructure]]. --- Related: [[Integrity Kernel MOC]] · [[Common Trust Core]] · [[Profile-Based Portability]] · [[Pressure Baseline Drift]] · [[Evidence Hierarchy]] · [[Sovereign AI Positioning]]