i think the goal is similar, but a separation is needed.

voicy, as it comes across is good for app specific functionality. it is by definition easier to implement functionality for a given app because you know what that app can do. app devs could include a config/description file with their app to add support.

saera tries to be siri. in this case it's role should be to interpret what you want and decide what to launch. this comes down to lexical analysis (i think thats the right term), trying to work out what the user wants to do. take a weather query, it needs to detect what, where and when and pass this on to app or voicy to execute request.