🗳️Proposal Template
Use the following template when creating proposals. Be sure to choose a short, action-oriented proposal title - e.g., “Strengthening $CTRL Utility” or “Platform Listing Overhaul”.
Summary
A concise overview (3–4 sentences) describing the purpose of this proposal and the main changes being suggested. This should read like an executive snapshot for busy voters.
Rationale
Explain why this proposal is needed.
Reference community feedback, current challenges, or opportunities
Align reasoning with AltCTRL’s core values (Safety, Empowerment, Innovation, Community)
Show how this proposal strengthens long-term growth, adoption, and user safety
Proposed Changes
List the specific changes being suggested. Break them into clear points (numbered or bulleted). Example structure:
[Change Area]
Describe what will change
[Change Area]
Describe the new rule, system, or feature
[Change Area]
Clarify any integration with $CTRL utility, governance, or platform tools
Implementation Plan
Detail the steps needed to execute if approved:
Phases 1 (Design): Define...
Phases 2 (Development): Build...
Phases 3 (Launch): Announce...
Timeline: 90 days post-approval
Communication: Docs updates, AMAs, explainer video, etc.
Expected Outcomes
Highlight key benefits with checkmarks for clarity ✅
✅ Increased [engagement / safety / utility]
✅ Strengthened community participation
✅ Improved $CTRL demand and retention
✅ Enhanced trust and platform adoption
Voting Options
For: Approve the proposal and begin implementation
Against: Reject the proposal and maintain current system
Abstain: You neither support nor oppose the proposal (still counts toward quorum)
Call to Action
A motivational closing paragraph that speaks directly to the community.
Encourage participation: “Your vote helps shape AltCTRL’s future”
Reinforce alignment with the mission: safety, empowerment, and innovation
Keep it approachable and engaging, in line with brand voice
Last updated