My suggestion is to bin this proposal, and have a SocialCG meeting with actual mainline projects present to define explicit goals, boundaries and responsibilities. And then, and only then, with consensus from mainline developers, write up a policy proposal.
If this policy proposal comes into force on 9 Feburary, then I will be forced to no longer participate here, as I cannot agree to this as presently worded, and do not see a path forward for rewording it that does not involve having actual discussions with the community at large including major stakeholders.
I can’t speak for other developers, but I suspect you’ll have effectively killed SocialCG if things move forward without that.
Nobody who takes this stuff seriously is going to waste time contributing to a technical community they can be banned from at any time because the wrong people deployed the software. Instead, interoperability discussion will return to backroom discussion and alternative working groups like Litepub. Sorry, but it’s just reality.