there is a small problem with it that it requires some consistency in the event records though... any garbage collection scheme for event data would need to respect the connection between delegations and acting in the name of events 

 oh yeah another tricky one, so, the identifier, is it a pubkey, and someone has the secret, or does its authorised representatives solely make event references that designate an npub to be representative (or remove them), and then you have at least 3 levels - the owner, who first registers the name, do they have extra privileges to add and remove designated npubs? or even cancel the registration, and if not, then you need some scheme of administrators for the name versus simple representatives

it can all be done but it essentially amounts to an access control list

it could be interesting to actually formalise the concept of access control lists altogether, as tehy can have private-to-relay meaning as well as representatives and even company hierarchy trees 

 also note that this is exactly the same engineering problem as DNS 

 I believe that this can be achieved in different ways. The determining factor will be the design you want to implement. Right now, at a high level, I see two possible approaches.

One is an interactive process, where note sharing, validation, and publication are done by humans without relying on extra servers, just relays. This process can be enhanced by using off-band communication and NIP46.

The other approach is non-interactive, where the process is delegated to a server that has all the necessary information. In this scenario, if an authorized npub sends an event to the server (which could be a dvm), the server will publish it under the npub of the company.