Signed-off-by: Mika Ipstenu Epstein <ipstenu@ipstenu.org> Signed-off-by: Brent Toderash <brent@toderash.net> Signed-off-by: Ipstenu (Mika Epstein) <Ipstenu@users.noreply.github.com> Signed-off-by: Claudio Rimann <claudio@haptiq.studio> Signed-off-by: Joe Murray <joe.murray@jmaconsulting.biz> Signed-off-by: Ryan McCue <me@ryanmccue.info> Co-authored-by: Brent Toderash <brent@toderash.net> Co-authored-by: Claudio Rimann <claudio@haptiq.studio> Co-authored-by: Joe Murray <joe.murray@jmaconsulting.biz> Co-authored-by: Ryan McCue <me@ryanmccue.info> |
||
|---|---|---|
| .. | ||
| appeals.md | ||
| contact-and-privacy.md | ||
| defederation.md | ||
| integrity.md | ||
| moderation-labels.md | ||
| moderation-services.md | ||
| README.md | ||
| risk-management.md | ||
| vetting-and-reporting.md | ||
Governance
| Status | Proposal |
| Date | 2025-07-22 |
Decentralization empowers anyone to host and distribute software, but it also requires shared responsibility. The FAIR Protocol defines a governance framework to ensure participants operate transparently, protect user data, and uphold moderation standards.
This section outlines the minimum expectations for all federation members, including:
- Contact and privacy requirements
- Integration with federation-wide moderation systems like Ozone
- Compliance with data protection laws (e.g., GDPR)
- Risk management
All Repositories and Aggregators must adhere to these requirements to remain part of the FAIR ecosystem. Governance is not about central control — it’s about maintaining mutual trust, accountability, and safety across a distributed network.
Topics
- Contact and Privacy Requirements
- Integrity and Transparency Requirements
- Vetting and Reporting
- Defederation and Removal Policy
- Risk Management
- ppeals Process
More documents may be added as the federation evolves to include appeals processes, escalation procedures, or delegated authority models.