Skip to Content

Changes for page Governance

Last modified by Robert Schaub on 2026/02/08 21:21
From version 1.4
edited by Robert Schaub
on 2026/02/08 08:08
Change comment: Renamed back-links.
To version 1.1
edited by Robert Schaub
on 2025/12/22 14:10
Change comment: Imported from XAR

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,1 @@
1 -Test.FactHarbor pre11 V0\.9\.70.Organisation.WebHome
1 +Test.FactHarbor.Organisation.WebHome
Content
... ... @@ -1,22 +1,15 @@
1 1  = Governance =
2 -
3 3  FactHarbor governance is **simple, transparent, flat, and focused on enabling automation**.
4 -{{include reference="Archive.FactHarbor 2026\.01\.20.Organisation.Diagrams.Governance Structure.WebHome"/}}
5 -
3 +{{include reference="FactHarbor.Organisation.Diagrams.Governance Structure.WebHome"/}}
6 6  == 1. Governance Philosophy ==
7 -
8 8  **Core Principles**:
9 -
10 10  * **Automation over bureaucracy**: Minimize manual processes
11 11  * **Transparency by default**: Open decision-making
12 12  * **Community input**: Listen but decide decisively
13 13  * **Measured outcomes**: Data drives decisions
14 14  * **Adaptive structure**: Evolve as needed
15 -
16 16  == 2. Organizational Structure ==
17 -
18 18  **Flat Cooperative Model**:
19 -
20 20  * Small organization with collaborative teamwork
21 21  * No hierarchical management layers
22 22  * Decisions by consensus when possible, voting when needed
... ... @@ -24,50 +24,34 @@
24 24  **General Assembly** → **Governing Team** → **Team Members** === 2.1 General Assembly (All Members) ===
25 25  Decides: Governing Team election, statutes, major strategic changes, budget
26 26  Meets: Annually
27 -
28 28  === 2.2 Governing Team ===
29 -
30 30  Decides: Strategy, policy, budget allocation, hiring
31 31  Meets: Quarterly
32 32  Size: small group (Facilitator, Coordinator, Treasurer + others)
33 -
34 34  === 2.3 Team Members ===
35 -
36 36  * **Technical Coordinator**: AKEL & infrastructure
37 37  * **Community Coordinator**: Moderators & contributors
38 38  * **Moderators** (part-time): Handle abuse/disputes
39 -
40 40  == 3. Decision Authority ==
41 -
42 42  **Day-to-day**: Technical Coordinator + Community Coordinator
43 43  **Tactical**: Governing Team (simple majority)
44 44  **Strategic**: General Assembly (2/3 majority)
45 -
46 46  == 4. Policy Development ==
47 -
48 48  **RFC Process** (Request for Comments):
49 -
50 50  1. Anyone drafts proposal
51 51  2. Community discussion 3. Governing Team reviews and votes
52 52  4. Decision published
53 53  **Emergency changes**: Technical Coordinator can act immediately, Governing Team ratifies later
54 -
55 55  == 5. Financial Governance ==
56 -
57 57  * Annual budget approved by General Assembly
58 58  * Two-signature requirement for >CHF 5,000
59 59  * Governing Team approval for >CHF 20,000
60 60  * Quarterly financial reports
61 61  * Annual independent audit
62 -
63 63  == 6. Automation Governance ==
64 -
65 65  **Core Principle**: AKEL makes content decisions. Humans make system decisions.
66 -
67 67  === 6.1 Decision Boundary ===
68 -
69 69  **What AKEL Decides (Automated)**:
70 -
71 71  * All claim verdicts and confidence scores
72 72  * All evidence assessments and relevance scores
73 73  * All source track record scores
... ... @@ -97,11 +97,8 @@
97 97  * Critical security issues
98 98  * Legal compliance requirements
99 99  * Immediate safety concerns
100 -
101 101  === 6.2 Principle: Fix the System, Not the Data ===
102 -
103 103  **When AKEL makes a "wrong" decision**:
104 -
105 105  * ❌ Do NOT manually override that specific verdict
106 106  * ✅ DO investigate: Is this a systematic issue?
107 107  * ✅ DO improve: Change algorithm/policy to handle such cases better
... ... @@ -111,11 +111,8 @@
111 111  **Example**:
112 112  * Bad: "AKEL rated this source too low, I'll manually boost it"
113 113  * Good: "AKEL consistently under-rates peer-reviewed sources. Let's adjust the scoring algorithm to weight peer-review more heavily."
114 -
115 115  === 6.3 Governance of AKEL ===
116 -
117 117  **Quarterly Performance Review**:
118 -
119 119  * Who: Governing Team + Technical Coordinator
120 120  * What: Review AKEL performance metrics, bias audits, user feedback patterns
121 121  * Output: Performance report, improvement priorities, policy updates if needed
... ... @@ -133,7 +133,6 @@
133 133  * Legal/compliance concerns
134 134  * New domains requiring special handling
135 135  **Algorithm Change Process**:
136 -
137 137  1. Identify issue from metrics
138 138  2. Propose solution (RFC - Request for Comments)
139 139  3. Test in staging environment
... ... @@ -141,11 +141,8 @@
141 141  5. Technical Coordinator approves (or escalates to Governing Team for policy changes)
142 142  6. Deploy with monitoring
143 143  7. Evaluate results
144 -
145 145  === 6.4 Human Intervention Criteria ===
146 -
147 147  **Legitimate reasons to intervene**:
148 -
149 149  * ✅ AKEL explicitly flags item for human review
150 150  * ✅ System metrics show performance degradation
151 151  * ✅ Legal/safety issue requires immediate action
... ... @@ -155,17 +155,13 @@
155 155  * ❌ "This source should rank higher" → Improve scoring rules
156 156  * ❌ "Manual quality gate before publication" → Defeats purpose of automation
157 157  * ❌ "I know better than the algorithm" → Then improve the algorithm
158 -
159 159  === 6.5 Consent-Based Decision Making ===
160 -
161 161  **For system changes**, use consent not consensus (from Sociocracy 3.0):
162 162  **Consent** = No principled objections
163 -
164 164  * Faster than consensus
165 165  * Respects concerns without requiring full agreement
166 166  * "I can live with this and support it"
167 167  **Process**:
168 -
169 169  1. Proposal presented (RFC)
170 170  2. Clarifying questions
171 171  3. Reactions and concerns
... ... @@ -174,7 +174,6 @@
174 174  6. If no objections → Decision made
175 175  7. If objections → Integrate and repeat
176 176  **Use for**:
177 -
178 178  * Algorithm changes
179 179  * Policy updates
180 180  * Infrastructure investments
... ... @@ -182,38 +182,26 @@
182 182  **Not for**:
183 183  * Strategic decisions (use voting)
184 184  * Emergency decisions (use autonomous authority)
185 -
186 186  == 7. Transparency & Accountability ==
187 -
188 188  **Always public**: Policies, structure, board membership, financials, quality metrics, major decisions
189 189  **Published quarterly**: Activity reports, metrics, moderation stats
190 190  **Internal documentation**: All meetings, decisions, actions retained indefinitely
191 -
192 192  == 7. Conflict Resolution ==
193 -
194 194  **User disputes**: Moderator → Appeal to different moderator → Governing Team (final)
195 195  **Timeline**: Reasonable timeframe
196 -
197 197  == 8. Moderation Oversight ==
198 -
199 199  **Moderator requirements**: high reputation, 6+ months active, clean record
200 200  **Review**: Quarterly by Community Coordinator, annually by Governing Team
201 201  **Appeal**: Any user can appeal promptly
202 -
203 203  == 9. Code of Conduct ==
204 -
205 205  **Governing Team**: Act in org interest, disclose conflicts, maintain confidentiality
206 206  **Team Members**: Follow procedures, professional conduct, document decisions
207 207  **Moderators**: Impartial decisions, respect privacy, respond timely
208 -
209 209  == 10. Amendment Process ==
210 -
211 211  **Minor changes**: Governing Team decision
212 212  **Major changes**: General Assembly (2/3 vote)
213 213  **Emergency**: Governing Team can act, must ratify at next Assembly
214 -
215 215  == 11. Related Pages ==
216 -
217 217  * [[Organisational Model>>FactHarbor.Organisation.Organisational-Model]]
218 218  * [[Legal Framework>>FactHarbor.Organisation.Legal-Framework]]
219 219  * [[Transparency Policy>>FactHarbor.Organisation.How-We-Work-Together.Transparency-Policy]]