This is not much of a proposal per se, mostly just a brain storm:
The initial idea was to "flip/flop" KEW to utilize a KEN service API for notification and action list (move KEW action list functionality into KEN) but at the f2f I think we decided instead to move KEN functionality (e.g. message deliverer plugins) into KEW, under the ActionRequest or a "communication broker" service, and expose this as a first class service on the bus which can be used by arbitrary applications.
I am just starting to look at this again. Any comments/ideas would be appreciated.