Glad it resonates with you @nick.eth
Are you suggesting that a ‘centralized’ Registrar be created that will take care of automatically setting forward resolutions (i.e. the next version and the ‘latest’ tag) when a contract is deployed?
For example, with a name like `42.enscribe.contract.eth`, the `contract.eth` 2ld needs to centralized so that only the correct org owner can register their org’s subname.
What is also important is figuring how the orgs will prove the ownership of the contract irrespective of whether the contract is `Ownable` or not. This is because we want this Versioning Registrar to work for all the contracts without anyone trying to game the system (like tag a wrong contract under their org)