Wiki source code of Organisational Model

Last modified by Robert Schaub on 2025/12/24 20:33

Show last authors
1 = Organisational Model =
2
3 == 1. Purpose ==
4
5 The Organisational Model describes how FactHarbor structures responsibilities, domains, and interfaces between them. It provides a framework that works for a very small organisation today and can scale to a larger community and possible federation.
6
7 == 2. Domains, Not Departments ==
8
9 FactHarbor works with **domains** rather than hard organisational departments.
10
11 A domain is a cluster of responsibilities and workflows. In early phases the same person may act in multiple domains; later, responsibilities can be distributed across several people and teams.
12
13 Core domains:
14
15 * **Research & Development domain** – Technical architecture, data model, core algorithms, and quality of modelling and reasoning.
16 * **Organisation domain** – Governance, documentation, contributor processes, licensing interpretation, organisational rules, and XWiki structure.
17 * **Public Relations & Care & Marketing domain** – Communication, clarity of messaging, user education, community support, and campaigns that respect neutrality principles.
18 * **Operations domain** – Infrastructure, hosting, deployment, monitoring, backups, access management, and operational security.
19
20
21
22 ----
23
24 == Domain Interaction Map ==
25
26 {{include reference="Archive.FactHarbor V0\.9\.23 Lost Data.Organisation.Diagrams.Domain Interaction Map.WebHome"/}}
27
28 == 3. Interfaces Between Domains ==
29
30 The Organisational Model defines clear interfaces:
31
32 * Research & Development and Organisation collaborate on documentation, modelling principles, and how reasoning is exposed to users.
33 * Organisation and PR & Care & Marketing collaborate on user-facing explanations and onboarding material.
34 * Organisation and Operations collaborate on access rules, backup and disaster-recovery procedures, and operational constraints.
35 * PR & Care & Marketing and Operations collaborate on communication-related tools, channels, and moderation infrastructure.
36
37 == 4. Small Organisation Assumption ==
38
39 In the early phases, FactHarbor is a **small organisation**. One person may hold multiple roles such as Executive Lead, Organisation Lead, and temporary R&D or PR responsibilities.
40
41 The model explicitly allows this while still keeping different responsibilities conceptually separate, so that they can later be split across several people without rewriting the core model.
42
43 == 5. Growth and Federation ==
44
45 As participation grows, domains may be split into more specialised roles or teams.
46 The Organisational Model should remain stable enough that:
47
48 * new teams can be added under existing domains
49 * responsibilities can be delegated without changing basic principles
50 * federated instances can align with the same high-level structure.