Skip to Content

Wiki source code of Organisation

Last modified by Robert Schaub on 2025/12/24 20:29
Show last authors
1 {{warning title="Version 0.9.32 (Draft)"}}
2 This document describes the **Organisation** domain of FactHarbor.
3 It is a working draft and may change as legal and community feedback is integrated.
4 {{/warning}}
5
6 = Organisation – Domain =
7
8 == 1. Purpose of the Organisation Domain ==
9
10 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.
11
12 == 2. Relationship to the FactHarbor Mission ==
13
14 FactHarbor’s mission is to bring clarity and transparency to complex, controversial, and misleading information.
15 The Organisation domain contributes to this mission by:
16
17 * keeping governance and contributor rules open and understandable
18 * documenting how decisions are made and who is responsible
19 * ensuring that licensing and funding models support long-term openness and independence
20 * supporting new contributors so they can participate safely and effectively.
21
22 == 3. Scope ==
23
24 The Organisation domain covers:
25
26 * Organisational structure, roles, and bodies
27 * Governance rules, decision processes, and escalation paths
28 * Contributor journeys, permissions, and responsibilities
29 * Open source model and licensing interpretation
30 * Finance & Compliance principles and funding model
31 * Legal and archival framework for the project
32 * Interfaces to the Research & Development, PR & Care & Marketing, and Operations domains
33
34 The Organisation domain does **not** design technical architectures or data models; that is the responsibility of the Research & Development domain.
35
36 == 4. Conceptual Domain Structure ==
37
38 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.
39
40 The core domains are:
41
42 * **Research & Development domain** – Owns the technical architecture, data model, modelling principles, and quality of reasoning.
43 * **Organisation domain** – Governs documentation, contributor processes, licensing interpretation, organisational rules, and the XWiki structure.
44 * **Public Relations & Care & Marketing domain** – Handles communication, user education, community support, and campaigns that remain fully compatible with neutrality principles.
45 * **Operations domain** – Responsible for infrastructure, hosting, deployment, monitoring, backups, access management, and operational security.
46
47 == 5. Boundaries and Interfaces ==
48
49 Key boundaries:
50
51 * Organisation defines rules and documentation; Research & Development designs technical structures.
52 * Organisation defines workflows; Operations executes them and reports operational constraints.
53 * PR & Care & Marketing adapts tone and format, but does not change the meaning of content.
54 * Governance bodies supervise and resolve escalations, but do not micromanage day-to-day work.
55
56 Typical interfaces:
57
58 * R&D and Organisation collaborate on documentation and modelling principles.
59 * Organisation and PR & Care & Marketing collaborate on user-facing explanations and onboarding material.
60 * Organisation and Operations collaborate on access rules, backup strategies, and disaster-recovery procedures.
61
62 == 6. Reading Guide ==
63
64 The Organisation domain is described in more detail on the following subpages:
65
66 **Core Structure**
67 * [[Organisational Model>>FactHarbor.Organisation.Organisational-Model]] – how responsibilities, domains, and interfaces are structured
68 * [[Roles & Bodies>>FactHarbor.Organisation.Roles-Bodies]] – key roles and organisational bodies
69 * [[Transition Model>>FactHarbor.Organisation.Transition-Model]] – how the organisation evolves between phases
70
71 **Rules & Rights**
72 * [[Governance>>FactHarbor.Organisation.Governance]] – governing bodies, roles, and compliance
73 * [[Open Source Model and Licensing>>FactHarbor.Organisation.Open Source Model and Licensing]] – licensing choices and open-source governance
74 * [[Legal Framework>>FactHarbor.Organisation.Legal-Framework]] – legal basis for the organisation
75
76 **Operations**
77 * [[Finance & Compliance>>FactHarbor.Organisation.Finance-Compliance]] – funding principles, transparency, and internal controls
78 * [[Decision Processes>>FactHarbor.Organisation.Decision-Processes]] – decision types, escalation, and documentation
79
80 **People**
81 * [[Contributor Models>>FactHarbor.Organisation.Contributor Models]] – contributor journey and participation models
82 * [[Contributor Processes>>FactHarbor.Organisation.Contributor-Processes]] – contributor workflows and process definitions
83
84 **Technical**
85 * [[Diagrams>>FactHarbor.Organisation.Diagrams.WebHome]] – diagram index and technical references (if any).