Wiki source code of Organisation
Last modified by Robert Schaub on 2026/02/08 21:33
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | = Organisation = |
| |
1.3 | 2 | |
| |
1.1 | 3 | This section describes **how FactHarbor operates** as an organization. |
| |
1.3 | 4 | |
| |
1.1 | 5 | == 1. Core Philosophy == |
| |
1.3 | 6 | |
| |
1.1 | 7 | **[[Automation Philosophy>>FactHarbor.Organisation.Automation-Philosophy]]** * AKEL is primary, humans monitor and improve |
| |
1.3 | 8 | |
| |
1.1 | 9 | * Fix the system, not the data |
| 10 | * Scale through automation, not people | ||
| |
1.3 | 11 | |
| |
1.1 | 12 | == 2. Governance & Decision Making == |
| |
1.3 | 13 | |
| |
1.20 | 14 | **[[Governance>>Archive.FactHarbor.Organisation.Governance.WebHome]]** |
| |
1.3 | 15 | |
| |
1.1 | 16 | * Organizational structure (Verein, Governing Team, Team Members) |
| 17 | * Automation governance (what AKEL decides vs humans) | ||
| 18 | * Financial governance | ||
| 19 | **[[Decision Processes>>FactHarbor.Organisation.Decision-Processes]]** | ||
| 20 | * Types of decisions (strategic, tactical, operational) | ||
| 21 | * Automation boundary | ||
| 22 | * Escalation paths | ||
| 23 | **[[Consent-Based Decision Making>>FactHarbor.Organisation.How-We-Work-Together.Consent-Based-Decision-Making]]** * Sociocracy 3.0 pattern for system changes | ||
| 24 | * Consent vs consensus | ||
| 25 | * Process steps and examples | ||
| |
1.3 | 26 | |
| |
1.1 | 27 | == 3. Team & Roles == |
| |
1.3 | 28 | |
| |
1.1 | 29 | **[[Organisational Model>>FactHarbor.Organisation.Organisational-Model]]** |
| |
1.3 | 30 | |
| |
1.1 | 31 | * Legal structure (Swiss Verein) |
| 32 | * Team structure (minimal, automation-first) | ||
| 33 | * Roles and responsibilities | ||
| 34 | **[[Roles & Bodies>>FactHarbor.Organisation.Roles-Bodies]]** | ||
| 35 | * Executive roles and governance bodies | ||
| 36 | * Domain ownership (S3 pattern) | ||
| 37 | * Support and advisory roles | ||
| |
1.3 | 38 | |
| |
1.1 | 39 | == 4. Contributors & Community == |
| |
1.3 | 40 | |
| |
1.1 | 41 | **[[Contributor Processes>>FactHarbor.Organisation.Contributor-Processes]]** |
| |
1.3 | 42 | |
| |
1.1 | 43 | * How to improve the SYSTEM (not review content) |
| 44 | * RFC workflow | ||
| 45 | * Contributor roles and trust levels | ||
| 46 | * Quality standards | ||
| |
1.3 | 47 | |
| |
1.1 | 48 | == 5. How We Work Together == |
| |
1.3 | 49 | |
| |
1.22 | 50 | **[[How We Work Together>>Archive.FactHarbor.Organisation.How-We-Work-Together.WebHome]]** |
| |
1.3 | 51 | |
| |
1.1 | 52 | === Culture & Values === |
| |
1.3 | 53 | |
| |
1.1 | 54 | **[[Workplace Culture>>FactHarbor.Organisation.How-We-Work-Together.Workplace-Culture]]** |
| |
1.3 | 55 | |
| |
1.1 | 56 | * Best Workplace Blueprint principles |
| 57 | * Sociocracy 3.0 integration | ||
| 58 | * AI-first culture | ||
| 59 | * How we work together | ||
| 60 | **[[Continuous Improvement>>FactHarbor.Organisation.How-We-Work-Together.Continuous-Improvement]]** | ||
| 61 | * Improvement cycle (observe → analyze → test → deploy) | ||
| 62 | * Sprint, quarterly, annual cadence | ||
| 63 | * Retrospectives and learning | ||
| 64 | **[[Consent-Based Decision Making>>FactHarbor.Organisation.How-We-Work-Together.Consent-Based-Decision-Making]]** | ||
| 65 | * Sociocracy 3.0 pattern for system changes | ||
| 66 | * Consent vs consensus | ||
| 67 | * Process steps and examples | ||
| |
1.3 | 68 | |
| |
1.1 | 69 | === Guidelines & Policies === |
| |
1.3 | 70 | |
| |
1.21 | 71 | **[[Global Rules>>Archive.FactHarbor.Organisation.How-We-Work-Together.GlobalRules.WebHome]]** |
| |
1.3 | 72 | |
| |
1.1 | 73 | * Evidence evaluation rules |
| 74 | * Risk tier definitions | ||
| 75 | * Source scoring criteria | ||
| 76 | **[[Terms of Service>>FactHarbor.Organisation.How-We-Work-Together.Terms-of-Service]]** | ||
| 77 | **[[Privacy Policy>>FactHarbor.Organisation.How-We-Work-Together.Privacy-Policy]]** | ||
| 78 | **[[Transparency Policy>>FactHarbor.Organisation.How-We-Work-Together.Transparency-Policy]]** | ||
| 79 | **[[Security Policy>>FactHarbor.Organisation.How-We-Work-Together.Security-Policy]]** | ||
| |
1.3 | 80 | |
| |
1.1 | 81 | == 6. Policies & Compliance == |
| |
1.3 | 82 | |
| |
1.1 | 83 | == 7. Operational Readiness == |
| |
1.3 | 84 | |
| |
1.1 | 85 | **[[Operational Readiness Checklist>>FactHarbor.Organisation.Operational-Readiness-Checklist]]** |
| |
1.3 | 86 | |
| |
1.1 | 87 | * Pre-launch requirements |
| 88 | * Technical readiness | ||
| 89 | * Legal and financial readiness | ||
| 90 | * Operational readiness | ||
| 91 | **[[Transition Model>>FactHarbor.Organisation.Transition-Model]]** | ||
| 92 | * From development to operations | ||
| 93 | * Phased rollout | ||
| |
1.3 | 94 | |
| |
1.1 | 95 | == 8. Supporting Documents == |
| |
1.3 | 96 | |
| |
1.21 | 97 | **[[Global Rules>>Archive.FactHarbor.Organisation.How-We-Work-Together.GlobalRules.WebHome]]** |
| |
1.3 | 98 | |
| |
1.1 | 99 | * Evidence evaluation rules |
| 100 | * Risk tier definitions | ||
| 101 | * Source scoring criteria | ||
| 102 | **[[Open Source Model and Licensing>>FactHarbor.Organisation.Open Source Model and Licensing]]** | ||
| 103 | * Open source philosophy | ||
| 104 | * Licensing choices | ||
| 105 | * Community governance | ||
| 106 | **[[Contributor License Agreement>>FactHarbor.Organisation.CLA]]** | ||
| 107 | * CLA terms | ||
| 108 | * IP assignment | ||
| |
1.3 | 109 | |
| |
1.1 | 110 | == 9. Domain Knowledge == |
| |
1.3 | 111 | |
| |
1.18 | 112 | **[[Core Problems FactHarbor Solves>>Archive.FactHarbor.Organisation.Core Problems FactHarbor Solves.WebHome]]** |
| |
1.3 | 113 | |
| |
1.1 | 114 | * Information overload |
| 115 | * Trust and credibility issues | ||
| 116 | * Context collapse | ||
| 117 | * Source reliability | ||
| |
1.3 | 118 | |
| |
1.1 | 119 | == 10. Visual Diagrams == |
| |
1.3 | 120 | |
| |
1.19 | 121 | **[[Diagrams>>Archive.FactHarbor.Organisation.Diagrams.WebHome]]** |
| |
1.3 | 122 | |
| |
1.1 | 123 | * Governance Structure |
| 124 | * Domain Interaction Map | ||
| 125 | * Claim and Scenario Lifecycle == Key Principles == | ||
| |
1.3 | 126 | |
| |
1.1 | 127 | ==== Automation First ==== |
| |
1.3 | 128 | |
| |
1.1 | 129 | * AKEL makes content decisions |
| 130 | * Humans improve algorithms | ||
| 131 | * Scale through code, not people | ||
| |
1.3 | 132 | |
| |
1.1 | 133 | ==== Continuous Improvement ==== |
| |
1.3 | 134 | |
| |
1.1 | 135 | * Measure everything |
| 136 | * Test before deploying | ||
| 137 | * Learn from failures | ||
| 138 | * Iterate rapidly | ||
| |
1.3 | 139 | |
| |
1.1 | 140 | ==== Transparency ==== |
| |
1.3 | 141 | |
| |
1.1 | 142 | * Open decisions |
| 143 | * Public metrics | ||
| 144 | * Documented rationale | ||
| 145 | * Auditable code | ||
| |
1.3 | 146 | |
| |
1.1 | 147 | ==== Empowerment ==== |
| |
1.3 | 148 | |
| |
1.1 | 149 | * Clear domains |
| 150 | * Autonomous decisions | ||
| 151 | * Support and resources | ||
| 152 | * Trust by default | ||
| |
1.3 | 153 | |
| |
1.1 | 154 | ==== User Focus ==== |
| |
1.3 | 155 | |
| |
1.1 | 156 | * Serve users' needs |
| 157 | * Protect privacy | ||
| 158 | * Build trust | ||
| 159 | * Enable informed decisions |