since, by definition, the Nexus is "the" up-link, all we need is clever overriding of the relevant handling functions, so the nexus will care for the routing, while the CoreService cares for command and presentation state handling
- front-end handle - Nexus == routing hub - CoreService == service access point for command invocation
...especially since we need a faked UI backbone for unit testing
