Wiki source code of Requirements
Version 7.1 by Robert Schaub on 2025/12/14 22:27
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | = Requirements = |
| 2 | |||
| |
6.1 | 3 | This page defines **Roles**, **Responsibilities**, and **Rules** for contributors and users of FactHarbor. |
| |
1.1 | 4 | |
| |
6.1 | 5 | == Roles == |
| |
1.1 | 6 | |
| |
7.1 | 7 | === Reader === |
| 8 | |||
| 9 | **Who**: Anyone (no login required). | ||
| 10 | |||
| 11 | **Can**: | ||
| 12 | * Browse and search claims | ||
| 13 | * View scenarios, evidence, verdicts, and timelines | ||
| 14 | * Compare scenarios and explore assumptions | ||
| 15 | * Flag issues, errors, contradictions, or suspicious patterns | ||
| 16 | * Use filters, search, and visualization tools | ||
| 17 | * Create personal views (saved searches, bookmarks - local browser storage) | ||
| 18 | * **Submit claims automatically** by providing text to analyze - new claims are added automatically unless equal claims already exist in the system | ||
| 19 | |||
| 20 | **Cannot**: | ||
| 21 | * Modify existing content | ||
| 22 | * Access draft content | ||
| 23 | * Participate in governance decisions | ||
| 24 | |||
| 25 | **Note**: Readers can request human review of AI-generated content by flagging it. | ||
| 26 | |||
| |
6.1 | 27 | === Contributor === |
| |
1.1 | 28 | |
| |
7.1 | 29 | **Who**: Registered and logged-in users (extends Reader capabilities). |
| |
1.1 | 30 | |
| |
6.1 | 31 | **Can**: |
| |
7.1 | 32 | * Everything a Reader can do |
| |
6.1 | 33 | * Submit claims |
| 34 | * Submit evidence | ||
| 35 | * Provide feedback | ||
| 36 | * Suggest scenarios | ||
| 37 | * Flag content for review | ||
| 38 | * Request human review of AI-generated content | ||
| |
1.1 | 39 | |
| |
6.1 | 40 | **Cannot**: |
| 41 | * Publish or mark content as "reviewed" or "approved" | ||
| 42 | * Override expert or maintainer decisions | ||
| 43 | * Directly modify AKEL or quality gate configurations | ||
| |
1.1 | 44 | |
| |
6.1 | 45 | === Reviewer === |
| |
1.1 | 46 | |
| |
6.1 | 47 | **Who**: Trusted community members, appointed by maintainers. |
| |
1.1 | 48 | |
| |
6.1 | 49 | **Can**: |
| 50 | * Review contributions from Contributors and AKEL drafts | ||
| 51 | * Validate AI-generated content (Mode 2 → Mode 3 transition) | ||
| 52 | * Edit claims, scenarios, and evidence | ||
| 53 | * Add clarifications or warnings | ||
| 54 | * Change content status: `draft` → `in review` → `published` / `rejected` | ||
| 55 | * Approve or reject **Tier B and C** content for "Human-Reviewed" status | ||
| 56 | * Flag content for expert review | ||
| 57 | * Participate in audit sampling | ||
| |
1.1 | 58 | |
| |
6.1 | 59 | **Cannot**: |
| 60 | * Approve Tier A content for "Human-Reviewed" status (requires Expert) | ||
| 61 | * Change governance rules | ||
| 62 | * Unilaterally change expert conclusions without process | ||
| 63 | * Bypass quality gates | ||
| |
1.1 | 64 | |
| |
6.1 | 65 | **Note on AI-Drafted Content**: |
| 66 | * Reviewers can validate AI-generated content (Mode 2) to promote it to "Human-Reviewed" (Mode 3) | ||
| 67 | * For Tier B and C, Reviewers have approval authority | ||
| 68 | * For Tier A, only Experts can grant "Human-Reviewed" status | ||
| |
1.1 | 69 | |
| |
6.1 | 70 | === Expert (Domain-Specific) === |
| |
1.1 | 71 | |
| |
6.1 | 72 | **Who**: Subject-matter specialists in specific domains (medicine, law, science, etc.). |
| |
1.1 | 73 | |
| |
6.1 | 74 | **Can**: |
| 75 | * Everything a Reviewer can do | ||
| 76 | * **Final authority** on Tier A content "Human-Reviewed" status | ||
| 77 | * Validate complex or controversial claims in their domain | ||
| 78 | * Define domain-specific quality standards | ||
| 79 | * Set reliability thresholds for domain sources | ||
| 80 | * Participate in risk tier assignment review | ||
| 81 | * Override AKEL suggestions in their domain (with documentation) | ||
| |
1.1 | 82 | |
| |
6.1 | 83 | **Cannot**: |
| 84 | * Change platform governance policies | ||
| 85 | * Approve content outside their expertise domain | ||
| 86 | * Bypass technical quality gates (but can flag for adjustment) | ||
| |
1.1 | 87 | |
| |
6.1 | 88 | **Specialization**: |
| 89 | * Experts are domain-specific (e.g., "Medical Expert", "Legal Expert", "Climate Science Expert") | ||
| 90 | * Cross-domain claims may require multiple expert reviews | ||
| |
1.1 | 91 | |
| |
6.1 | 92 | === Auditor === |
| |
1.1 | 93 | |
| |
6.1 | 94 | **Who**: Reviewers or Experts assigned to sampling audit duties. |
| |
1.1 | 95 | |
| |
6.1 | 96 | **Can**: |
| 97 | * Review sampled AI-generated content against quality standards | ||
| 98 | * Validate quality gate enforcement | ||
| 99 | * Identify patterns in AI errors or hallucinations | ||
| 100 | * Provide feedback for system improvement | ||
| 101 | * Flag content for immediate review if errors found | ||
| 102 | * Contribute to audit statistics and transparency reports | ||
| |
1.1 | 103 | |
| |
6.1 | 104 | **Cannot**: |
| 105 | * Change audit sampling algorithms (maintainer responsibility) | ||
| 106 | * Bypass normal review workflows | ||
| 107 | * Audit content they personally created | ||
| |
1.1 | 108 | |
| |
6.1 | 109 | **Selection**: |
| 110 | * Auditors selected based on domain expertise and review quality | ||
| 111 | * Rotation to prevent audit fatigue | ||
| 112 | * Stratified assignment (Tier A auditors need higher expertise) | ||
| |
1.1 | 113 | |
| |
6.1 | 114 | **Audit Focus**: |
| 115 | * Tier A: Recommendation 30-50% sampling rate, expert auditors | ||
| 116 | * Tier B: Recommendation 10-20% sampling rate, reviewer/expert auditors | ||
| 117 | * Tier C: Recommendation 5-10% sampling rate, reviewer auditors | ||
| |
5.1 | 118 | |
| |
6.1 | 119 | === Moderator === |
| |
5.1 | 120 | |
| |
6.1 | 121 | **Who**: Maintainers or trusted long-term contributors. |
| |
5.1 | 122 | |
| |
6.1 | 123 | **Can**: |
| 124 | * All Reviewer and Expert capabilities (cross-domain) | ||
| 125 | * Manage user accounts and permissions | ||
| 126 | * Handle disputes and conflicts | ||
| 127 | * Enforce community guidelines | ||
| 128 | * Suspend or ban abusive users | ||
| 129 | * Finalize publication status for sensitive content | ||
| 130 | * Review and adjust risk tier assignments | ||
| 131 | * Oversee audit system performance | ||
| |
5.1 | 132 | |
| |
6.1 | 133 | **Cannot**: |
| 134 | * Change core data model or architecture | ||
| 135 | * Override technical system constraints | ||
| 136 | * Make unilateral governance decisions without consensus | ||
| |
5.1 | 137 | |
| |
6.1 | 138 | === Maintainer === |
| |
5.1 | 139 | |
| |
6.1 | 140 | **Who**: Core team members responsible for the platform. |
| |
5.1 | 141 | |
| |
6.1 | 142 | **Can**: |
| 143 | * All Moderator capabilities | ||
| 144 | * Change data model, architecture, and technical systems | ||
| 145 | * Configure quality gates and AKEL parameters | ||
| 146 | * Adjust audit sampling algorithms | ||
| 147 | * Set and modify risk tier policies | ||
| 148 | * Make platform-wide governance decisions | ||
| 149 | * Access and modify backend systems | ||
| 150 | * Deploy updates and fixes | ||
| 151 | * Grant and revoke roles | ||
| |
5.1 | 152 | |
| |
6.1 | 153 | **Governance**: |
| 154 | * Maintainers operate under organizational governance rules | ||
| 155 | * Major policy changes require Governing Team approval | ||
| 156 | * Technical decisions made collaboratively | ||
| |
5.1 | 157 | |
| 158 | ---- | ||
| 159 | |||
| |
6.1 | 160 | == Content Publication States == |
| |
5.1 | 161 | |
| |
6.1 | 162 | === Mode 1: Draft === |
| 163 | * Not visible to public | ||
| 164 | * Visible to contributor and reviewers | ||
| 165 | * Can be edited by contributor or reviewers | ||
| 166 | * Default state for failed quality gates | ||
| |
5.1 | 167 | |
| |
6.1 | 168 | === Mode 2: AI-Generated (Published) === |
| 169 | * **Public** and visible to all users | ||
| 170 | * Clearly labeled as "AI-Generated, Awaiting Human Review" | ||
| 171 | * Passed all automated quality gates | ||
| 172 | * Risk tier displayed (A/B/C) | ||
| 173 | * Users can: | ||
| 174 | ** Read and use content | ||
| 175 | ** Request human review | ||
| 176 | ** Flag for expert attention | ||
| 177 | * Subject to sampling audits | ||
| 178 | * Can be promoted to Mode 3 by reviewer/expert validation | ||
| |
5.1 | 179 | |
| |
6.1 | 180 | === Mode 3: Human-Reviewed (Published) === |
| 181 | * **Public** and visible to all users | ||
| 182 | * Labeled as "Human-Reviewed" with reviewer/expert attribution | ||
| 183 | * Passed quality gates + human validation | ||
| 184 | * Highest trust level | ||
| 185 | * For Tier A, requires Expert approval | ||
| 186 | * For Tier B/C, Reviewer approval sufficient | ||
| |
5.1 | 187 | |
| |
6.1 | 188 | === Rejected === |
| 189 | * Not visible to public | ||
| 190 | * Visible to contributor with rejection reason | ||
| 191 | * Can be resubmitted after addressing issues | ||
| 192 | * Rejection logged for transparency | ||
| |
5.1 | 193 | |
| 194 | ---- | ||
| 195 | |||
| |
6.1 | 196 | == Contribution Rules == |
| |
5.1 | 197 | |
| |
6.1 | 198 | === All Contributors Must: === |
| 199 | * Provide sources for claims | ||
| 200 | * Use clear, neutral language | ||
| 201 | * Avoid personal attacks or insults | ||
| 202 | * Respect intellectual property (cite sources) | ||
| 203 | * Accept community feedback gracefully | ||
| |
5.1 | 204 | |
| |
6.1 | 205 | === AKEL (AI) Must: === |
| 206 | * Mark all outputs with `AuthorType = AI` | ||
| 207 | * Pass quality gates before Mode 2 publication | ||
| 208 | * Perform mandatory contradiction search | ||
| 209 | * Disclose confidence levels and uncertainty | ||
| 210 | * Provide traceable reasoning chains | ||
| 211 | * Flag potential bubbles or echo chambers | ||
| 212 | * Submit to audit sampling | ||
| |
5.1 | 213 | |
| |
6.1 | 214 | === Reviewers Must: === |
| 215 | * Be impartial and evidence-based | ||
| 216 | * Document reasoning for decisions | ||
| 217 | * Escalate to experts when appropriate | ||
| 218 | * Participate in audits when assigned | ||
| 219 | * Provide constructive feedback | ||
| |
5.1 | 220 | |
| |
6.1 | 221 | === Experts Must: === |
| 222 | * Stay within domain expertise | ||
| 223 | * Disclose conflicts of interest | ||
| 224 | * Document specialized terminology | ||
| 225 | * Provide reasoning for domain-specific decisions | ||
| 226 | * Participate in Tier A audits | ||
| |
5.1 | 227 | |
| 228 | ---- | ||
| 229 | |||
| |
6.1 | 230 | == Quality Standards == |
| |
5.1 | 231 | |
| |
6.1 | 232 | === Source Requirements === |
| 233 | * Primary sources preferred over secondary | ||
| 234 | * Publication date and author must be identifiable | ||
| 235 | * Sources must be accessible (not paywalled when possible) | ||
| 236 | * Contradictory sources must be acknowledged | ||
| 237 | * Echo chamber sources must be flagged | ||
| |
5.1 | 238 | |
| |
6.1 | 239 | === Claim Requirements === |
| 240 | * Falsifiable or evaluable | ||
| 241 | * Clear definitions of key terms | ||
| 242 | * Boundaries and scope stated | ||
| 243 | * Assumptions made explicit | ||
| 244 | * Uncertainty acknowledged | ||
| |
5.1 | 245 | |
| |
6.1 | 246 | === Evidence Requirements === |
| 247 | * Relevant to the claim and scenario | ||
| 248 | * Reliability assessment provided | ||
| 249 | * Methodology described (for studies) | ||
| 250 | * Limitations noted | ||
| 251 | * Conflicting evidence acknowledged | ||
| |
5.1 | 252 | |
| 253 | ---- | ||
| 254 | |||
| |
6.1 | 255 | == Risk Tier Assignment == |
| |
5.1 | 256 | |
| |
6.1 | 257 | **Automated (AKEL)**: Initial tier suggested based on domain, keywords, impact |
| 258 | **Human Validation**: Moderators or Experts can override AKEL suggestions | ||
| 259 | **Review**: Risk tiers periodically reviewed based on audit outcomes | ||
| |
5.1 | 260 | |
| |
6.1 | 261 | **Tier A Indicators**: |
| 262 | * Medical diagnosis or treatment advice | ||
| 263 | * Legal interpretation or advice | ||
| 264 | * Election or voting information | ||
| 265 | * Safety or security sensitive | ||
| 266 | * Major financial decisions | ||
| 267 | * Potential for significant harm | ||
| |
5.1 | 268 | |
| |
6.1 | 269 | **Tier B Indicators**: |
| 270 | * Complex scientific causality | ||
| 271 | * Contested policy domains | ||
| 272 | * Historical interpretation with political implications | ||
| 273 | * Significant economic impact claims | ||
| |
5.1 | 274 | |
| |
6.1 | 275 | **Tier C Indicators**: |
| 276 | * Established historical facts | ||
| 277 | * Simple definitions | ||
| 278 | * Well-documented scientific consensus | ||
| 279 | * Basic reference information | ||
| |
5.1 | 280 | |
| 281 | ---- | ||
| 282 | |||
| |
6.1 | 283 | == Related Pages == |
| |
5.1 | 284 | |
| |
6.1 | 285 | * [[AKEL (AI Knowledge Extraction Layer)>>FactHarbor.Specification.AI Knowledge Extraction Layer (AKEL).WebHome]] |
| 286 | * [[Automation>>FactHarbor.Specification.Automation.WebHome]] | ||
| 287 | * [[Workflows>>FactHarbor.Specification.Workflows.WebHome]] | ||
| 288 | * [[Governance>>FactHarbor.Organisation.Governance]] | ||
| |
5.1 | 289 |