This sounds trickier than it is: the Router is
breaking its own design right now be firing
installation events during the subscriber inquiries.
The router has always assumed that events would only
be fired to "subscribers" but, like in the case of the
InstallationEvent, there are a number of event
categories that are subscriberless... the router
should have a method to deal with all these when the
subscriber identification logic yields nothing.