The Rule Loader keeps the Rule Evaluator fed with the right rules. The cloud authors and versions rule packs; the loader fetches them, validates and compiles them to WASM, and swaps them in live — without ever leaving the runtime without a working rule set.
Hot reload, never a gap
Reloads are atomic: a new pack is fully compiled and validated before it becomes active. If validation fails, the current pack stays in force and the failure is reported — the gateway is never left rule-less.
On a pushed version notification (or periodic check), the loader downloads the new rule pack and verifies its integrity.
Rules are compiled to a sandboxed WASM module and checked against the actuator capability manifest — a rule may only reference actuators the gateway actually exposes.
The compiled module replaces the active one between evaluation ticks, so no in-flight evaluation is interrupted and no input sample is dropped.
Versioning
Each active pack carries a version stamp that is reported up with telemetry, so the cloud always knows exactly which rule logic a given device is running.