= Governance
:project-name: {Project Name}
:repo-url: {Repository URL – *REMINDER: Provide this for each project*}

== 🏛️ Governance Model

{project-name} is governed through **transparent, community-oriented decision-making** that balances technical excellence with inclusivity.

== 🎯 Core Principles

1. **Transparency**: All decisions documented publicly
2. **Meritocracy**: Recognition based on contribution quality, not quantity
3. **Inclusivity**: Multiple paths to influence (TPCF)
4. **Sustainability**: Long-term thinking, succession planning
5. **Ethical alignment**: Decisions align with link:ETHICS.md[Ethical Guidelines]

== 👥 Roles & Responsibilities

=== Maintainers

**Current maintainers**: *REMINDER: List current maintainers*

- {Name} ({GitLab-username}) - {Role/Focus}
- {Name} ({GitLab-username}) - {Role/Focus}

**Responsibilities**:

- **Perimeter 1 access**: Core systems, build orchestration, CI/CD
- **Code review**: All merge requests to core systems
- **Release management**: Versioning, changelogs, releases
- **Security**: Vulnerability response, security audits
- **Governance**: Enforce CoC, resolve disputes

**Eligibility**:

- Sustained contributions (6+ months)
- Deep understanding of architecture
- Demonstrated commitment to RSR/CCCP principles
- Endorsed by 2+ existing maintainers

**Nomination**: link:{repo-url}/-/issues/new?issuable_template=maintainer_nomination[Maintainer nomination]

=== Trusted Contributors (Perimeter 2)

**Responsibilities**:

- **Protocol extensions**: New features, integrations
- **Expert contributions**: Advanced implementations
- **Mentorship**: Guide new contributors
- **Code review**: Review community contributions

**Eligibility**:

- Multiple quality contributions
- Expertise in relevant domain
- Understanding of TPCF and RSR compliance

**Application**: link:{repo-url}/-/issues/new?issuable_template=expert_contributor[Expert contributor application]

=== Community Members (Perimeter 3)

**Responsibilities**:

- **Documentation**: Improvements, translations
- **Testing**: Bug reports, spec tests
- **Ideas**: Feature requests, discussions

**Eligibility**: Anyone! Open to all.

**Start**: link:CONTRIBUTING.adoc[Contributing guide]

=== Stewards (Ethics Oversight)

**Current stewards**: *REMINDER: List stewards*

- {Name} - Focus: {ethical-domain}

**Responsibilities**:

- **Ethical review**: Assess ethical implications of decisions
- **Incident response**: Handle link:ETHICS.md[ethical concerns]
- **Policy development**: Update ethical guidelines

**Eligibility**:

- Demonstrated commitment to ethical technology
- Expertise in ethics, policy, or social impact
- Appointed by maintainers + community vote

== ⚖️ Decision-Making

=== Lazy Consensus

**Default model**: Lazy consensus for most decisions.

1. **Proposal**: Post in link:{repo-url}/-/issues[Issues] or link:{repo-url}/-/discussions[Discussions]
2. **Discussion**: Minimum 7 days for feedback
3. **Objections**: If none, proposal accepted
4. **Veto**: Maintainers can veto with justification

=== RFC (Request for Comments)

**Major changes** require RFC:

- Architecture changes
- Breaking changes
- New perimeter assignments
- Governance changes

**Process**:

1. **Draft**: Create RFC in `docs/rfcs/`
2. **Discussion**: Minimum 14 days
3. **Vote**: Maintainers vote (majority)
4. **Implementation**: Approved RFCs tracked in link:ROADMAP.md[Roadmap]

**Template**: link:docs/rfcs/template.adoc[RFC template]

=== Voting

**When needed** (RFCs, maintainer nominations, major disputes):

- **Maintainers**: 1 vote each
- **Quorum**: 50% + 1 of maintainers
- **Majority**: > 50% of votes cast
- **Veto**: No vetoes without supermajority (75%) override

**Transparency**: All votes documented in issue/RFC.

== 🔄 Conflict Resolution

=== Step 1: Direct Communication

Parties attempt to resolve directly.

=== Step 2: Mediation

Neutral maintainer facilitates discussion.

=== Step 3: Arbitration

Maintainers vote on resolution (majority).

=== Step 4: Escalation

Stewards review for ethical implications.

=== Code of Conduct Violations

See link:CODE_OF_CONDUCT.adoc[Code of Conduct] for separate process.

== 🎓 Maintainer Succession

=== Active Maintainership

Maintainers are expected to:

- **Respond**: To issues, MRs, discussions (reasonably)
- **Contribute**: Code, review, or governance
- **Communicate**: Life changes, reduced availability

=== Emeritus Status

Inactive maintainers (6+ months) become **Emeritus Maintainers**:

- **Recognition**: Credited in CONTRIBUTORS.md
- **Advisory role**: Can advise, no voting rights
- **Re-activation**: Can request active status if circumstances change

=== Removal

Maintainers can be removed for:

- **Inactivity**: 12+ months without communication
- **CoC violations**: Repeated or severe violations
- **Loss of trust**: Supermajority (75%) vote

**Process**: RFC + vote, with opportunity to respond.

== 💰 Financial Governance

=== Funding Sources

*REMINDER: Document funding sources.*

- **Donations**: link:FUNDING.yml[FUNDING.yml]
- **Sponsorships**: {sponsor-details}
- **Grants**: {grant-details}

=== Budget Decisions

- **< £500**: Maintainer discretion
- **£500-£5000**: Maintainer consensus
- **> £5000**: Community RFC + vote

**Transparency**: Quarterly financial reports in link:docs/finances/[Finances folder]

=== Paid Contributions

- **Bounties**: Funded features, open to all
- **Stipends**: For sustained contributors
- **Contracting**: Specific expertise needs

**Policy**: link:docs/finances/paid-contributions.adoc[Paid contributions policy]

== 🗳️ Elections

=== Maintainer Elections

**Frequency**: Annual (or as needed)

**Process**:

1. **Nominations**: Open 2 weeks
2. **Campaigning**: Candidates present vision
3. **Voting**: All contributors with 3+ merged contributions
4. **Results**: Published publicly

=== Steward Elections

**Frequency**: Every 2 years

**Process**: Similar to maintainer elections, with emphasis on ethical expertise.

== 📊 Transparency & Accountability

=== Public Records

- **Decisions**: Documented in issues, RFCs, discussions
- **Meetings**: Minutes published (if private meetings occur)
- **Finances**: Quarterly reports
- **Enforcement**: Anonymised CoC actions (quarterly)

=== Annual Reports

**Published annually**:

- Project health (contributors, issues, MRs)
- Financial summary
- Governance changes
- Major accomplishments
- Future direction

== 🔄 Governance Evolution

This governance model is **not set in stone**.

**Propose changes**:

1. **RFC**: Draft governance change
2. **Discussion**: Minimum 30 days
3. **Vote**: Supermajority (75%) required
4. **Implementation**: Update this document

== 📞 Contact

- **Governance questions**: link:{repo-url}/-/discussions[Discussions]
- **Maintainer nominations**: link:{repo-url}/-/issues/new?issuable_template=maintainer_nomination[Nomination template]
- **Disputes**: {governance-email}

== 📚 References

- **TPCF**: link:CONTRIBUTING.adoc[Tri-Perimeter Contribution Framework]
- **Ethics**: link:ETHICS.md[Ethical Guidelines]
- **CoC**: link:CODE_OF_CONDUCT.adoc[Code of Conduct]
- **MAA Framework**: link:CLAUDE.md[Mutually Assured Accountability]

---

*"Governance is service, not authority."*

— The Rhodium Standard
