Wiki source code of Organisational Model
Last modified by Robert Schaub on 2026/02/08 08:31
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | = Organisational Model = | ||
| 2 | |||
| 3 | FactHarbor operates as a **Swiss Verein** (non-profit association) with a **simple, flat structure** focused on automation over bureaucracy. | ||
| 4 | |||
| 5 | == 1. Legal Structure == | ||
| 6 | |||
| 7 | **Entity Type**: Swiss Verein (Association) | ||
| 8 | **Jurisdiction**: Switzerland | ||
| 9 | **Governed By**: Swiss Civil Code (Art. 60-79) | ||
| 10 | **Key Characteristics**: | ||
| 11 | |||
| 12 | * Non-profit purpose | ||
| 13 | * Member-based governance | ||
| 14 | * Democratic decision-making | ||
| 15 | * Limited liability | ||
| 16 | * Tax-exempt status (if public benefit) | ||
| 17 | |||
| 18 | == 2. Governance Structure == | ||
| 19 | |||
| 20 | === 2.1 General Assembly === | ||
| 21 | |||
| 22 | **Composition**: All Verein members | ||
| 23 | **Powers**: | ||
| 24 | |||
| 25 | * Elect Governing Team | ||
| 26 | * Approve annual budget | ||
| 27 | * Amend statutes | ||
| 28 | * Decide on major strategic changes | ||
| 29 | * Dissolve organization | ||
| 30 | **Meetings**: Annually (+ extraordinary as needed) | ||
| 31 | |||
| 32 | === 2.2 Governing Team === | ||
| 33 | |||
| 34 | **Size**: small group | ||
| 35 | **Composition**: | ||
| 36 | |||
| 37 | * Facilitator (chair) | ||
| 38 | * Coordinator | ||
| 39 | * Treasurer | ||
| 40 | * 0-4 additional team members | ||
| 41 | **Term**: 2 years (renewable) | ||
| 42 | **Powers**: | ||
| 43 | * Strategic direction | ||
| 44 | * Budget approval | ||
| 45 | * Policy decisions | ||
| 46 | * Hiring/firing key staff | ||
| 47 | * Represent organization externally | ||
| 48 | **Meetings**: Quarterly (minimum) | ||
| 49 | |||
| 50 | === 2.3 Team Member Roles === | ||
| 51 | |||
| 52 | **Philosophy**: Minimal team, automation-first. Team members improve the SYSTEM, not the DATA. | ||
| 53 | **Core Principle**: AKEL makes content decisions. Humans monitor system performance and improve algorithms. | ||
| 54 | **Essential Roles**: | ||
| 55 | **Technical Coordinator** (1 FTE): | ||
| 56 | |||
| 57 | * **Domain**: AKEL performance and infrastructure | ||
| 58 | * **Monitors**: Processing speed, error rates, resource utilization, algorithm performance metrics | ||
| 59 | * **Improves**: Algorithms, infrastructure optimization, processing efficiency | ||
| 60 | * **Does NOT**: Review individual claim verdicts, override AKEL decisions | ||
| 61 | * **Authority**: Approve technical changes within domain boundaries | ||
| 62 | * **Decision Method**: Autonomous within domain, consent for cross-domain changes | ||
| 63 | **Community Coordinator** (1 FTE): | ||
| 64 | * **Domain**: Community health and feedback loop optimization | ||
| 65 | * **Monitors**: User feedback patterns, contribution quality trends, community engagement | ||
| 66 | * **Improves**: Onboarding processes, documentation, feedback mechanisms, community guidelines | ||
| 67 | * **Does NOT**: Moderate individual disputes (AKEL handles), make content decisions | ||
| 68 | * **Authority**: Approve community process changes | ||
| 69 | * **Decision Method**: Autonomous within domain | ||
| 70 | **Moderators** (part-time): | ||
| 71 | * **Domain**: Handle AKEL-flagged escalations and system gaming | ||
| 72 | * **Monitors**: Items AKEL marks for human review (abuse, manipulation attempts) | ||
| 73 | * **Improves**: Detection algorithms based on observed patterns | ||
| 74 | * **Does NOT**: Routine content review, override AKEL verdicts | ||
| 75 | * **Authority**: Handle flagged items, propose detection improvements | ||
| 76 | * **Decision Method**: Autonomous for flagged items, propose improvements to Technical Coordinator | ||
| 77 | **Optional Contractors** (as needed): | ||
| 78 | * Developers: Specific feature development | ||
| 79 | * Data Scientists: Algorithm research and optimization | ||
| 80 | * Legal Counsel: Compliance and legal review | ||
| 81 | * Accountant: Annual audits | ||
| 82 | **Total Core Staff**: full-timeE + part-time moderators | ||
| 83 | **Key Distinction**: | ||
| 84 | * ✅ Team members monitor AGGREGATE metrics and improve SYSTEMS | ||
| 85 | * ❌ Team members do NOT review individual claims or override AKEL | ||
| 86 | * ✅ When metrics show problems, fix the ALGORITHM | ||
| 87 | * ❌ Do NOT manually correct individual outputs | ||
| 88 | |||
| 89 | === 2.3.5 Team Roles Diagram === | ||
| 90 | |||
| 91 | {{include reference="Archive.FactHarbor 2026\.02\.08.Specification.Diagrams.Human User Roles.WebHome"/}} | ||
| 92 | |||
| 93 | == 3. Decision-Making == | ||
| 94 | |||
| 95 | === 3.1 Routine Operations === | ||
| 96 | |||
| 97 | **Handled by**: Technical Coordinator + Community Coordinator | ||
| 98 | **Scope**: | ||
| 99 | |||
| 100 | * Day-to-day operations | ||
| 101 | * Content moderation (via moderators) | ||
| 102 | * Technical maintenance | ||
| 103 | * Minor policy clarifications | ||
| 104 | **Transparency**: All decisions documented | ||
| 105 | |||
| 106 | === 3.2 Strategic Decisions === | ||
| 107 | |||
| 108 | **Handled by**: Governing Team | ||
| 109 | **Scope**: | ||
| 110 | |||
| 111 | * Budget allocation | ||
| 112 | * Major feature additions | ||
| 113 | * Policy changes | ||
| 114 | * Partnerships | ||
| 115 | * Hiring | ||
| 116 | **Process**: Majority vote (quorum: 50%+1) | ||
| 117 | |||
| 118 | === 3.3 Major Changes === | ||
| 119 | |||
| 120 | **Handled by**: General Assembly | ||
| 121 | **Scope**: | ||
| 122 | |||
| 123 | * Statute amendments | ||
| 124 | * Dissolution | ||
| 125 | * Merger/acquisition | ||
| 126 | * Major strategic pivots | ||
| 127 | **Process**: 2/3 majority vote | ||
| 128 | |||
| 129 | == 4. User Community Roles == | ||
| 130 | |||
| 131 | {{include reference="Archive.FactHarbor 2026\.02\.08.Organisation.Diagrams.Governance Structure.WebHome"/}} | ||
| 132 | |||
| 133 | === 4.1 Readers === | ||
| 134 | |||
| 135 | **Rights**: | ||
| 136 | |||
| 137 | * Browse content | ||
| 138 | * Flag issues | ||
| 139 | * Submit claims | ||
| 140 | **Responsibilities**: | ||
| 141 | * Respect community standards | ||
| 142 | * Provide constructive feedback | ||
| 143 | |||
| 144 | === 4.2 Contributors === | ||
| 145 | |||
| 146 | **Reputation system** replaces role hierarchy. Earn through quality contributions. | ||
| 147 | **Requirements**: | ||
| 148 | |||
| 149 | * Register account | ||
| 150 | * Accept terms of service | ||
| 151 | * Build reputation through contributions | ||
| 152 | **Rights**: | ||
| 153 | * Edit claims, evidence, scenarios | ||
| 154 | * Participate in discussions | ||
| 155 | * Earn reputation points | ||
| 156 | **Responsibilities**: | ||
| 157 | * Maintain neutrality | ||
| 158 | * Cite sources | ||
| 159 | * Accept feedback graciously | ||
| 160 | |||
| 161 | === 4.3 Moderators === | ||
| 162 | |||
| 163 | **Selection**: | ||
| 164 | |||
| 165 | * Appointed by Governing Team | ||
| 166 | * Must have high reputation | ||
| 167 | * Must have clean track record | ||
| 168 | **Rights**: | ||
| 169 | * Review flagged content | ||
| 170 | * Hide harmful content | ||
| 171 | * Issue warnings/bans | ||
| 172 | * Resolve disputes | ||
| 173 | **Responsibilities**: | ||
| 174 | * Impartiality | ||
| 175 | * Transparency | ||
| 176 | * Documented decisions | ||
| 177 | * Timely response | ||
| 178 | **Oversight**: | ||
| 179 | * Governing Team reviews moderator actions | ||
| 180 | * Can overturn decisions | ||
| 181 | * Annual performance review | ||
| 182 | |||
| 183 | == 5. Membership == | ||
| 184 | |||
| 185 | === 5.1 Verein Membership === | ||
| 186 | |||
| 187 | **Who can join**: | ||
| 188 | |||
| 189 | * Anyone supporting FactHarbor's mission | ||
| 190 | * Age 18+ | ||
| 191 | * Accept statutes | ||
| 192 | **Membership fee**: Symbolic (e.g., CHF 20/year) | ||
| 193 | **Rights**: | ||
| 194 | * Vote in General Assembly | ||
| 195 | * Stand for Governing Team election | ||
| 196 | * Access to member-only information | ||
| 197 | * Participate in strategic discussions | ||
| 198 | **Termination**: | ||
| 199 | * Voluntary resignation | ||
| 200 | * Non-payment of dues (after warning) | ||
| 201 | * Serious violation of principles | ||
| 202 | * Decision by General Assembly | ||
| 203 | |||
| 204 | === 5.2 Contributor Status === | ||
| 205 | |||
| 206 | **Separate from membership**: Can be contributor without being member | ||
| 207 | **Based on**: Activity and reputation | ||
| 208 | **No fees**: Open to all | ||
| 209 | |||
| 210 | == 6. Funding Model == | ||
| 211 | |||
| 212 | === 6.1 Revenue Sources === | ||
| 213 | |||
| 214 | **Primary**: | ||
| 215 | |||
| 216 | * Grants from foundations | ||
| 217 | * Donations from individuals | ||
| 218 | * Institutional partnerships | ||
| 219 | **Secondary**: | ||
| 220 | * API access fees (commercial users) | ||
| 221 | * Data licensing (with open data commitment) | ||
| 222 | * Training/consulting services | ||
| 223 | **Prohibited**: | ||
| 224 | * Advertising | ||
| 225 | * Selling user data | ||
| 226 | * Pay-for-rating | ||
| 227 | * Conflicts of interest | ||
| 228 | |||
| 229 | === 6.2 Budget Transparency === | ||
| 230 | |||
| 231 | **Publicly disclosed**: | ||
| 232 | |||
| 233 | * Annual financial statements | ||
| 234 | * Major funding sources (>10% of budget) | ||
| 235 | * Team Members compensation ranges | ||
| 236 | * Major expenses | ||
| 237 | **Published**: On website, annually | ||
| 238 | |||
| 239 | == 7. Conflict of Interest Policy == | ||
| 240 | |||
| 241 | === 7.1 Governing Team Members & Team Members === | ||
| 242 | |||
| 243 | **Must disclose**: | ||
| 244 | |||
| 245 | * Financial interests | ||
| 246 | * Employment relationships | ||
| 247 | * Family connections | ||
| 248 | * Other potential conflicts | ||
| 249 | **Must recuse** from decisions where conflicted | ||
| 250 | |||
| 251 | === 7.2 Contributors === | ||
| 252 | |||
| 253 | **Prohibited**: | ||
| 254 | |||
| 255 | * Direct financial stake in claim outcomes | ||
| 256 | * Paid to promote/attack specific claims | ||
| 257 | **Required**: | ||
| 258 | * Disclosure of other potential conflicts | ||
| 259 | * In evaluation history, not in account | ||
| 260 | |||
| 261 | == 8. Accountability Mechanisms == | ||
| 262 | |||
| 263 | === 8.1 Internal === | ||
| 264 | |||
| 265 | * Governing Team oversight of staff | ||
| 266 | * Regular audits (financial, security) | ||
| 267 | * Performance metrics published | ||
| 268 | * Community feedback channels | ||
| 269 | * Moderator appeal process | ||
| 270 | |||
| 271 | === 8.2 External === | ||
| 272 | |||
| 273 | * Annual report to members | ||
| 274 | * Public financial statements | ||
| 275 | * Independent audits | ||
| 276 | * Media scrutiny | ||
| 277 | * Academic research welcome | ||
| 278 | |||
| 279 | === 8.3 Transparency Commitments === | ||
| 280 | |||
| 281 | * Open source code | ||
| 282 | * Public data exports | ||
| 283 | * Documented decisions | ||
| 284 | * Algorithm transparency | ||
| 285 | * Quality metrics dashboard | ||
| 286 | |||
| 287 | == 9. Dispute Resolution == | ||
| 288 | |||
| 289 | === 9.1 User Disputes === | ||
| 290 | |||
| 291 | **Level 1**: Moderator decision | ||
| 292 | **Level 2**: Appeal to different moderator | ||
| 293 | **Level 3**: Governing Team review (final) | ||
| 294 | **Timeline**: Reasonable timeframe | ||
| 295 | |||
| 296 | === 9.2 Team Members/Governing Team Disputes === | ||
| 297 | |||
| 298 | **Internal**: Direct discussion | ||
| 299 | **Mediation**: If needed, external mediator | ||
| 300 | **Arbitration**: If unresolved, Swiss arbitration | ||
| 301 | |||
| 302 | === 9.3 Legal Disputes === | ||
| 303 | |||
| 304 | **Jurisdiction**: Swiss courts | ||
| 305 | **Applicable law**: Swiss law | ||
| 306 | **Venue**: Zürich | ||
| 307 | |||
| 308 | == 10. Succession Planning == | ||
| 309 | |||
| 310 | === 10.1 Governing Team Succession === | ||
| 311 | |||
| 312 | * Staggered terms (not all expire simultaneously) | ||
| 313 | * Nominating committee identifies candidates | ||
| 314 | * General Assembly elects | ||
| 315 | * Transitional handover period | ||
| 316 | |||
| 317 | === 10.2 Team Members Succession === | ||
| 318 | |||
| 319 | * Key staff document their processes | ||
| 320 | * Cross-training where possible | ||
| 321 | * External recruitment if needed | ||
| 322 | * Contractor support during transitions | ||
| 323 | |||
| 324 | === 10.3 Organizational Continuity === | ||
| 325 | |||
| 326 | * Documented procedures | ||
| 327 | * Automated systems reduce key person risk | ||
| 328 | * Regular backups and documentation | ||
| 329 | * Emergency response plan | ||
| 330 | |||
| 331 | == 11. Evolution & Adaptation == | ||
| 332 | |||
| 333 | === 11.1 Regular Reviews === | ||
| 334 | |||
| 335 | **Annually**: | ||
| 336 | |||
| 337 | * Structure assessment | ||
| 338 | * Process improvements | ||
| 339 | * Policy updates | ||
| 340 | * Strategic planning | ||
| 341 | **Periodically**: | ||
| 342 | * Comprehensive review | ||
| 343 | * Major reforms if needed | ||
| 344 | * Statutes amendments | ||
| 345 | |||
| 346 | === 11.2 Community Input === | ||
| 347 | |||
| 348 | * Open RFC (Request for Comments) process | ||
| 349 | * Public discussion forums | ||
| 350 | * Surveys and feedback | ||
| 351 | * Trial periods for major changes | ||
| 352 | |||
| 353 | === 11.3 Emergency Changes === | ||
| 354 | |||
| 355 | **Governing Team can act quickly** for: | ||
| 356 | |||
| 357 | * Security issues | ||
| 358 | * Legal compliance | ||
| 359 | * Critical bugs | ||
| 360 | * Abuse crises | ||
| 361 | **Must be ratified** by General Assembly at next meeting | ||
| 362 | |||
| 363 | == 12. Related Pages == | ||
| 364 | |||
| 365 | * [[Governance>>Archive.FactHarbor 2026\.02\.08.Organisation.Governance.WebHome]] | ||
| 366 | * [[Legal Framework>>FactHarbor.Organisation.Legal-Framework]] | ||
| 367 | * [[Open Source Model>>FactHarbor.Organisation.Open Source Model and Licensing]] | ||
| 368 | * [[Transparency Policy>>FactHarbor.Organisation.How-We-Work-Together.Transparency-Policy]] |