Wiki source code of Governance & Open Source Model(from Gemini)
Version 7.1 by Robert Schaub on 2025/11/26 07:19
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
4.1 | 1 | = FactHarbor Open Source, Governance & Financing Model = |
| 2 | |||
| |
3.1 | 3 | == Version 0.1 (Draft) == |
| 4 | |||
| 5 | == 0. Overview == | ||
| |
4.1 | 6 | |
| |
3.1 | 7 | FactHarbor is a long-term public knowledge infrastructure. |
| 8 | |||
| 9 | Its governance model must ensure: | ||
| |
4.1 | 10 | |
| |
3.1 | 11 | * Integrity against manipulation |
| 12 | * Transparency of reasoning and code | ||
| 13 | * Longevity beyond any single founder | ||
| 14 | * Sustainability via realistic financing | ||
| 15 | * Openness without compromising trust | ||
| 16 | * Legal compliance under Swiss, EU, and US frameworks | ||
| 17 | |||
| 18 | This document defines the Open Source Model, Governance Model, and Financing Model across two phases: | ||
| |
4.1 | 19 | |
| |
5.1 | 20 | * Startup Phase — Founder-led, lightweight, flexible |
| 21 | * Non-Profit Organisation (Swiss Verein) Phase — Stable, community-governed, mission-locked | ||
| |
3.1 | 22 | |
| 23 | The transition is triggered by maturity and community growth, not a predetermined date. | ||
| 24 | |||
| 25 | == 1. Licensing Model == | ||
| |
4.1 | 26 | |
| |
3.1 | 27 | === 1.1 Open Source License — AGPLv3 === |
| |
4.1 | 28 | |
| |
3.1 | 29 | The GNU Affero General Public License v3 (AGPLv3) is selected because it: |
| |
4.1 | 30 | |
| |
3.1 | 31 | * Ensures full transparency of all server-side modifications |
| 32 | * Forces any fork or remote service to publish source code | ||
| 33 | * Protects against hidden logic changes (critical for truth-based systems) | ||
| 34 | * Allows commercial activity if and only if source modifications remain open | ||
| 35 | AGPLv3 is the strongest available license aligned with FactHarbor’s mission of trust, transparency, and manipulation resistance. | ||
| 36 | |||
| 37 | === 1.2 Branding, Attribution & Name Protection === | ||
| |
4.1 | 38 | |
| |
5.1 | 39 | * Trademark: FactHarbor name, logo, and brand elements are protected via trademark (held by Founder initially, then transferred to Verein). |
| 40 | * Purpose: Prevent malicious forks impersonating FactHarbor.' | ||
| 41 | * Attribution Guidelines (Non-Binding): FactHarbor requests (but does not require) that public-facing deployments display: “Powered by FactHarbor.” This is a guideline, fully compatible with AGPLv3. | ||
| |
3.1 | 42 | |
| 43 | == 2. Copyright, CLA & Intellectual Property == | ||
| |
4.1 | 44 | |
| |
3.1 | 45 | === 2.1 Copyright Ownership === |
| |
4.1 | 46 | |
| |
5.1 | 47 | * Startup Phase: Founder holds copyright to all FactHarbor code, AI templates, documentation, and assets. Third-party contributors retain copyright to their individual contributions. |
| 48 | * Non-Profit Phase: All relevant assets transfer to the Verein (see Section 3.2.3). | ||
| |
3.1 | 49 | |
| 50 | === 2.2 Contributor License Agreement (CLA) === | ||
| |
4.1 | 51 | |
| |
3.1 | 52 | All contributors must sign a CLA before contributions can be merged. The CLA states: |
| 53 | Contributors retain their original copyright, but they grant the FactHarbor Organization (Founder → later Swiss Verein): | ||
| |
4.1 | 54 | |
| |
5.1 | 55 | * A ''perpetual, worldwide, irrevocable, royalty-free license'' to use, modify, sublicense, and redistribute their contributions under AGPLv3. |
| 56 | * The ''explicit right to enforce AGPLv3'', including filing legal action against infringers, and defending license terms, acting on the contributor’s behalf where necessary. | ||
| |
3.1 | 57 | |
| 58 | === 2.3 Core Components and Enforcement === | ||
| |
4.1 | 59 | |
| |
5.1 | 60 | The organisation may optionally request a Copyright Assignment Agreement (CAA) for critical subsystems (e.g., the AKEL engine), but this is not required at this stage. |
| |
3.1 | 61 | |
| 62 | == 3. Governance Model == | ||
| |
4.1 | 63 | |
| |
5.1 | 64 | FactHarbor uses ''Stewardship Governance'' — where strategic control remains with a trusted core group to prevent hijacking and ensure mission alignment. |
| |
3.1 | 65 | |
| 66 | === 3.1 Startup Phase Governance === | ||
| |
4.1 | 67 | |
| |
5.1 | 68 | * Founder Leadership: Founder acts as Sole Maintainer, approves all merges, manages releases, and has final authority over technical and strategic decisions. The founder has legal responsibility. |
| 69 | * Core Team (Future Addition): The Founder may appoint trusted individuals. Security-sensitive changes require multi-party approval. | ||
| 70 | * Founder Succession Plan: Before transitioning, the Founder will define a succession mechanism in the Governance Charter (e.g., Founder-appointed successor, Steering Council ratification). | ||
| |
3.1 | 71 | |
| |
4.1 | 72 | === 3.2 Non-Profit Organisation (Swiss Verein) Governance === |
| |
3.1 | 73 | |
| |
4.1 | 74 | The transition occurs when FactHarbor reaches organisational maturity, forming a ''Swiss Verein'' with mission-driven statutes and no profit distribution allowed. |
| 75 | |||
| |
5.1 | 76 | * Governance Bodies: Includes the ''Steering Council'' (central decision-making), ''Core Maintainers'' (code review/merges), and ''Security Council" (security veto/audits). |
| 77 | * Founder’s Role After Transition: The Founder becomes a Permanent Steering Council member and strategic vision holder, but decisions follow the Governance Charter. | ||
| 78 | * Asset Transfer Protocol (Critical Legal Step): At the moment the Swiss Verein is formally created, a documented ''Asset Transfer Agreement'' is executed, conveying Copyright, Domains, Repositories, and Trademarks from the Founder to the Verein. |