Independent technical note defines a stateless ECA rule engine, suggesting a universal framework for rule selection.
This note defines a stateless ECA rule engine as a pure mathematical action-selection function. An event occurrence consists of an event type and an optional payload. Payloads and condition sets are finite typed partial maps that distinguish a concrete value, an explicit null, and an absent key. A condition-side null is an explicit wildcard, whereas a payload-side null is a present null value. The query retains the matching rules of greatest specificity, resolves any tie with a fixed deterministic selector, and returns one action or the no-action value ⊥. Specificity assigns weight two to a concrete condition, one to an explicit-null wildcard, and zero to an omitted key. The score is defined for every condition set and compared only among rules that fully match the current payload. The engine is stateless because, for a fixed rule base and tie selector, its result depends only on the current event occurrence. Event types, parameter domains, conditions, and actions remain otherwise uninterpreted, making the model independent of any application domain or implementation technology. Status: Independent technical note; not peer-reviewed. Companion implementation: 10.5281/zenodo.21802923Interactive demonstration: https://rohingosling.github.io/eca-rule-engine-2/
No takes yet. Share an insight, caveat, or question.
Rohin Gosling (2026) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: