Rules Engine & Event Viewer

We're looking for a talented architect / developer to pull together a prototype solution. Essentially this will be a rules engine taking data from multiple data stores, analysing the data based on rules we configure and outputting that result to a push service so it can be consumed by multiple client types e.g. email, http, mobile, dashboards etc. Essentially we are looking to build an 'if this than that' type infrastructure. For example, our customers will have many off the shelf and bespoke systems running in their business, all of which contain significant data. We would like to consume and merge specific bits of that data and notify a user if a particular event has occurred. The [login to view URL] attached shows AWS as the main architectural framework but we are open to using any technology. However, we would like the configuration of a new 'rule' or 'event' to be somewhat trivial i.e. a junior / mid level engineer would be capable of doing it. Therefore the following components should be easy to swap in and out of the framework; - A new customer data store - be it a web service or direct database connection - A new rule or event class. Shown above as an AWS lambda but again we are open to any architecture. These "rule classes" should consume specific data from the customer data sources and hold the core logic to determine whether a notification is necessary - shown in the diagram as examples ([login to view URL] > [login to view URL] then notify) - A new notification consumer. Onboarding a new customer must be straight forward. So, at a minimum setting up a new email address or a new dashboard to display their events must be trivial (Again we are open to using any dashboard platform). Finally - there's a sequence diagram attached to indicate high level work flow ([login to view URL]). Please Note* - Excellent English is a requirement - We would like to think a solution exists using mostly off the shelf components