Notification-Oriented Paradigm (PON) in Elixir: why the BEAM fits reactive rules

Notification-Oriented Paradigm (PON) in Elixir: why the BEAM fits reactive rules Part 1 of 12 — This series documents a proof-of-concept Notification-Oriented Paradigm (PON) engine in Elixir, a hexagonal boundary around it, and a Smart Brewery digital twin used as a stress lab (simulation, LiveView, telemetry, TimescaleDB, and ML hooks). Here we set the vocabulary and motivation; later posts walk through OTP wiring, the metaprogrammed DSL, the brewery case study, and hard-won performance lessons. Industrial software, building automation, and operations dashboards all share a pattern: when the world changes, something should happen—open a valve, raise an alarm, enqueue a job, or just refresh a score. You can implement that as a big imperative script, a rules engine, or a graph of small reactive pieces. The Notification-Oriented Paradigm (PON) takes the last path: facts hold state, rules react when relevant facts change, and work propagates by notifications rather than by constantly re-s