Community
Local or usage-level scope. Quorum 25%, simple majority > 50%. Voting ≥ 5 days.
Governance · Proposals
Any major platform evolution proposal goes through the community. Pricing, geographic expansion, partnerships: if it affects athletes, it goes to vote.
Author writes: title, problem, proposed solution, estimated impact, dismissed alternatives. Proposal stays private until submission.
The proposal enters the voting phase after review. Minimum duration by category: community ≥ 5 days, operational ≥ 7 days, strategic ≥ 14 days.
Required quorum on the active electorate: 25% for community, 40% for operational, 60% for strategic. Weighted real-time count.
Adopted if quorum reached AND required majority met — 2/3 supermajority for strategic, simple majority > 50% for operational and community. Otherwise rejected or expired. Immutable append-only trace.
Adopted decisions are implemented by the technical team with a public schedule. Tracked via the Governance banner.
Local or usage-level scope. Quorum 25%, simple majority > 50%. Voting ≥ 5 days.
Operational changes: pricing, expansion, partner integrations. Quorum 40%, simple majority > 50%. Voting ≥ 7 days.
Structural decisions: business model, governance rules, major partnerships. Quorum 60%, 2/3 supermajority. Voting ≥ 14 days.
The team can decide in urgency (security breach, legal compliance) then submit for a posteriori ratification. Mandatory public trace.