Skip to Content

Wiki source code of Roles & Bodies

Last modified by Robert Schaub on 2025/12/18 12:03
Show last authors
1 = Roles & Bodies =
2 == 1. Overview ==
3 This page summarises the main roles and bodies that appear in the Organisation domain.
4 In a small organisation, one person may hold several of these roles at the same time.
5 == 2. Executive Roles (Leads) ==
6 * **Executive Lead** – Ensures coherence across all domains, oversees implementation of Governance decisions, and represents the organisation externally where appropriate.
7 * **Research & Development Lead** – Owns the technical architecture, data model, and quality of reasoning ALGORITHMS and models (the systems that evaluate claims, not the evaluation outputs).
8 * **Organisation Lead** – Maintains organisational documentation, governance rules, contributor processes, and the XWiki structure.
9 * **PR & Care & Marketing Lead** – Oversees communication, user support, campaigns, and community-facing material while respecting neutrality rules.
10 * **Finance & Compliance Lead** – Maintains the financial ledger, budgeting, reporting, and the conflict-of-interest register.
11 == 3. Governance Bodies ==
12 * **Governing Team** – Strategic oversight, compliance monitoring, and resolution of escalated issues.
13 * **Governance Steward** – Safeguards neutrality, transparency, and fairness of procedures.
14 == 4. Support Roles ==
15 Examples of support roles that may be added as the project grows:
16 * **Infrastructure Manager** – Coordinates hosting, deployment, monitoring, and backups.
17 * **Repository Steward** – Keeps repositories structured, tagged, and consistent.
18 * **Process Support Specialist** – Helps contributors follow defined workflows and improves processes.
19 * **Onboarding Coordinator** – Supports new contributors with documentation and introductory sessions.
20 == 5. Advisory Roles ==
21 * **Legal Advisor**
22 * **Ethics Advisor**
23 * **Scientific / Domain Advisors**
24 These advisory roles provide input and critique but do not replace the formal responsibilities of the Governing Team or Executives.
25 == 5.5 Domain Concept (from Sociocracy 3.0) ==
26 Each role has a **domain** - a clearly defined area of authority and responsibility.
27 **Domain definition includes**:
28 * **Purpose**: Why this domain exists
29 * **Responsibilities**: What this role is accountable for
30 * **Dependencies**: What this role needs from others
31 * **Authority**: What decisions this role can make autonomously
32 * **Constraints**: What boundaries limit this authority
33 **Examples**:
34 **Technical Coordinator Domain**:
35 * Purpose: Ensure AKEL performs optimally
36 * Responsibilities: System performance, infrastructure, algorithm improvements
37 * Dependencies: Performance metrics from monitoring, improvement suggestions from community
38 * Authority: Approve technical changes that don't affect policy
39 * Constraints: Must use consent-based decision for policy-affecting changes
40 **Community Coordinator Domain**:
41 * Purpose: Enable effective community contribution
42 * Responsibilities: Documentation, onboarding, feedback loops, community health
43 * Dependencies: User feedback, contribution patterns
44 * Authority: Approve community process changes
45 * Constraints: Cannot change technical systems or policies
46 **Key principle**: Clear domains prevent overlaps, enable autonomous decisions, and clarify escalation paths.
47 == 6. Principles for Role Design ==
48 * Responsibilities must be written down and accessible.
49 * The same person may hold several roles, but conflicts of interest must be declared.
50 * For sensitive areas (finance, governance, moderation) there should always be at least one other person able to review or approve critical actions.