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