Skip to Content

Changes for page Requirements

Last modified by Robert Schaub on 2026/02/08 21:23
From version 1.1
edited by Robert Schaub
on 2025/12/16 21:42
Change comment: Imported from XAR
To version 2.9
edited by Robert Schaub
on 2026/01/20 20:28
Change comment: Renamed back-links.

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,1 @@
1 -FactHarbor.Specification.WebHome
1 +Archive.FactHarbor 0\.9\.40.Specification.WebHome
Content
... ... @@ -9,6 +9,7 @@
9 9  **Who**: Anyone (no login required).
10 10  
11 11  **Can**:
12 +
12 12  * Browse and search claims
13 13  * View scenarios, evidence, verdicts, and timelines
14 14  * Compare scenarios and explore assumptions
... ... @@ -18,6 +18,7 @@
18 18  * **Submit claims automatically** by providing text to analyze - new claims are added automatically unless equal claims already exist in the system
19 19  
20 20  **Cannot**:
22 +
21 21  * Modify existing content
22 22  * Access draft content
23 23  * Participate in governance decisions
... ... @@ -29,6 +29,7 @@
29 29  **Who**: Registered and logged-in users (extends Reader capabilities).
30 30  
31 31  **Can**:
34 +
32 32  * Everything a Reader can do
33 33  * Submit claims
34 34  * Submit evidence
... ... @@ -38,6 +38,7 @@
38 38  * Request human review of AI-generated content
39 39  
40 40  **Cannot**:
44 +
41 41  * Publish or mark content as "reviewed" or "approved"
42 42  * Override expert or maintainer decisions
43 43  * Directly modify AKEL or quality gate configurations
... ... @@ -47,6 +47,7 @@
47 47  **Who**: Trusted community members, appointed by maintainers.
48 48  
49 49  **Can**:
54 +
50 50  * Review contributions from Contributors and AKEL drafts
51 51  * Validate AI-generated content (Mode 2 → Mode 3 transition)
52 52  * Edit claims, scenarios, and evidence
... ... @@ -57,6 +57,7 @@
57 57  * Participate in audit sampling
58 58  
59 59  **Cannot**:
65 +
60 60  * Approve Tier A content for "Human-Reviewed" status (requires Expert)
61 61  * Change governance rules
62 62  * Unilaterally change expert conclusions without process
... ... @@ -63,6 +63,7 @@
63 63  * Bypass quality gates
64 64  
65 65  **Note on AI-Drafted Content**:
72 +
66 66  * Reviewers can validate AI-generated content (Mode 2) to promote it to "Human-Reviewed" (Mode 3)
67 67  * For Tier B and C, Reviewers have approval authority
68 68  * For Tier A, only Experts can grant "Human-Reviewed" status
... ... @@ -72,6 +72,7 @@
72 72  **Who**: Subject-matter specialists in specific domains (medicine, law, science, etc.).
73 73  
74 74  **Can**:
82 +
75 75  * Everything a Reviewer can do
76 76  * **Final authority** on Tier A content "Human-Reviewed" status
77 77  * Validate complex or controversial claims in their domain
... ... @@ -81,11 +81,13 @@
81 81  * Override AKEL suggestions in their domain (with documentation)
82 82  
83 83  **Cannot**:
92 +
84 84  * Change platform governance policies
85 85  * Approve content outside their expertise domain
86 86  * Bypass technical quality gates (but can flag for adjustment)
87 87  
88 88  **Specialization**:
98 +
89 89  * Experts are domain-specific (e.g., "Medical Expert", "Legal Expert", "Climate Science Expert")
90 90  * Cross-domain claims may require multiple expert reviews
91 91  
... ... @@ -94,6 +94,7 @@
94 94  **Who**: Reviewers or Experts assigned to sampling audit duties.
95 95  
96 96  **Can**:
107 +
97 97  * Review sampled AI-generated content against quality standards
98 98  * Validate quality gate enforcement
99 99  * Identify patterns in AI errors or hallucinations
... ... @@ -102,16 +102,19 @@
102 102  * Contribute to audit statistics and transparency reports
103 103  
104 104  **Cannot**:
116 +
105 105  * Change audit sampling algorithms (maintainer responsibility)
106 106  * Bypass normal review workflows
107 107  * Audit content they personally created
108 108  
109 109  **Selection**:
122 +
110 110  * Auditors selected based on domain expertise and review quality
111 111  * Rotation to prevent audit fatigue
112 112  * Stratified assignment (Tier A auditors need higher expertise)
113 113  
114 114  **Audit Focus**:
128 +
115 115  * Tier A: Recommendation 30-50% sampling rate, expert auditors
116 116  * Tier B: Recommendation 10-20% sampling rate, reviewer/expert auditors
117 117  * Tier C: Recommendation 5-10% sampling rate, reviewer auditors
... ... @@ -121,6 +121,7 @@
121 121  **Who**: Maintainers or trusted long-term contributors.
122 122  
123 123  **Can**:
138 +
124 124  * All Reviewer and Expert capabilities (cross-domain)
125 125  * Manage user accounts and permissions
126 126  * Handle disputes and conflicts
... ... @@ -131,6 +131,7 @@
131 131  * Oversee audit system performance
132 132  
133 133  **Cannot**:
149 +
134 134  * Change core data model or architecture
135 135  * Override technical system constraints
136 136  * Make unilateral governance decisions without consensus
... ... @@ -140,6 +140,7 @@
140 140  **Who**: Core team members responsible for the platform.
141 141  
142 142  **Can**:
159 +
143 143  * All Moderator capabilities
144 144  * Change data model, architecture, and technical systems
145 145  * Configure quality gates and AKEL parameters
... ... @@ -151,14 +151,15 @@
151 151  * Grant and revoke roles
152 152  
153 153  **Governance**:
171 +
154 154  * Maintainers operate under organizational governance rules
155 155  * Major policy changes require Governing Team approval
156 156  * Technical decisions made collaboratively
157 157  
158 -
159 159  == 2. Content Publication States ==
160 160  
161 161  === 2.1 Mode 1: Draft ===
179 +
162 162  * Not visible to public
163 163  * Visible to contributor and reviewers
164 164  * Can be edited by contributor or reviewers
... ... @@ -165,18 +165,20 @@
165 165  * Default state for failed quality gates
166 166  
167 167  === 2.2 Mode 2: AI-Generated (Published) ===
186 +
168 168  * **Public** and visible to all users
169 169  * Clearly labeled as "AI-Generated, Awaiting Human Review"
170 170  * Passed all automated quality gates
171 171  * Risk tier displayed (A/B/C)
172 172  * Users can:
173 - ** Read and use content
174 - ** Request human review
175 - ** Flag for expert attention
192 +** Read and use content
193 +** Request human review
194 +** Flag for expert attention
176 176  * Subject to sampling audits
177 177  * Can be promoted to Mode 3 by reviewer/expert validation
178 178  
179 179  === 2.3 Mode 3: Human-Reviewed (Published) ===
199 +
180 180  * **Public** and visible to all users
181 181  * Labeled as "Human-Reviewed" with reviewer/expert attribution
182 182  * Passed quality gates + human validation
... ... @@ -185,15 +185,16 @@
185 185  * For Tier B/C, Reviewer approval sufficient
186 186  
187 187  === 2.4 Rejected ===
208 +
188 188  * Not visible to public
189 189  * Visible to contributor with rejection reason
190 190  * Can be resubmitted after addressing issues
191 191  * Rejection logged for transparency
192 192  
193 -
194 194  == 3. Contribution Rules ==
195 195  
196 196  === 3.1 All Contributors Must: ===
217 +
197 197  * Provide sources for claims
198 198  * Use clear, neutral language
199 199  * Avoid personal attacks or insults
... ... @@ -201,6 +201,7 @@
201 201  * Accept community feedback gracefully
202 202  
203 203  === 3.2 AKEL (AI) Must: ===
225 +
204 204  * Mark all outputs with `AuthorType = AI`
205 205  * Pass quality gates before Mode 2 publication
206 206  * Perform mandatory contradiction search
... ... @@ -210,6 +210,7 @@
210 210  * Submit to audit sampling
211 211  
212 212  === 3.3 Reviewers Must: ===
235 +
213 213  * Be impartial and evidence-based
214 214  * Document reasoning for decisions
215 215  * Escalate to experts when appropriate
... ... @@ -217,6 +217,7 @@
217 217  * Provide constructive feedback
218 218  
219 219  === 3.4 Experts Must: ===
243 +
220 220  * Stay within domain expertise
221 221  * Disclose conflicts of interest
222 222  * Document specialized terminology
... ... @@ -223,10 +223,10 @@
223 223  * Provide reasoning for domain-specific decisions
224 224  * Participate in Tier A audits
225 225  
226 -
227 227  == 4. Quality Standards ==
228 228  
229 229  === 4.1 Source Requirements ===
253 +
230 230  * Primary sources preferred over secondary
231 231  * Publication date and author must be identifiable
232 232  * Sources must be accessible (not paywalled when possible)
... ... @@ -234,6 +234,7 @@
234 234  * Echo chamber sources must be flagged
235 235  
236 236  === 4.2 Claim Requirements ===
261 +
237 237  * Falsifiable or evaluable
238 238  * Clear definitions of key terms
239 239  * Boundaries and scope stated
... ... @@ -241,6 +241,7 @@
241 241  * Uncertainty acknowledged
242 242  
243 243  === 4.3 Evidence Requirements ===
269 +
244 244  * Relevant to the claim and scenario
245 245  * Reliability assessment provided
246 246  * Methodology described (for studies)
... ... @@ -247,14 +247,14 @@
247 247  * Limitations noted
248 248  * Conflicting evidence acknowledged
249 249  
276 +== 5. Risk tier Assignment ==
250 250  
251 -== 5. Risk Tier Assignment ==
252 -
253 253  **Automated (AKEL)**: Initial tier suggested based on domain, keywords, impact
254 254  **Human Validation**: Moderators or Experts can override AKEL suggestions
255 255  **Review**: Risk tiers periodically reviewed based on audit outcomes
256 256  
257 257  **Tier A Indicators**:
283 +
258 258  * Medical diagnosis or treatment advice
259 259  * Legal interpretation or advice
260 260  * Election or voting information
... ... @@ -263,6 +263,7 @@
263 263  * Potential for significant harm
264 264  
265 265  **Tier B Indicators**:
292 +
266 266  * Complex scientific causality
267 267  * Contested policy domains
268 268  * Historical interpretation with political implications
... ... @@ -269,21 +269,17 @@
269 269  * Significant economic impact claims
270 270  
271 271  **Tier C Indicators**:
299 +
272 272  * Established historical facts
273 273  * Simple definitions
274 274  * Well-documented scientific consensus
275 275  * Basic reference information
276 276  
277 -
278 -
279 -
280 280  == 6. User Role Hierarchy Diagram ==
281 281  
282 282  The following diagram visualizes the complete role hierarchy:
283 283  
284 284  
285 -
286 -
287 287  == 7. Role Hierarchy Diagrams ==
288 288  
289 289  === 7.1 User Class Diagram ===
... ... @@ -290,33 +290,29 @@
290 290  
291 291  The following class diagram visualizes the complete user role hierarchy:
292 292  
293 -{{include reference="FactHarbor.Specification.Diagrams.User Class Diagram.WebHome"/}}
316 +{{include reference="Archive.FactHarbor.Specification.Diagrams.User Class Diagram.WebHome"/}}
294 294  
295 295  === 7.2 Human User Roles ===
296 296  
297 297  This diagram shows the two-track progression for human users:
298 298  
299 -{{include reference="FactHarbor.Specification.Diagrams.Human User Roles.WebHome"/}}
322 +{{include reference="Archive.FactHarbor.Specification.Diagrams.Human User Roles.WebHome"/}}
300 300  
301 301  === 7.3 Technical and System Users ===
302 302  
303 303  This diagram shows system processes and their management:
304 304  
305 -{{include reference="FactHarbor.Specification.Diagrams.Technical and System Users.WebHome"/}}
328 +{{include reference="Archive.FactHarbor.Specification.Diagrams.Technical and System Users.WebHome"/}}
306 306  
307 307  **Key Design Principles**:
331 +
308 308  * **Two tracks from Contributor**: Content Track (Reviewer) and Technical Track (Maintainer)
309 309  * **Technical Users**: System processes (AKEL, bots) managed by Maintainers
310 310  * **Separation of concerns**: Editorial authority independent from technical authority
311 311  
312 -
313 -
314 -
315 -
316 316  = Functional Requirements =
317 317  
318 318  
319 -
320 320  This page defines what the FactHarbor system must **do** to fulfill its mission.
321 321  
322 322  Requirements are structured as FR (Functional Requirement) items and organized by capability area.
... ... @@ -327,6 +327,7 @@
327 327  === 8.1 FR1 – Claim Intake ===
328 328  
329 329  The system must support Claim creation from:
349 +
330 330  * Free-text input (from any Reader)
331 331  * URLs (web pages, articles, posts)
332 332  * Uploaded documents and transcripts
... ... @@ -354,7 +354,6 @@
354 354  * Allow manual correction of cluster membership
355 355  * Provide explanation why two claims are considered "same cluster"
356 356  
357 -
358 358  == 9. Scenario System ==
359 359  
360 360  === 9.1 FR5 – Scenario Creation ===
... ... @@ -366,6 +366,7 @@
366 366  === 9.2 FR6 – Required Scenario Fields ===
367 367  
368 368  Each scenario includes:
388 +
369 369  * Definitions (key terms)
370 370  * Assumptions (explicit, testable where possible)
371 371  * Boundaries (time, geography, population, conditions)
... ... @@ -383,7 +383,6 @@
383 383  * Users can compare scenarios side by side
384 384  * Show differences in assumptions, definitions, and evidence sets
385 385  
386 -
387 387  == 10. Evidence Management ==
388 388  
389 389  === 10.1 FR9 – Evidence Ingestion ===
... ... @@ -395,6 +395,7 @@
395 395  === 10.2 FR10 – Evidence Assessment ===
396 396  
397 397  For each piece of evidence:
417 +
398 398  * Assign reliability / quality ratings
399 399  * Capture who rated it and why
400 400  * Indicate known limitations, biases, or conflicts of interest
... ... @@ -406,12 +406,12 @@
406 406  * Make dependencies explicit (e.g., "Scenario A uses subset of evidence used in Scenario B")
407 407  * Use ScenarioEvidenceLink table with RelevanceScore
408 408  
409 -
410 410  == 11. Verdicts & Truth Landscape ==
411 411  
412 412  === 11.1 FR12 – Scenario Verdicts ===
413 413  
414 414  For each Scenario:
434 +
415 415  * Provide a **probability- or likelihood-based verdict**
416 416  * Capture uncertainty and reasoning
417 417  * Distinguish between AKEL draft and human-approved verdict
... ... @@ -429,7 +429,6 @@
429 429  * Allow users to see "as of date X, what did we know?"
430 430  * Maintain complete version history for auditing
431 431  
432 -
433 433  == 12. Workflow, Moderation & Audit ==
434 434  
435 435  === 12.1 FR15 – Workflow States ===
... ... @@ -447,17 +447,17 @@
447 447  === 12.3 FR17 – Audit Trail ===
448 448  
449 449  * Every significant action (create, edit, publish, delete/hide) is logged with:
450 - ** Who did it
451 - ** When (timestamp)
452 - ** What changed (diffs)
453 - ** Why (justification text)
469 +** Who did it
470 +** When (timestamp)
471 +** What changed (diffs)
472 +** Why (justification text)
454 454  
455 -
456 456  == 13. Quality Gates & AI Review ==
457 457  
458 458  === 13.1 FR18 – Quality Gate Validation ===
459 459  
460 460  Before AI-generated content (Mode 2) publication, enforce:
479 +
461 461  * Gate 1: Source Quality
462 462  * Gate 2: Contradiction Search (MANDATORY)
463 463  * Gate 3: Uncertainty Quantification
... ... @@ -475,7 +475,6 @@
475 475  * Moderators and Experts can override
476 476  * Risk tier affects publication workflow
477 477  
478 -
479 479  == 14. Federation Requirements ==
480 480  
481 481  === 14.1 FR21 – Node Autonomy ===
... ... @@ -487,6 +487,7 @@
487 487  === 14.2 FR22 – Data Sharing Modes ===
488 488  
489 489  Nodes must be able to:
508 +
490 490  * Share claims and summaries only
491 491  * Share selected claims, scenarios, and verdicts
492 492  * Share full underlying evidence metadata where allowed
... ... @@ -513,7 +513,6 @@
513 513  * NEVER share model weights
514 514  * NEVER override local governance
515 515  
516 -
517 517  == 15. Non-Functional Requirements ==
518 518  
519 519  === 15.1 NFR1 – Transparency ===
... ... @@ -548,6 +548,7 @@
548 548  * Release 1.0: **2000+ concurrent users** on a reasonably provisioned node
549 549  
550 550  Technical targets for Release 1.0:
569 +
551 551  * Scalable monolith or early microservice architecture
552 552  * Sharded vector database (for semantic search)
553 553  * Optional IPFS or other decentralized storage for large artifacts
... ... @@ -578,7 +578,6 @@
578 578  * Support for saved views, filters, and user-level preferences
579 579  * Progressive disclosure: casual users see summaries, advanced users can dive deep
580 580  
581 -
582 582  == 16. Release Levels ==
583 583  
584 584  === 16.1 Proof of Concept (POC) ===
... ... @@ -608,15 +608,10 @@
608 608  * Multi-node federation with full sync protocol
609 609  * Mature audit system
610 610  
611 -
612 -
613 -
614 614  == 17. Related Pages ==
615 615  
616 616  
617 -
618 -* [[AKEL (AI Knowledge Extraction Layer)>>FactHarbor.Specification.AI Knowledge Extraction Layer (AKEL).WebHome]]
619 -* [[Automation>>FactHarbor.Specification.Automation.WebHome]]
632 +* [[AKEL (AI Knowledge Extraction Layer)>>Archive.FactHarbor.Specification.AI Knowledge Extraction Layer (AKEL).WebHome]]
633 +* [[Automation>>Archive.FactHarbor.Specification.Automation.WebHome]]
620 620  * [[Workflows>>FactHarbor.Specification.Workflows.WebHome]]
621 -* [[Governance>>FactHarbor.Organisation.Governance]]
622 -
635 +* [[Governance>>Archive.FactHarbor.Organisation.Governance.WebHome]]