Governance · proposed

Community governance

Governing principle

If the movement only survives while its originator drives every change, it contradicts the freedom to continue. Community stewardship should be explicit, shareable, accountable and forkable.

Founding open debate

Before soliciting badges or celebratory endorsements, invite participants to break the charter. Create a public issue category: What Would Make This Fail? Capture objections, tradeoffs and respectful dissent as first-class contributions. Credit critique that improves the standard.

Proposed open debate prompts:

1. Is this substantively new, or open source with pirate branding?
2. Can a public-domain ideal coexist with contribution attribution, trademark and patent rights?
3. What does genuine data ownership mean for collaborative, organizational or publicly replicated records?
4. Where does full process disclosure end to protect secrets, privacy, security and third-party rights?
5. Can labor, taxes, reserves and risk be honestly represented in cost-based pricing?
6. Who audits the auditors, conformance badges and costs?
7. Could a project comply technically while using coercive or abusive hosted-service terms?
8. Can smaller maintainers participate without onerous documentation overhead?
9. What should survive a protocol or cloud provider disappearing?
10. Would a competing fork have the right to continue the movement's symbols and specification?

Proposed governance

• Publish a public specification change process and decision record; revisions are versioned, never silently rewritten.
• Give contributors a right to propose, discuss, translate, red-team, test and fork, regardless of code expertise.
• Maintain respectful contribution standards with a published moderation/appeal procedure.
• Keep critical governance, releases, credentials and finance access distributed among multiple maintainers; separate public openness from private access credentials.
• Require independent approval for high-impact standard changes; document rationale, objections and dissenting alternatives.
• Build a succession procedure, access-recovery policy, and handoff playbook so a new maintainer can continue the project.
• Do not claim to have a decentralized governance mechanism before it exists.

A voluntary flag, not a monopoly

An optional movement emblem could be useful for discovery, but the right to use the software or apply the open spec must not depend on approval, fee or membership. If accuracy requires controls around a compliance mark, separate those from open content/code rights and establish fair, accountable governance. Naming/trademark clearance remains outstanding.

Contribution credits

Value documentation, careful critique, a repaired deployment, translated material, security fixes, independent reproduction, cost reductions and human support alongside code. Attribution is culturally important even when no enforceable attribution duty is imposed by public-domain dedication.

Community structure

Start with a public repository, issues, pull requests and an open contributor forum. Consider independent maintainers and rotating working groups for legal, protocol, security, economics and communications. Evaluate fiscal sponsorship only if funds or legal administration become necessary.