Skip to Content
Last modified by Robert Schaub on 2025/12/24 20:30
From version 7.1
edited by Robert Schaub
on 2025/11/26 07:19
Change comment: There is no comment for this version
To version 3.1
edited by Robert Schaub
on 2025/11/24 14:18
Change comment: There is no comment for this version

Summary

Details

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