Organisation – Domain

1. Purpose of the Organisation Domain

The Organisation domain defines and maintains the structural, governance, contributor, licensing, and documentation framework of FactHarbor. It exists so that the project operates with clarity, transparency, and well-defined responsibilities — even when it grows from a very small organisation to a larger, federated community.

2. Relationship to the FactHarbor Mission

FactHarbor’s mission is to bring clarity and transparency to complex, controversial, and misleading information.
The Organisation domain contributes to this mission by:

• keeping governance and contributor rules open and understandable
• documenting how decisions are made and who is responsible
• ensuring that licensing and funding models support long-term openness and independence
• supporting new contributors so they can participate safely and effectively.

3. Scope

The Organisation domain covers:

• Organisational structure, roles, and bodies
• Governance rules, decision processes, and escalation paths
• Contributor journeys, permissions, and responsibilities
• Open source model and licensing interpretation
• Finance & Compliance principles and funding model
• Legal and archival framework for the project
• Interfaces to the Research & Development, PR & Care & Marketing, and Operations domains

The Organisation domain does not design technical architectures or data models; that is the responsibility of the Research & Development domain.

4. Conceptual Domain Structure

FactHarbor is organised into conceptual domains. These domains do not necessarily correspond to formal departments or teams; in a small organisation one person can hold several roles across domains.

The core domains are:

• Research & Development domain – Owns the technical architecture, data model, modelling principles, and quality of reasoning.
• Organisation domain – Governs documentation, contributor processes, licensing interpretation, organisational rules, and the XWiki structure.
• Public Relations & Care & Marketing domain – Handles communication, user education, community support, and campaigns that remain fully compatible with neutrality principles.
• Operations domain – Responsible for infrastructure, hosting, deployment, monitoring, backups, access management, and operational security.

5. Boundaries and Interfaces

Key boundaries:

• Organisation defines rules and documentation; Research & Development designs technical structures.
• Organisation defines workflows; Operations executes them and reports operational constraints.
• PR & Care & Marketing adapts tone and format, but does not change the meaning of content.
• Governance bodies supervise and resolve escalations, but do not micromanage day-to-day work.

Typical interfaces:

• R&D and Organisation collaborate on documentation and modelling principles.
• Organisation and PR & Care & Marketing collaborate on user-facing explanations and onboarding material.
• Organisation and Operations collaborate on access rules, backup strategies, and disaster-recovery procedures.

6. Reading Guide

The Organisation domain is described in more detail on the following subpages:

Core Structure

• Organisational Model – how responsibilities, domains, and interfaces are structured
• Roles & Bodies – key roles and organisational bodies
• Transition Model – how the organisation evolves between phases

Rules & Rights

• Governance – governing bodies, roles, and compliance
• Open Source Model and Licensing – licensing choices and open-source governance
• Legal Framework – legal basis for the organisation

Operations

• Finance & Compliance – funding principles, transparency, and internal controls
• Decision Processes – decision types, escalation, and documentation

People

• Contributor Models – contributor journey and participation models
• Contributor Processes – contributor workflows and process definitions

Technical

• Diagrams – diagram index and technical references (if any).