Skip to Content

Wiki source code of License and Disclaimer

Version 1.1 by Robert Schaub on 2025/12/21 11:39
Hide last authors
Robert Schaub 1.1 1 = License and Disclaimer =
2
3 == 1. Overview ==
4
5 FactHarbor is an **open-source nonprofit project** committed to transparency, accessibility, and community collaboration. This page defines how FactHarbor resources are licensed and the conditions under which they may be used, modified, and distributed.
6
7 **FactHarbor operates under a multi-license model** designed to:
8
9 * Maximize reuse and adaptation of our work
10 * Maintain transparency and openness as core values
11 * Prevent proprietary capture of community-contributed work
12 * Enable broad ecosystem participation
13 * Protect the "FactHarbor" brand and methodology integrity
14
15 This page explains **how FactHarbor is run from a licensing and enforcement perspective** — as an open, trustworthy, non-profit oriented, but professionally maintained project.
16
17 Together with other Organisation pages, it defines **how FactHarbor is run**:
18
19 * [[Governance>>FactHarbor.Organisation.Governance.WebHome]] — who decides what, and under which principles
20 * [[Finance & Compliance>>FactHarbor.Organisation.Finance-Compliance]] — how funding, transparency, and internal controls work
21 * [[Legal Framework>>FactHarbor.Organisation.Legal-Framework]] — legal forms, contracts, and regulatory aspects
22
23 The **Specification** (Mission, Requirements, Architecture, Data Model, Workflows, etc.) describes **what FactHarbor does**.
24
25 This Open Source Model and Licensing page (together with Governance and Finance & Compliance) describes **how FactHarbor is run and protected**.
26
27 **Note:** Normative licensing decisions on this page **override** any older variants or drafts.
28
29 ---
30
31 == 2. Core Open Source Commitment ==
32
33 FactHarbor is, and will remain, an **open source project** that:
34
35 * Publishes its work openly whenever legally and ethically possible
36 * Makes its reasoning and evidence inspectable
37 * Invites contributions under clear, transparent rules
38 * Avoids situations where a "FactHarbor-branded" system becomes a black box
39 * Maintains exceptional organisational transparency to build trust
40
41 ---
42
43 == 3. Licensing (Current Decisions) ==
44
45 === 3.1 Documentation ===
46
47 All general **documentation** (organisational and technical) is licensed under:
48
49 * **[[Creative Commons Attribution-ShareAlike 4.0 International License (CC BY-SA 4.0)>>http://creativecommons.org/licenses/by-sa/4.0/]]**
50
51 This allows:
52
53 * Reuse, adaptation, and translation of documentation
54 * Including commercial reuse
55 * As long as:
56 ** Clear attribution to FactHarbor is preserved, and
57 ** Derivative works are shared under the **same license (CC BY-SA 4.0)**
58
59 **Exception handling:**
60
61 * In rare cases, **security-sensitive or abuse-enabling documentation** may be:
62 ** Published only in partial form, or
63 ** Made available under more restrictive terms, or
64 ** Kept internal
65 * Any such exceptions must be **explicitly documented** where they apply
66
67 === 3.2 Core Protocol & Data Model ===
68
69 The **core protocol**, core **data model** (including key ERDs), and other "defining specifications" are licensed under:
70
71 * **[[Creative Commons Attribution-ShareAlike 4.0 International License (CC BY-SA 4.0)>>http://creativecommons.org/licenses/by-sa/4.0/]]**
72
73 **Intent:**
74
75 * Enable **collaborative evolution** of the protocol and data model
76 * Allow broad reuse, referencing, and implementation
77 * Ensure derivative specifications remain open (share-alike requirement)
78 * Maintain canonical status through **trademark control** rather than license restrictions
79
80 **Implications:**
81
82 * You may **use, implement, and modify** the protocol/data model in your own systems
83 * You may **publish derivative or modified specifications** under CC BY-SA 4.0
84 * Derivative specifications must:
85 ** Be clearly attributed to FactHarbor
86 ** Use different branding/names (trademark protection)
87 ** State they are "derived from FactHarbor protocol"
88 ** Remain under CC BY-SA 4.0 (share-alike)
89 * Changes to the **canonical FactHarbor specification** are governed through FactHarbor's internal review and release processes
90
91 **Trademark Protection:**
92
93 The "FactHarbor" name and associated marks are protected separately from the license. Derivative protocols may not use "FactHarbor" branding without explicit permission, ensuring users can distinguish official from derivative implementations.
94
95 This approach (license for sharing + trademark for brand protection) follows successful models like Mozilla Firefox and the W3C.
96
97 === 3.3 Code ===
98
99 **Default License:** Unless explicitly stated otherwise, **code** produced under the FactHarbor project is licensed under:
100
101 * **[[MIT License>>https://opensource.org/licenses/MIT]]**
102
103 This allows:
104
105 * Broad reuse, including in commercial software
106 * Proprietary integrations and extensions
107 * As long as:
108 ** The MIT license text is included, and
109 ** Attribution to the FactHarbor project is preserved
110
111 **Hybrid Licensing for Core Components:**
112
113 For the **core reasoning engine** and **AKEL components**, we recommend using **[[GNU Affero General Public License v3.0 (AGPL-3.0)>>https://www.gnu.org/licenses/agpl-3.0.en.html]]** to prevent black-box deployments and ensure transparency of modifications.
114
115 **The recommended hybrid approach:**
116
117 * **AGPL-3.0** for:
118 ** Core verdict engine
119 ** AKEL reasoning logic
120 ** Scenario evaluation engine
121 * **MIT** for:
122 ** Integrations
123 ** Utilities
124 ** Frontend clients
125 ** Libraries
126 ** Tools
127
128 This hybrid model (similar to Wikimedia's use of AGPL for MediaWiki) balances maximum adoption with protection of the transparency mission.
129
130 **Rationale:**
131
132 * AGPL-3.0 is **network copyleft** — requires source disclosure for network services
133 * Prevents "FactHarbor-as-a-service" black boxes that contradict transparency mission
134 * MIT for peripheral components maximizes ecosystem growth
135 * Strong protection of **openness of reasoning** is handled via:
136 ** Open protocol and data model (CC BY-SA)
137 ** Open documentation (CC BY-SA)
138 ** AGPL for core reasoning components
139 ** Explicit transparency rules
140
141 The decision to implement this hybrid model should be made explicitly before the first public release.
142
143 === 3.4 Structured Data & Curation Artefacts ===
144
145 Structured data, curated knowledge artefacts and derived datasets are licensed under:
146
147 * **[[Open Database License (ODbL)>>https://opendatacommons.org/licenses/odbl/]]**
148
149 **Note on ODbL:** The Open Database License includes a share-alike requirement, ensuring derivative databases remain open. This aligns with FactHarbor's commitment to openness and prevents proprietary capture of community-curated data.
150
151 **Principles:**
152
153 * Data used for public reasoning should be:
154 ** Reusable and remixable
155 ** Properly attributed
156 ** Versioned and traceable
157 ** Kept open through share-alike
158 * Privacy, safety, and legal constraints may require:
159 ** Partial publication or anonymity
160 ** Stronger access control around certain datasets
161
162 Concrete exceptions and more restrictive handling must be **documented at dataset level**.
163
164 === 3.5 Attribution Guidelines (Non-Mandatory but Recommended) ===
165
166 FactHarbor encourages, but generally does not require beyond the base licenses, that:
167
168 * User interfaces show a short line such as:
169
170 {{code}}
171 Powered by FactHarbor (open documentation, open protocol, open data)
172 {{/code}}
173
174 **Intent:**
175
176 * Strengthen **brand recognition** and trust
177 * Keep attribution light-weight and compatible with open licenses
178 * Avoid creating extra legal conditions beyond the existing licenses
179
180 ---
181
182 == 4. Licensing Goals and Principles ==
183
184 Earlier "Open Source Model & Licensing" drafts contained valuable reasoning about **why** strong open-source protections might be needed. The core goals remain relevant, even though the exact license mix has evolved.
185
186 FactHarbor's licensing aims to:
187
188 * **Protect openness of reasoning**
189 ** Users must be able to understand how conclusions were reached
190 ** Code and documentation that materially affect user-visible behaviour should be inspectable or clearly described
191 * **Discourage hostile or misleading forks**
192 ** Avoid "closed clones" that keep the FactHarbor name or appearance while hiding important changes
193 ** Forks that significantly diverge should use their own branding and not pretend to be official FactHarbor instances
194 * **Make modifications traceable**
195 ** Substantial changes to code, specs, or governance documents should be documented and versioned
196 ** Users interacting with a service based on FactHarbor should be able to see **which version or fork** they are using
197 * **Support long-term sustainability and legal clarity**
198 ** Licenses and governance must be enforceable in practice
199 ** The organisation should have clear standing to protect the project if needed
200
201 ---
202
203 == 5. Contributors, Governance & CLA ==
204
205 === 5.1 Contributor Journey (from licensing perspective) ===
206
207 The contributor journey (Visitor → New Contributor → Contributor → Trusted Contributor → Moderator) is defined in more detail in the **Contributor Processes** and **Organisation** pages.
208
209 From a **licensing** perspective, the key points are:
210
211 * All contributions must be compatible with the chosen licenses (CC BY-SA, MIT, AGPL, ODbL, etc.)
212 * Contributors confirm that they have the right to contribute the material under these licenses
213 * Higher-trust roles (Trusted Contributors, Moderators) help enforce licensing and attribution rules when reviewing changes
214
215 For full role definitions, see the **Organisation / Contributor Processes** documentation.
216
217 === 5.2 Contributor License Agreement (CLA) ===
218
219 To keep the legal situation clear and enforceable, FactHarbor uses a **Contributor License Agreement (CLA)**.
220
221 See [[Contributor License Agreement>>FactHarbor.Organisation.CLA]].
222
223 ==== 5.2.1 Dual Contributor Model ====
224
225 FactHarbor distinguishes between two contributor types with different copyright arrangements:
226
227 **Unpaid Contributors (Volunteers):**
228
229 * **Retain copyright** of their contributions
230 * Grant FactHarbor a perpetual, royalty-free license to use and distribute
231 * Enable the project to enforce licenses on their behalf
232 * Maintain attribution in version control and documentation
233
234 **Paid Contributors (Employees, Contractors):**
235
236 * **Transfer copyright** to FactHarbor Organisation
237 * Ensures clear ownership for sponsored work
238 * Simplifies long-term governance
239 * Still receive attribution for their contributions
240
241 **This dual model:**
242
243 * Respects volunteer contributions while preserving their rights
244 * Provides clarity for commercially sponsored work
245 * Ensures FactHarbor can effectively maintain and defend the project
246 * Maintains transparency about contribution sources
247
248 ==== 5.2.2 Core Intent (All Contributors) ====
249
250 Regardless of contributor type, the CLA ensures:
251
252 * Contributors grant the **FactHarbor organisation**:
253 ** A **perpetual, worldwide, irrevocable license** to use, modify, and redistribute their contributions under the project's chosen licenses (CC BY-SA, MIT, AGPL, ODbL, etc.), and
254 ** The **express right to enforce** those licenses and **pursue legal action** against infringers on their behalf
255
256 This ensures that:
257
258 * The organisation has **clear standing** to defend the project legally
259 * Individual contributors do not have to act alone against infringements
260 * Licensing remains enforceable even if contributors become inactive
261
262 ==== 5.2.3 Determining Contributor Type ====
263
264 * **Default**: Contributors are considered unpaid volunteers unless they have a written agreement specifying paid status
265 * **Paid Status Indicators**: Employment contract, written contracting agreement, or grant/sponsorship agreement
266 * **Transparency**: Contributor type should be disclosed where applicable
267
268 See [[Contributor License Agreement>>FactHarbor.Organisation.CLA]] for complete terms.
269
270 ---
271
272 == 6. AI Models and Licensing (AKEL) ==
273
274 AKEL (AI Knowledge Extraction Layer) may rely on different types of models. Licensing and transparency rules are crucial here.
275
276 === 6.1 Open vs Proprietary Models ===
277
278 AKEL may use:
279
280 * **Open-source models (preferred)**:
281 ** Weights and code are openly available under compatible licenses
282 ** Prompts, evaluation logic and integration code are made public where licenses permit
283 * **Proprietary / hosted models (allowed but constrained)**:
284 ** Used only when necessary for quality or feasibility
285 ** Must be clearly **disclosed to the user** at point of use
286 ** AKEL must label which parts of its output derive from proprietary tools
287 ** Surrounding **integration logic remains open** (MIT/AGPL or compatible) and is documented
288
289 **Rules:**
290
291 * No deployment may suggest "fully open" AI if proprietary models are used without disclosure
292 * For high-impact reasoning (e.g. health, politics, safety-critical topics), **open, auditable models** are preferred wherever feasible
293 * Where proprietary models are unavoidable, additional care is taken to:
294 ** Document limitations
295 ** Avoid overstating certainty
296 ** Keep reasoning layers as transparent as possible
297
298 === 6.2 Prompts, Pipelines and Integration Code ===
299
300 * Orchestration code, pipelines and evaluation logic around AKEL are treated as part of the **open FactHarbor codebase** (MIT or AGPL)
301 * Where prompts or model configurations are licensed in a way that restricts publication, this must be documented clearly, and safe abstractions should be used in public documentation
302
303 === 6.3 AI Prompts and Orchestration ===
304
305 * Prompts, system instructions, and orchestration code are considered **Code** and licensed under **MIT** or **AGPL** (depending on component)
306 * They must be visible in the repository to ensure the system is not a 'black box'
307 * If a proprietary model requires a prompt that cannot be shared (e.g. contractual restriction), that component cannot be part of the open core
308
309 ---
310
311 == 7. Third-Party Libraries and Components ==
312
313 FactHarbor depends on third-party libraries under:
314
315 * Permissive licenses (MIT, Apache-2.0, BSD), and/or
316 * Other compatible open-source licenses
317
318 **Requirements:**
319
320 * All dependencies must be **license-compatible** with:
321 ** The MIT/AGPL-licensed code, and
322 ** The overall FactHarbor licensing strategy
323 * License information is documented in:
324 ** `/LICENSE` and, where applicable, `/NOTICE`
325 ** A dedicated "Third-Party Licenses" section in project documentation
326
327 FactHarbor actively avoids dependencies that:
328
329 * Restrict redistribution in ways incompatible with open-source norms
330 * Prevent network users from accessing the relevant source
331 * Conflict with the project's transparency and licensing goals
332
333 ---
334
335 == 8. Repository Standards ==
336
337 Each official FactHarbor repository must follow a minimum standard.
338
339 === 8.1 Required Files ===
340
341 Each repository should contain at least:
342
343 * **README** — purpose, scope, status, and how to use it
344 * **LICENSE** — the applicable license(s) for the repository
345 * **CONTRIBUTING** — how to propose changes; coding/writing guidelines
346 * **CODEOWNERS** — who is responsible for which parts
347 * **CHANGELOG** — human-readable log of important changes
348 * **SECURITY** (or SECURITY.md) — how to report vulnerabilities and how they are handled
349
350 === 8.2 Prohibited Content ===
351
352 FactHarbor repositories must **not** contain:
353
354 * Purely ideological advocacy texts unrelated to the project's purpose
355 * Opaque binaries or artefacts that cannot reasonably be inspected or reproduced
356 * Embedded secrets (API keys, passwords, private tokens)
357 * Content that materially contradicts the stated licenses or governance rules
358
359 ---
360
361 == 9. Attribution of Derivative Works ==
362
363 If you create a derivative work based on FactHarbor materials, please attribute it as follows:
364
365 === Documentation & Specifications (CC BY-SA 4.0) ===
366
367 {{code}}
368 This work, '[Your Work Name]', is a derivative of 'FactHarbor' by Robert Schaub
369 and the FactHarbor community. '[Your Work Name]' is licensed under CC BY-SA 4.0
370 by [Your Name].
371 {{/code}}
372
373 === Code - MIT Licensed Components ===
374
375 {{code}}
376 Based on FactHarbor by Robert Schaub and contributors
377 Licensed under MIT License
378 Original source: https://github.com/factharbor/[repository-name]
379 {{/code}}
380
381 === Code - AGPL Licensed Components (Core Engine) ===
382
383 {{code}}
384 Based on FactHarbor Core Engine by Robert Schaub and contributors
385 Licensed under GNU AGPL v3.0
386 Source code available at: https://github.com/factharbor/[repository-name]
387 {{/code}}
388
389 === Databases (ODbL) ===
390
391 {{code}}
392 This database is derived from FactHarbor curated data by Robert Schaub
393 and the FactHarbor community. Licensed under ODbL by [Your Name].
394 {{/code}}
395
396 Please replace placeholders like '[Your Work Name]' and '[Your Name]' with actual values.
397
398 ---
399
400 == 10. Organisational Transparency ==
401
402 FactHarbor is committed to exceptional transparency in all aspects of its operations, governance, and finances. This commitment is essential to build trust in a system claiming to support well-grounded judgments.
403
404 === 10.1 Financial Transparency ===
405
406 We commit to publishing annually:
407
408 * Complete financial statements (audited where possible)
409 * Swiss tax filings (annual statements per Swiss law)
410 * Income sources in aggregate (grants, donations, sponsorships)
411 * Expense breakdown by category
412 * Compensation ranges for staff roles (not individual salaries)
413 * Major funding relationships and partnerships
414
415 === 10.2 Governance Transparency ===
416
417 We commit to publishing:
418
419 * All governance documents (bylaws, policies, procedures)
420 * Governing Team composition and meeting schedules
421 * Governing Team meeting minutes (with narrow exceptions for privacy, security, or legal matters)
422 * Policy changes with rationale and effective dates
423 * Decision-making process documentation
424 * Conflict of interest policies and disclosures
425
426 === 10.3 Operational Transparency ===
427
428 We commit to publishing:
429
430 * Transparency reports (published twice yearly)
431 * Content moderation statistics and practices
432 * AKEL performance metrics and audit results
433 * Risk tier assignment statistics
434 * Partnership agreements and funding relationships
435 * Incident reports (security, moderation, governance)
436 * System uptime and performance data
437
438 === 10.4 Privacy Protection ===
439
440 While maintaining organisational transparency, we protect:
441
442 * Individual user privacy and personal data
443 * Security vulnerabilities (until patched, typically 30-90 days)
444 * Personnel matters and personal information
445 * Ongoing legal matters (until resolved)
446 * Whistleblower and abuse reports
447 * Authentication credentials and sensitive operational details
448
449 === 10.5 Review and Oversight ===
450
451 * Annual review of all information marked "private"
452 * Public reporting on transparency compliance
453 * Community input opportunities on transparency policies
454 * Appeals process for information requests
455 * Independent transparency audits (when feasible)
456
457 See [[Transparency Policy>>FactHarbor.Organisation.How-We-Work-Together.Transparency-Policy]] for complete details.
458
459 ---
460
461 == 11. Legal Disclaimer ==
462
463 === 11.1 No Liability for Results ===
464
465 The materials, tools, and resources provided by FactHarbor can be used by any entity or organization.
466
467 **The creators, contributors, and maintainers of FactHarbor are not liable for:**
468
469 * The achievement of certain objectives or results by entities/organizations using FactHarbor materials
470 * Decisions made based on FactHarbor analyses or outputs
471 * Errors, inaccuracies, or incompleteness in analyses or data
472 * Any direct, indirect, incidental, special, consequential, or punitive damages
473
474 === 11.2 "As Is" Service ===
475
476 FactHarbor is provided **"AS IS"** without warranty of any kind, either express or implied, including but not limited to:
477
478 * Warranties of merchantability
479 * Fitness for a particular purpose
480 * Non-infringement
481 * Accuracy or completeness
482
483 === 11.3 Content Accuracy ===
484
485 * We do not guarantee the accuracy of user-submitted content
486 * Evaluations represent community assessments, not absolute truth
487 * Use your own judgment when relying on information
488
489 === 11.4 Availability ===
490
491 We do not guarantee uninterrupted or error-free service.
492
493 === 11.5 Educational and Informational Purpose ===
494
495 FactHarbor analyses, verdicts, and evidence models are intended for **educational and informational purposes only**. They should not be considered as:
496
497 * Professional advice (legal, medical, financial, or otherwise)
498 * Definitive truth or final judgments
499 * Replacements for independent verification and critical thinking
500 * Absolute or infallible assessments
501
502 **Users are encouraged to:**
503
504 * Verify information independently
505 * Consult qualified professionals when appropriate
506 * Apply critical thinking and judgment
507 * Understand the limitations and assumptions of AI-generated analyses
508
509 ---
510
511 == 12. Privacy and Data Handling ==
512
513 * **User Privacy**: FactHarbor respects user privacy and handles personal data in accordance with applicable privacy laws (Swiss FADP, EU GDPR)
514 * **Transparency**: Data processing practices are documented and publicly available
515 * **No Hidden Data Collection**: All data collection and usage is clearly disclosed
516
517 See [[Privacy Policy>>FactHarbor.Organisation.How-We-Work-Together.Privacy-Policy]] for complete details.
518
519 ---
520
521 == 13. Third-Party Content and AI Models ==
522
523 * **AI-Generated Content**: Some FactHarbor outputs are generated using AI models (AKEL system)
524 ** Proprietary models (where used) are clearly disclosed at point of use
525 ** AI-generated content is marked with **AuthorType = AI**
526 * **Web Search Results**: Evidence may be sourced from third-party websites and search results
527 * **No Endorsement**: Inclusion of third-party content does not constitute endorsement
528 * **Third-Party Licenses**: External content remains subject to its original licensing terms
529
530 ---
531
532 == 14. Limitation of Liability ==
533
534 To the maximum extent permitted by law, FactHarbor and its operators shall not be liable for any indirect, incidental, special, consequential, or punitive damages.
535
536 ---
537
538 == 15. Governing Law ==
539
540 These licensing terms and disclaimers are governed by **Swiss law**. Disputes will be resolved under Swiss jurisdiction.
541
542 ---
543
544 == 16. Changes to License Terms ==
545
546 FactHarbor reserves the right to update these license terms. Any changes will be:
547
548 * Documented with clear versioning
549 * Announced to the community
550 * Applied prospectively (existing content remains under original terms unless explicitly migrated)
551
552 Material changes will be announced with reasonable notice.
553
554 ---
555
556 == 17. Contact and Questions ==
557
558 For questions about licensing, attribution, or use of FactHarbor materials:
559
560 * **Project Website**: [[https://schaubgroup.ch/bin/view/FactHarbor/]]
561 * **Licensing Questions**: [Contact information to be established]
562 * **General Questions**: [Contact information to be established]
563
564 ---
565
566 == 18. Related Policies ==
567
568 * [[Privacy Policy>>FactHarbor.Organisation.How-We-Work-Together.Privacy-Policy]]
569 * [[Terms of Service>>FactHarbor.Organisation.How-We-Work-Together.Terms-of-Service]]
570 * [[Transparency Policy>>FactHarbor.Organisation.How-We-Work-Together.Transparency-Policy]]
571 * [[Security Policy>>FactHarbor.Organisation.How-We-Work-Together.Security-Policy]]
572 * [[Contributor License Agreement>>FactHarbor.Organisation.CLA]]
573 * [[Governance>>FactHarbor.Organisation.Governance.WebHome]]
574 * [[Finance & Compliance>>FactHarbor.Organisation.Finance-Compliance]]
575
576 ---
577
578 **© 2024-2025 by Robert Schaub and the FactHarbor Community**
579
580 **FactHarbor** is a registered trademark. Use of the FactHarbor name and logo requires explicit permission.
581
582 ---
583
584 == License Summary Table ==
585
586 | **Content Type** | **License** | **Key Principle** |
587 |---|---|---|
588 | Documentation | CC BY-SA 4.0 | Share openly, attribute, share-alike |
589 | Protocol & Data Model | CC BY-SA 4.0 | Open specifications, trademark-protected brand |
590 | Code (Default) | MIT | Maximum reuse, minimal restrictions |
591 | Code (Core Engine/AKEL) | AGPL-3.0 | Network transparency, prevent black boxes |
592 | Structured Data | ODbL | Open data, share-alike for databases |
593
594 ---
595
596 **FactHarbor Mission**: Bring clarity and transparency to unclear, controversial, and misleading information by shedding light on the context, assumptions, and evidence behind claims.
597
598 **Core Values:**
599
600 * 🌍 **Non-profit organization** – No commercial interests
601 * 📖 **Fully open source** – All code and methodology public
602 * 🔍 **Complete transparency** – No hidden algorithms
603 * 🆓 **Accessible to everyone** – No paywalls or restrictions
604
605 ---
606
607 **Version:** Based on FactHarbor V0.9.69
608 **Status:** Draft - To be finalized before launch