# Agnostic Engine The Agnostic Engine (**ACE**) is the layer that makes one fixed [[Common Trust Core|kernel]] work across physically different industries. It holds a set of **adapters** — one per domain (water, gas, oil, chemical) and, within a plant, per asset class (compressors, pipelines, processing units, etc.). > [!abstract] Where it sits in the data path > `telemetry in → Adapter (ACE) → Common Trust Core → trust state` > The adapter sits **between** the raw telemetry stream and the kernel. It normalises and translates incoming signals into the form the kernel expects, and injects the domain's physical laws. This is the practical mechanism behind [[Profile-Based Portability]]: the kernel never changes, the adapter does. Standing up a new industry — or a new asset inside an existing plant — is an adapter exercise, not a kernel rewrite. > [!example] Why tuning matters: the SWaT unit bug > The early SWaT run showed a high false-positive rate (the ~5.9% sensor-coverage case). The cause was not a kernel failure — it was a **unit mismatch**: the data carried pressure in bar while the kernel expected Pascal. Adding the bar↔Pascal conversion in the adapter fixed the result. This is exactly the per-domain calibration a [[Deployment Path|pilot]] exists to do, and why public datasets alone can't finish the job: "what works for seawater doesn't work for wastewater." Note on maturity: the engine and adapters exist in design, but their per-industry **tuning** is the unvalidated part — see [[Unvalidated Components]]. The adapter concept is what lets the founder describe IK as covering "almost every industry." --- Related: [[Integrity Kernel MOC]] · [[Common Trust Core]] · [[Profile-Based Portability]] · [[Cross-Domain Validation]] · [[Unvalidated Components]] · [[Deployment Path]]