Organisation

This section describes how FactHarbor operates as an organization.

1. Core Philosophy

Automation Philosophy 

• AKEL is primary, humans monitor and improve
• Fix the system, not the data
• Scale through automation, not people

2. Governance & Decision Making

Governance

• Organizational structure (Verein, Governing Team, Team Members)
• Automation governance (what AKEL decides vs humans)
• Financial governance
  Decision Processes
• Types of decisions (strategic, tactical, operational)
• Automation boundary
• Escalation paths
  Consent-Based Decision Making 
• Sociocracy 3.0 pattern for system changes
• Consent vs consensus
• Process steps and examples

3. Team & Roles

Organisational Model

• Legal structure (Swiss Verein)
• Team structure (minimal, automation-first)
• Roles and responsibilities
  Roles & Bodies
• Executive roles and governance bodies
• Domain ownership (S3 pattern)
• Support and advisory roles

4. Contributors & Community

Contributor Processes

• How to improve the SYSTEM (not review content)
• RFC workflow
• Contributor roles and trust levels
• Quality standards

5. How We Work Together

How We Work Together

Culture & Values

Workplace Culture

• Best Workplace Blueprint principles
• Sociocracy 3.0 integration
• AI-first culture
• How we work together
  Continuous Improvement
• Improvement cycle (observe → analyze → test → deploy)
• Sprint, quarterly, annual cadence
• Retrospectives and learning
  Consent-Based Decision Making
• Sociocracy 3.0 pattern for system changes
• Consent vs consensus
• Process steps and examples

Guidelines & Policies

Global Rules

• Evidence evaluation rules
• Risk tier definitions
• Source scoring criteria
  Terms of Service
  Privacy Policy
  Transparency Policy
  Security Policy

6. Policies & Compliance

7. Operational Readiness

Operational Readiness Checklist

• Pre-launch requirements
• Technical readiness
• Legal and financial readiness
• Operational readiness
  Transition Model
• From development to operations
• Phased rollout

8. Supporting Documents

Global Rules

• Evidence evaluation rules
• Risk tier definitions
• Source scoring criteria
  Open Source Model and Licensing
• Open source philosophy
• Licensing choices
• Community governance
  Contributor License Agreement
• CLA terms
• IP assignment

9. Domain Knowledge

Core Problems FactHarbor Solves

• Information overload
• Trust and credibility issues
• Context collapse
• Source reliability

10. Visual Diagrams

Diagrams

• Governance Structure
• Domain Interaction Map
• Claim and Scenario Lifecycle
  -

Key Principles

Automation First

• AKEL makes content decisions
• Humans improve algorithms
• Scale through code, not people

Continuous Improvement

• Measure everything
• Test before deploying
• Learn from failures
• Iterate rapidly

Transparency

• Open decisions
• Public metrics
• Documented rationale
• Auditable code

Empowerment

• Clear domains
• Autonomous decisions
• Support and resources
• Trust by default

User Focus

• Serve users' needs
• Protect privacy
• Build trust
• Enable informed decisions
  -