Wiki source code of Organisation

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

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