How Governance Works

Proposal → vote → PR

1. Anyone proposes a change in Discord — new server, site copy, a policy note.
2. Compliance pre-check. Anything touching money, donations, deposits, or the Bohemia disclaimer is checked against our locked rules first. Violations are dead on arrival — no vote can approve them.
3. The community votes with emoji: ✅ approve · ❌ reject · 🤷 abstain.
4. Quorum + majority decides. See the thresholds below.
5. Founder override / veto can stop anything, always.
6. Audited action. On approval the AI maintainer opens a feature branch → PR; the founder merges. Discord fills the queue; it never merges or spends.

The current vote rules

• Who can vote: verified members whose account is at least 7 days old (blocks throwaway sockpuppets).
• Quorum: at least 3 eligible ✅/❌ ballots, or the proposal fails as “no quorum.”
• Threshold: a simple majority of non-abstain ballots (ties fail — the status quo wins).
• Voting window: 48 hours.

What a vote can (and can't) do

The AI maintainer will only ever queue actions on this allow-list — and only the enabled ones. Financial and deploy powers are built but disabled until later phases add spend caps, allow-lists, a public ledger, and audit controls.

Enabled now (content & ops):

• Edit site copy / listings / non-locked docs
• Add a DayZ server to the supported list
• Add/remove/stage a safehouse (routine → runner-ops side channel)
• Publish a non-binding community policy note

Disabled until later phases (founder-driven only):

• Spend from the donation treasury — Phase 3. Needs caps + allowlist + ledger + founder veto before it can turn on.
• Deploy the site — Phase 3+. Needs CI + human approval before it can turn on.
• Enable real-money rental pricing/checkout — PROHIBITED by COMPLIANCE.md. Cannot be enabled by any vote; founder + legal review only.

Want a say in how the fleet is run?

Join Discord, get verified, and weigh in on the next proposal in #vote.