Skip to Content

Changes for page Requirements

Last modified by Robert Schaub on 2025/12/24 20:34
From version 8.1
edited by Robert Schaub
on 2025/12/15 16:56
Change comment: Imported from XAR
To version 8.3
edited by Robert Schaub
on 2025/12/16 20:28
Change comment: Renamed back-links.

Summary

Details

Page properties
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,6 +151,7 @@
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
... ... @@ -160,6 +160,7 @@
160 160  == Content Publication States ==
161 161  
162 162  === Mode 1: Draft ===
181 +
163 163  * Not visible to public
164 164  * Visible to contributor and reviewers
165 165  * Can be edited by contributor or reviewers
... ... @@ -166,18 +166,20 @@
166 166  * Default state for failed quality gates
167 167  
168 168  === Mode 2: AI-Generated (Published) ===
188 +
169 169  * **Public** and visible to all users
170 170  * Clearly labeled as "AI-Generated, Awaiting Human Review"
171 171  * Passed all automated quality gates
172 172  * Risk tier displayed (A/B/C)
173 173  * Users can:
174 - ** Read and use content
175 - ** Request human review
176 - ** Flag for expert attention
194 +** Read and use content
195 +** Request human review
196 +** Flag for expert attention
177 177  * Subject to sampling audits
178 178  * Can be promoted to Mode 3 by reviewer/expert validation
179 179  
180 180  === Mode 3: Human-Reviewed (Published) ===
201 +
181 181  * **Public** and visible to all users
182 182  * Labeled as "Human-Reviewed" with reviewer/expert attribution
183 183  * Passed quality gates + human validation
... ... @@ -186,6 +186,7 @@
186 186  * For Tier B/C, Reviewer approval sufficient
187 187  
188 188  === Rejected ===
210 +
189 189  * Not visible to public
190 190  * Visible to contributor with rejection reason
191 191  * Can be resubmitted after addressing issues
... ... @@ -196,6 +196,7 @@
196 196  == Contribution Rules ==
197 197  
198 198  === All Contributors Must: ===
221 +
199 199  * Provide sources for claims
200 200  * Use clear, neutral language
201 201  * Avoid personal attacks or insults
... ... @@ -203,6 +203,7 @@
203 203  * Accept community feedback gracefully
204 204  
205 205  === AKEL (AI) Must: ===
229 +
206 206  * Mark all outputs with `AuthorType = AI`
207 207  * Pass quality gates before Mode 2 publication
208 208  * Perform mandatory contradiction search
... ... @@ -212,6 +212,7 @@
212 212  * Submit to audit sampling
213 213  
214 214  === Reviewers Must: ===
239 +
215 215  * Be impartial and evidence-based
216 216  * Document reasoning for decisions
217 217  * Escalate to experts when appropriate
... ... @@ -219,6 +219,7 @@
219 219  * Provide constructive feedback
220 220  
221 221  === Experts Must: ===
247 +
222 222  * Stay within domain expertise
223 223  * Disclose conflicts of interest
224 224  * Document specialized terminology
... ... @@ -230,6 +230,7 @@
230 230  == Quality Standards ==
231 231  
232 232  === Source Requirements ===
259 +
233 233  * Primary sources preferred over secondary
234 234  * Publication date and author must be identifiable
235 235  * Sources must be accessible (not paywalled when possible)
... ... @@ -237,6 +237,7 @@
237 237  * Echo chamber sources must be flagged
238 238  
239 239  === Claim Requirements ===
267 +
240 240  * Falsifiable or evaluable
241 241  * Clear definitions of key terms
242 242  * Boundaries and scope stated
... ... @@ -244,6 +244,7 @@
244 244  * Uncertainty acknowledged
245 245  
246 246  === Evidence Requirements ===
275 +
247 247  * Relevant to the claim and scenario
248 248  * Reliability assessment provided
249 249  * Methodology described (for studies)
... ... @@ -259,6 +259,7 @@
259 259  **Review**: Risk tiers periodically reviewed based on audit outcomes
260 260  
261 261  **Tier A Indicators**:
291 +
262 262  * Medical diagnosis or treatment advice
263 263  * Legal interpretation or advice
264 264  * Election or voting information
... ... @@ -267,6 +267,7 @@
267 267  * Potential for significant harm
268 268  
269 269  **Tier B Indicators**:
300 +
270 270  * Complex scientific causality
271 271  * Contested policy domains
272 272  * Historical interpretation with political implications
... ... @@ -273,6 +273,7 @@
273 273  * Significant economic impact claims
274 274  
275 275  **Tier C Indicators**:
307 +
276 276  * Established historical facts
277 277  * Simple definitions
278 278  * Well-documented scientific consensus
... ... @@ -305,15 +305,16 @@
305 305  
306 306  This diagram shows the two-track progression for human users:
307 307  
308 -{{include reference="Test.FactHarborV09.Specification.Diagrams.Human User Roles.WebHome"/}}
340 +{{include reference="FactHarbor.Archive.FactHarbor V0\.9\.23 Lost Data.Specification.Diagrams.Human User Roles.WebHome"/}}
309 309  
310 310  === Technical and System Users ===
311 311  
312 312  This diagram shows system processes and their management:
313 313  
314 -{{include reference="Test.FactHarborV09.Specification.Diagrams.Technical and System Users.WebHome"/}}
346 +{{include reference="FactHarbor.Archive.FactHarbor V0\.9\.23 Lost Data.Specification.Diagrams.Technical and System Users.WebHome"/}}
315 315  
316 316  **Key Design Principles**:
349 +
317 317  * **Two tracks from Contributor**: Content Track (Reviewer) and Technical Track (Maintainer)
318 318  * **Technical Users**: System processes (AKEL, bots) managed by Maintainers
319 319  * **Separation of concerns**: Editorial authority independent from technical authority
... ... @@ -332,7 +332,7 @@
332 332  
333 333  Requirements are structured as FR (Functional Requirement) items and organized by capability area.
334 334  
335 ----
368 +----
336 336  
337 337  == Claim Intake & Normalization ==
338 338  
... ... @@ -339,6 +339,7 @@
339 339  === FR1 – Claim Intake ===
340 340  
341 341  The system must support Claim creation from:
375 +
342 342  * Free-text input (from any Reader)
343 343  * URLs (web pages, articles, posts)
344 344  * Uploaded documents and transcripts
... ... @@ -366,7 +366,7 @@
366 366  * Allow manual correction of cluster membership
367 367  * Provide explanation why two claims are considered "same cluster"
368 368  
369 ----
403 +----
370 370  
371 371  == Scenario System ==
372 372  
... ... @@ -379,6 +379,7 @@
379 379  === FR6 – Required Scenario Fields ===
380 380  
381 381  Each scenario includes:
416 +
382 382  * Definitions (key terms)
383 383  * Assumptions (explicit, testable where possible)
384 384  * Boundaries (time, geography, population, conditions)
... ... @@ -396,7 +396,7 @@
396 396  * Users can compare scenarios side by side
397 397  * Show differences in assumptions, definitions, and evidence sets
398 398  
399 ----
434 +----
400 400  
401 401  == Evidence Management ==
402 402  
... ... @@ -409,6 +409,7 @@
409 409  === FR10 – Evidence Assessment ===
410 410  
411 411  For each piece of evidence:
447 +
412 412  * Assign reliability / quality ratings
413 413  * Capture who rated it and why
414 414  * Indicate known limitations, biases, or conflicts of interest
... ... @@ -420,7 +420,7 @@
420 420  * Make dependencies explicit (e.g., "Scenario A uses subset of evidence used in Scenario B")
421 421  * Use ScenarioEvidenceLink table with RelevanceScore
422 422  
423 ----
459 +----
424 424  
425 425  == Verdicts & Truth Landscape ==
426 426  
... ... @@ -427,6 +427,7 @@
427 427  === FR12 – Scenario Verdicts ===
428 428  
429 429  For each Scenario:
466 +
430 430  * Provide a **probability- or likelihood-based verdict**
431 431  * Capture uncertainty and reasoning
432 432  * Distinguish between AKEL draft and human-approved verdict
... ... @@ -444,7 +444,7 @@
444 444  * Allow users to see "as of date X, what did we know?"
445 445  * Maintain complete version history for auditing
446 446  
447 ----
484 +----
448 448  
449 449  == Workflow, Moderation & Audit ==
450 450  
... ... @@ -463,12 +463,12 @@
463 463  === FR17 – Audit Trail ===
464 464  
465 465  * Every significant action (create, edit, publish, delete/hide) is logged with:
466 - ** Who did it
467 - ** When (timestamp)
468 - ** What changed (diffs)
469 - ** Why (justification text)
503 +** Who did it
504 +** When (timestamp)
505 +** What changed (diffs)
506 +** Why (justification text)
470 470  
471 ----
508 +----
472 472  
473 473  == Quality Gates & AI Review ==
474 474  
... ... @@ -475,6 +475,7 @@
475 475  === FR18 – Quality Gate Validation ===
476 476  
477 477  Before AI-generated content (Mode 2) publication, enforce:
515 +
478 478  * Gate 1: Source Quality
479 479  * Gate 2: Contradiction Search (MANDATORY)
480 480  * Gate 3: Uncertainty Quantification
... ... @@ -492,7 +492,7 @@
492 492  * Moderators and Experts can override
493 493  * Risk tier affects publication workflow
494 494  
495 ----
533 +----
496 496  
497 497  == Federation Requirements ==
498 498  
... ... @@ -505,6 +505,7 @@
505 505  === FR22 – Data Sharing Modes ===
506 506  
507 507  Nodes must be able to:
546 +
508 508  * Share claims and summaries only
509 509  * Share selected claims, scenarios, and verdicts
510 510  * Share full underlying evidence metadata where allowed
... ... @@ -531,7 +531,7 @@
531 531  * NEVER share model weights
532 532  * NEVER override local governance
533 533  
534 ----
573 +----
535 535  
536 536  == Non-Functional Requirements ==
537 537  
... ... @@ -567,6 +567,7 @@
567 567  * Release 1.0: **2000+ concurrent users** on a reasonably provisioned node
568 568  
569 569  Technical targets for Release 1.0:
609 +
570 570  * Scalable monolith or early microservice architecture
571 571  * Sharded vector database (for semantic search)
572 572  * Optional IPFS or other decentralized storage for large artifacts
... ... @@ -597,7 +597,7 @@
597 597  * Support for saved views, filters, and user-level preferences
598 598  * Progressive disclosure: casual users see summaries, advanced users can dive deep
599 599  
600 ----
640 +----
601 601  
602 602  == Release Levels ==
603 603  
... ... @@ -628,7 +628,7 @@
628 628  * Multi-node federation with full sync protocol
629 629  * Mature audit system
630 630  
631 ----
671 +----
632 632  
633 633  
634 634  
... ... @@ -640,4 +640,3 @@
640 640  * [[Automation>>FactHarbor.Specification.Automation.WebHome]]
641 641  * [[Workflows>>FactHarbor.Specification.Workflows.WebHome]]
642 642  * [[Governance>>FactHarbor.Organisation.Governance]]
643 -