Wiki source code of Governance
Version 2.1 by Robert Schaub on 2025/12/14 18:59
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | = Governance = |
| 2 | |||
| |
2.1 | 3 | FactHarbor is governed collaboratively with clear separation between **organizational policy and decisions** and **technical implementation**. |
| |
1.1 | 4 | |
| |
2.1 | 5 | == Governance Structure == |
| |
1.1 | 6 | |
| |
2.1 | 7 | * **Governing Team** – Sets high-level policy, organizational direction, funding priorities |
| 8 | * **Lead** – Coordinates execution, represents organization publicly | ||
| 9 | * **Core Maintainers** – Technical and specification decisions, code/spec review | ||
| 10 | * **Domain Experts** – Subject-matter authority in specialized areas | ||
| 11 | * **Community Contributors** – Feedback, proposals, and participation in decision-making | ||
| |
1.1 | 12 | |
| |
2.1 | 13 | ---- |
| |
1.1 | 14 | |
| |
2.1 | 15 | == Decision-Making Levels == |
| |
1.1 | 16 | |
| |
2.1 | 17 | === Technical Decisions (Maintainers) === |
| |
1.1 | 18 | |
| |
2.1 | 19 | **Scope**: Architecture, data model, AKEL configuration, quality gates, system performance |
| |
1.1 | 20 | |
| |
2.1 | 21 | **Process**: |
| 22 | * Proposals discussed in technical forums | ||
| 23 | * Review by core maintainers | ||
| 24 | * Consensus-based approval | ||
| 25 | * Breaking changes require broader community input | ||
| 26 | * Quality gate adjustments require rationale and audit validation | ||
| |
1.1 | 27 | |
| |
2.1 | 28 | **Examples**: |
| 29 | * Adding new quality gate | ||
| 30 | * Adjusting AKEL parameters | ||
| 31 | * Modifying audit sampling algorithms | ||
| 32 | * Database schema changes | ||
| |
1.1 | 33 | |
| |
2.1 | 34 | === Policy Decisions (Governing Team + Community) === |
| |
1.1 | 35 | |
| |
2.1 | 36 | **Scope**: Risk tier policies, publication rules, content guidelines, ethical boundaries |
| |
1.1 | 37 | |
| |
2.1 | 38 | **Process**: |
| 39 | * Proposal published for community feedback | ||
| 40 | * Discussion period (recommendation: minimum 14 days for major changes) | ||
| 41 | * Governing Team decision with community input | ||
| 42 | * Transparency in reasoning | ||
| 43 | * Risk tier policy changes require Expert consultation | ||
| |
1.1 | 44 | |
| |
2.1 | 45 | **Examples**: |
| 46 | * Defining Tier A domains | ||
| 47 | * Setting audit sampling rates | ||
| 48 | * Content moderation policies | ||
| 49 | * Community guidelines | ||
| |
1.1 | 50 | |
| |
2.1 | 51 | === Domain-Specific Decisions (Experts) === |
| |
1.1 | 52 | |
| |
2.1 | 53 | **Scope**: Domain quality standards, source reliability in specialized fields, Tier A content validation |
| |
1.1 | 54 | |
| |
2.1 | 55 | **Process**: |
| 56 | * Expert consensus in domain | ||
| 57 | * Documented reasoning | ||
| 58 | * Review by other experts | ||
| 59 | * Escalation to Governing Team if unresolved | ||
| 60 | * Experts set domain-specific audit criteria | ||
| |
1.1 | 61 | |
| |
2.1 | 62 | **Examples**: |
| 63 | * Medical claim evaluation standards | ||
| 64 | * Legal citation requirements | ||
| 65 | * Scientific methodology thresholds | ||
| 66 | * Tier A approval criteria by domain | ||
| |
1.1 | 67 | |
| |
2.1 | 68 | ---- |
| |
1.1 | 69 | |
| |
2.1 | 70 | == AI and Human Roles in Governance == |
| |
1.1 | 71 | |
| |
2.1 | 72 | === Human-Only Governance Decisions === |
| |
1.1 | 73 | |
| |
2.1 | 74 | The following can **never** be automated: |
| |
1.1 | 75 | |
| |
2.1 | 76 | * **Ethical boundary setting** – What content is acceptable, what harm thresholds exist |
| 77 | * **Risk tier policy** – Which domains are Tier A/B/C (though AKEL can suggest) | ||
| 78 | * **Audit system oversight** – Quality standards, sampling strategies, auditor selection | ||
| 79 | * **Dispute resolution** – Conflicts between experts, controversial decisions | ||
| 80 | * **Community guidelines enforcement** – Bans, suspensions, conflict mediation | ||
| 81 | * **Organizational direction** – Mission, vision, funding priorities | ||
| |
1.1 | 82 | |
| |
2.1 | 83 | === AKEL Advisory Role === |
| |
1.1 | 84 | |
| |
2.1 | 85 | AKEL can **assist but not decide**: |
| |
1.1 | 86 | |
| |
2.1 | 87 | * Suggest risk tier assignments (humans validate) |
| 88 | * Flag content for expert review (humans decide) | ||
| 89 | * Identify patterns in audit failures (humans adjust policy) | ||
| 90 | * Propose quality gate refinements (maintainers approve) | ||
| 91 | * Detect emerging topics needing new policies (Governing Team decides) | ||
| |
1.1 | 92 | |
| |
2.1 | 93 | === Transparency Requirement === |
| |
1.1 | 94 | |
| |
2.1 | 95 | All governance decisions must be: |
| 96 | * **Documented** with reasoning | ||
| 97 | * **Published** for community visibility | ||
| 98 | * **Reviewable** by community members | ||
| 99 | * **Reversible** if evidence of error or harm | ||
| |
1.1 | 100 | |
| |
2.1 | 101 | ---- |
| |
1.1 | 102 | |
| |
2.1 | 103 | == Audit System Governance == |
| |
1.1 | 104 | |
| |
2.1 | 105 | === Audit Oversight Committee === |
| |
1.1 | 106 | |
| |
2.1 | 107 | **Composition**: Maintainers, Domain Experts, and Governing Team member(s) |
| |
1.1 | 108 | |
| |
2.1 | 109 | **Responsibilities**: |
| 110 | * Set quality standards for audit evaluation | ||
| 111 | * Review audit statistics and trends | ||
| 112 | * Adjust sampling rates based on performance | ||
| 113 | * Approve changes to audit algorithms | ||
| 114 | * Oversee auditor selection and rotation | ||
| 115 | * Publish transparency reports | ||
| |
1.1 | 116 | |
| |
2.1 | 117 | **Meeting Frequency**: Recommendation: Regular meetings as needed |
| |
1.1 | 118 | |
| |
2.1 | 119 | **Reporting**: Recommendation: Periodic transparency reports to community |
| |
1.1 | 120 | |
| |
2.1 | 121 | === Audit Performance Metrics === |
| |
1.1 | 122 | |
| |
2.1 | 123 | Tracked and published: |
| 124 | * Audit pass/fail rates by tier | ||
| 125 | * Common failure patterns | ||
| 126 | * System improvements implemented | ||
| 127 | * Time to resolution for audit failures | ||
| 128 | * Auditor performance (anonymized) | ||
| |
1.1 | 129 | |
| |
2.1 | 130 | === Feedback Loop Governance === |
| |
1.1 | 131 | |
| |
2.1 | 132 | **Process**: |
| 133 | 1. Audits identify patterns in AI errors | ||
| 134 | 2. Audit Committee reviews patterns | ||
| 135 | 3. Maintainers propose technical fixes | ||
| 136 | 4. Changes tested in sandbox | ||
| 137 | 5. Community informed of improvements | ||
| 138 | 6. Deployed with monitoring | ||
| |
1.1 | 139 | |
| |
2.1 | 140 | **Escalation**: |
| 141 | * Persistent high failure rates → Pause AI publication in affected tier/domain | ||
| 142 | * Critical errors → Immediate system review | ||
| 143 | * Pattern of harm → Policy revision | ||
| |
1.1 | 144 | |
| |
2.1 | 145 | ---- |
| |
1.1 | 146 | |
| |
2.1 | 147 | == Risk Tier Policy Governance == |
| |
1.1 | 148 | |
| |
2.1 | 149 | === Risk Tier Assignment Authority === |
| |
1.1 | 150 | |
| |
2.1 | 151 | * **AKEL**: Suggests initial tier based on domain, keywords, content analysis |
| 152 | * **Moderators**: Can override AKEL for individual content | ||
| 153 | * **Experts**: Set tier policy for their domains | ||
| 154 | * **Governing Team**: Approve tier policy changes, resolve tier disputes | ||
| |
1.1 | 155 | |
| |
2.1 | 156 | === Risk Tier Review Process === |
| |
1.1 | 157 | |
| |
2.1 | 158 | **Triggers for Review**: |
| 159 | * Significant audit failures in a tier | ||
| 160 | * New emerging topics or domains | ||
| 161 | * Community flags systematic misclassification | ||
| 162 | * Expert domain recommendations | ||
| 163 | * Periodic policy review | ||
| |
1.1 | 164 | |
| |
2.1 | 165 | **Process**: |
| 166 | 1. Expert domain review (identify if Tier A/B/C appropriate) | ||
| 167 | 2. Community input period (recommendation: sufficient time for feedback) | ||
| 168 | 3. Audit Committee assessment (error patterns in current tier) | ||
| 169 | 4. Governing Team decision | ||
| 170 | 5. Implementation with monitoring period | ||
| 171 | 6. Transparency report on rationale | ||
| |
1.1 | 172 | |
| |
2.1 | 173 | === Current Tier Assignments (Baseline) === |
| |
1.1 | 174 | |
| |
2.1 | 175 | **Tier A**: Medical, legal, elections, safety/security, major financial decisions |
| |
1.1 | 176 | |
| |
2.1 | 177 | **Tier B**: Complex science causality, contested policy, historical interpretation with political implications, significant economic impact |
| |
1.1 | 178 | |
| |
2.1 | 179 | **Tier C**: Established historical facts, simple definitions, well-documented scientific consensus, basic reference info |
| |
1.1 | 180 | |
| |
2.1 | 181 | **Note**: These are guidelines; edge cases require expert judgment |
| |
1.1 | 182 | |
| |
2.1 | 183 | ---- |
| |
1.1 | 184 | |
| |
2.1 | 185 | == Quality Gate Governance == |
| |
1.1 | 186 | |
| |
2.1 | 187 | === Quality Gate Modification Process === |
| |
1.1 | 188 | |
| |
2.1 | 189 | **Who Can Propose**: Maintainers, Experts, Audit Committee |
| |
1.1 | 190 | |
| |
2.1 | 191 | **Requirements**: |
| 192 | * Rationale based on audit failures or system improvements | ||
| 193 | * Testing in sandbox environment | ||
| 194 | * Impact assessment (false positive/negative rates) | ||
| 195 | * Community notification before deployment | ||
| |
1.1 | 196 | |
| |
2.1 | 197 | **Approval**: |
| 198 | * Technical changes: Maintainer consensus | ||
| 199 | * Policy changes (e.g., new gate criteria): Governing Team approval | ||
| |
1.1 | 200 | |
| |
2.1 | 201 | **Examples of Governed Changes**: |
| 202 | * Adjusting contradiction search scope | ||
| 203 | * Modifying source reliability thresholds | ||
| 204 | * Adding new bubble detection patterns | ||
| 205 | * Changing uncertainty quantification formulas | ||
| |
1.1 | 206 | |
| |
2.1 | 207 | ---- |
| |
1.1 | 208 | |
| |
2.1 | 209 | == Community Participation == |
| |
1.1 | 210 | |
| |
2.1 | 211 | === Open Discussion Forums === |
| |
1.1 | 212 | |
| |
2.1 | 213 | * Technical proposals (maintainer-led) |
| 214 | * Policy proposals (Governing Team-led) | ||
| 215 | * Domain-specific discussions (Expert-led) | ||
| 216 | * Audit findings and improvements (Audit Committee-led) | ||
| |
1.1 | 217 | |
| |
2.1 | 218 | === Proposal Mechanism === |
| |
1.1 | 219 | |
| |
2.1 | 220 | Anyone can propose: |
| 221 | 1. Submit proposal with rationale | ||
| 222 | 2. Community discussion (recommendation: minimum timeframe for feedback) | ||
| 223 | 3. Relevant authority reviews (Maintainers/Governing Team/Experts) | ||
| 224 | 4. Decision with documented reasoning | ||
| 225 | 5. Implementation (if approved) | ||
| |
1.1 | 226 | |
| |
2.1 | 227 | === Transparency === |
| |
1.1 | 228 | |
| |
2.1 | 229 | * All decisions documented in public wiki |
| 230 | * Audit statistics published periodically | ||
| 231 | * Governing Team meeting minutes published | ||
| 232 | * Expert recommendations documented | ||
| 233 | * Community feedback acknowledged | ||
| |
1.1 | 234 | |
| |
2.1 | 235 | ---- |
| |
1.1 | 236 | |
| |
2.1 | 237 | == Dispute Resolution == |
| |
1.1 | 238 | |
| |
2.1 | 239 | === Conflict Between Experts === |
| |
1.1 | 240 | |
| |
2.1 | 241 | 1. Experts attempt consensus |
| 242 | 2. If unresolved, escalate to Governing Team | ||
| 243 | 3. Governing Team appoints neutral expert panel | ||
| 244 | 4. Panel recommendation | ||
| 245 | 5. Governing Team decision (final) | ||
| |
1.1 | 246 | |
| |
2.1 | 247 | === Conflict Between Maintainers === |
| |
1.1 | 248 | |
| |
2.1 | 249 | 1. Discussion in maintainer forum |
| 250 | 2. Attempt consensus | ||
| 251 | 3. If unresolved, Lead makes decision | ||
| 252 | 4. Community informed of reasoning | ||
| |
1.1 | 253 | |
| |
2.1 | 254 | === User Appeals === |
| |
1.1 | 255 | |
| |
2.1 | 256 | Users can appeal: |
| 257 | * Content rejection decisions | ||
| 258 | * Risk tier assignments | ||
| 259 | * Audit outcomes | ||
| 260 | * Moderation actions | ||
| 261 | |||
| 262 | **Process**: | ||
| 263 | 1. Submit appeal with evidence | ||
| 264 | 2. Reviewed by independent moderator/expert | ||
| 265 | 3. Decision with reasoning | ||
| 266 | 4. Final appeal to Governing Team (if warranted) | ||
| 267 | |||
| 268 | ---- | ||
| 269 | |||
| 270 | == Related Pages == | ||
| 271 | |||
| 272 | * [[AKEL (AI Knowledge Extraction Layer)>>FactHarbor.Specification.AI Knowledge Extraction Layer (AKEL).WebHome]] | ||
| 273 | * [[Automation>>FactHarbor.Specification.Automation.WebHome]] | ||
| 274 | * [[Requirements (Roles)>>FactHarbor.Specification.Requirements.WebHome]] | ||
| 275 | * [[Organisational Model>>FactHarbor.Organisation.Organisational-Model]] | ||
| 276 |