Skip to Content
Last modified by Robert Schaub on 2025/12/24 20:30
From version 4.1
edited by Robert Schaub
on 2025/11/25 17:37
Change comment: There is no comment for this version
To version 8.2
edited by Robert Schaub
on 2025/12/11 11:05
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -FactHarbor Open Source, Governance & Financing Model (from Gemini)
1 +Governance & Open Source Model (from Gemini)
Parent
... ... @@ -1,1 +1,1 @@
1 -FactHarbor.Playground.WebHome
1 +FactHarbor.Playground.FactHarbor.Playground.WebHome
Content
... ... @@ -17,8 +17,8 @@
17 17  
18 18  This document defines the Open Source Model, Governance Model, and Financing Model across two phases:
19 19  
20 -* '''Startup Phase''' — Founder-led, lightweight, flexible
21 -* '''Non-Profit Organisation (Swiss Verein) Phase''' — Stable, community-governed, mission-locked
20 +* Startup Phase — Founder-led, lightweight, flexible
21 +* Non-Profit Organisation (Swiss Verein) Phase — Stable, community-governed, mission-locked
22 22  
23 23  The transition is triggered by maturity and community growth, not a predetermined date.
24 24  
... ... @@ -36,15 +36,16 @@
36 36  
37 37  === 1.2 Branding, Attribution & Name Protection ===
38 38  
39 -* '''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.''
40 -* '''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.
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.
41 41  
42 42  == 2. Copyright, CLA & Intellectual Property ==
43 43  
44 44  === 2.1 Copyright Ownership ===
45 45  
46 -* '''Startup Phase:''' Founder holds copyright to all FactHarbor code, AI templates, documentation, and assets. Third-party contributors retain copyright to their individual contributions.
47 -* '''Non-Profit Phase:''' All relevant assets transfer to the Verein (see Section 3.2.3).
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).
48 48  
49 49  === 2.2 Contributor License Agreement (CLA) ===
50 50  
... ... @@ -51,27 +51,27 @@
51 51  All contributors must sign a CLA before contributions can be merged. The CLA states:
52 52  Contributors retain their original copyright, but they grant the FactHarbor Organization (Founder → later Swiss Verein):
53 53  
54 -* A '''perpetual, worldwide, irrevocable, royalty-free license''' to use, modify, sublicense, and redistribute their contributions under AGPLv3.
55 -* The '''explicit right to enforce AGPLv3''', including filing legal action against infringers and defending license terms, acting on the contributor’s behalf where necessary.
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.
56 56  
57 57  === 2.3 Core Components and Enforcement ===
58 58  
59 -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.
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.
60 60  
61 61  == 3. Governance Model ==
62 62  
63 -FactHarbor uses '''Stewardship Governance''' — where strategic control remains with a trusted core group to prevent hijacking and ensure mission alignment.
64 +FactHarbor uses ''Stewardship Governance'' — where strategic control remains with a trusted core group to prevent hijacking and ensure mission alignment.
64 64  
65 65  === 3.1 Startup Phase Governance ===
66 66  
67 -* '''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.
68 -* '''3.1.2 Core Team (Future Addition):''' The Founder may appoint trusted individuals. Security-sensitive changes require multi-party approval.
69 -* '''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).
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).
70 70  
71 71  === 3.2 Non-Profit Organisation (Swiss Verein) Governance ===
72 72  
73 73  The transition occurs when FactHarbor reaches organisational maturity, forming a ''Swiss Verein'' with mission-driven statutes and no profit distribution allowed.
74 74  
75 -* '''3.2.1 Governance Bodies:''' Includes the '''Steering Council''' (central decision-making), '''Core Maintainers''' (code review/merges), and '''Security Council''' (security veto/audits).
76 -* '''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.
77 -* '''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.
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.