I like it, and I think the closest approach we currently have is nostrhub.io and the 'nip' spec: nostr:naddr1qvzqqqrcvypzqprpljlvcnpnw3pejvkkhrc3y6wvmd7vjuad0fg2ud3dky66gaxaqqxku6tswvkk7m3ddehhxarjqk4nmy. However, I think it is not a complete solution since it lacks the some consensus feature, which is needed for interoperability and clarity, where multiple people come up with specs for the same case but with slightly different approaches or kind numbering, leading to competing, and fragmented specs that are practically the same, and it's not clear which path to follow

I think the potential of Nostr to overcome this issue is huge, given its fatures. The Nostr protocol and NIPs can be hosted on a specific relay, such as 'relay.nostr.com,' and all the official NIPs can be hosted there. Additionally, I've found that other open protocols like MCP have a well-thought-out document on how to contribute to the protocol, called 'SEP.' This is interesting because MCP is being used by many companies, and managing the governance of it must be clear. I think we can draw some inspiration from their proposal and adapt it to benefit from Nostr's features.

Here is the link for reference: https://modelcontextprotocol.io/community/sep-guidelines