Organisational Model

1.1

1

= Organisational Model =

== 1. Purpose ==

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.

Core domains:

* **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

== 3. Domain Interaction Map ==

22

23

{{include reference="FactHarbor.Organisation.Diagrams.Domain Interaction Map.WebHome"/}}

24

25

== 4. Interfaces Between Domains ==

26

27

The Organisational Model defines clear interfaces:

28

29

* Research & Development and Organisation collaborate on documentation, modelling principles, and how reasoning is exposed to users.

30

* Organisation and PR & Care & Marketing collaborate on user-facing explanations and onboarding material.

31

* Organisation and Operations collaborate on access rules, backup and disaster-recovery procedures, and operational constraints.

32

* PR & Care & Marketing and Operations collaborate on communication-related tools, channels, and moderation infrastructure.

33

34

== 5. Small Organisation Assumption ==

35

36

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.

37

38

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.

39

40

== 6. Growth and Federation ==

41

42

As participation grows, domains may be split into more specialised roles or teams.

43

The Organisational Model should remain stable enough that:

44

45

* new teams can be added under existing domains

46