Changes for page Requirements

Last modified by Robert Schaub on 2025/12/24 20:34

From version 7.1
edited by Robert Schaub
on 2025/12/14 22:27
Change comment: Imported from XAR
To version 2.1
edited by Robert Schaub
on 2025/12/12 09:32
Change comment: Imported from XAR

Summary

Details

Page properties
Content
... ... @@ -1,289 +1,91 @@
1 1  = Requirements =
2 2  
3 -This page defines **Roles**, **Responsibilities**, and **Rules** for contributors and users of FactHarbor.
3 +This chapter defines the requirements for FactHarbor.
4 4  
5 -== Roles ==
5 +== User Roles ==
6 6  
7 7  === Reader ===
8 +* **Responsibilities**: Browse, search, view scenarios/verdicts, flag issues.
9 +* **Permissions**: Read-only access.
10 +* **Limitations**: Cannot change content.
8 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 -
27 27  === Contributor ===
13 +* **Responsibilities**: Submit claims, draft scenarios, attach evidence.
14 +* **Permissions**: Create/Edit drafts, comment.
15 +* **Limitations**: Cannot publish without review.
28 28  
29 -**Who**: Registered and logged-in users (extends Reader capabilities).
30 -
31 -**Can**:
32 -* Everything a Reader can do
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
39 -
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
44 -
45 45  === Reviewer ===
18 +* **Responsibilities**: Validate contributions, check consistency.
19 +* **Permissions**: Change status to "Published" or "Rejected".
46 46  
47 -**Who**: Trusted community members, appointed by maintainers.
21 +=== Expert ===
22 +* **Responsibilities**: Domain-specific judgment, refine assumptions.
23 +* **Permissions**: Attach expert annotations, propose re-evaluation.
48 48  
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
58 -
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
64 -
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
69 -
70 -=== Expert (Domain-Specific) ===
71 -
72 -**Who**: Subject-matter specialists in specific domains (medicine, law, science, etc.).
73 -
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)
82 -
83 -**Cannot**:
84 -* Change platform governance policies
85 -* Approve content outside their expertise domain
86 -* Bypass technical quality gates (but can flag for adjustment)
87 -
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
91 -
92 -=== Auditor ===
93 -
94 -**Who**: Reviewers or Experts assigned to sampling audit duties.
95 -
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
103 -
104 -**Cannot**:
105 -* Change audit sampling algorithms (maintainer responsibility)
106 -* Bypass normal review workflows
107 -* Audit content they personally created
108 -
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)
113 -
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
118 -
119 119  === Moderator ===
26 +* **Responsibilities**: Handle abuse, spam, and manipulation.
27 +* **Permissions**: Hide content, ban users.
120 120  
121 -**Who**: Maintainers or trusted long-term contributors.
29 +=== Maintainer / Administrator ===
30 +* **Responsibilities**: Node config, security, role assignment.
31 +* **Permissions**: System configuration.
122 122  
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
33 +=== AKEL (AI) ===
34 +* **Responsibilities**: Propose drafts, normalize, classify.
35 +* **Permissions**: Create machine-generated drafts.
36 +* **Limitations**: Never publishes without human approval.
132 132  
133 -**Cannot**:
134 -* Change core data model or architecture
135 -* Override technical system constraints
136 -* Make unilateral governance decisions without consensus
38 +== Functional Requirements ==
137 137  
138 -=== Maintainer ===
40 +=== Claim Intake & Normalization ===
41 +* **FR1**: Support text, URL, document input.
42 +* **FR2**: Normalize wording while preserving original.
43 +* **FR3**: Classify by domain/type.
44 +* **FR4**: Cluster similar claims.
139 139  
140 -**Who**: Core team members responsible for the platform.
46 +=== Scenario System ===
47 +* **FR5**: Create scenarios linked to clusters.
48 +* **FR6**: Require Definitions, Assumptions, Boundaries.
49 +* **FR7**: Full versioning.
50 +* **FR8**: Side-by-side comparison.
141 141  
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
52 +=== Evidence Management ===
53 +* **FR9**: Ingest external sources.
54 +* **FR10**: Assess reliability/quality.
55 +* **FR11**: Link evidence to multiple scenarios.
152 152  
153 -**Governance**:
154 -* Maintainers operate under organizational governance rules
155 -* Major policy changes require Governing Team approval
156 -* Technical decisions made collaboratively
57 +=== Verdicts & Truth Landscape ===
58 +* **FR12**: Likelihood-based verdicts **per scenario**.
59 +* **FR13**: Aggregate into Truth Landscape.
60 +* **FR14**: Show evolution over time.
157 157  
158 -----
62 +=== Workflow & Audit ===
63 +* **FR15**: Draft -> Review -> Publish states.
64 +* **FR16**: Moderation tools.
65 +* **FR17**: Full audit trail.
159 159  
160 -== Content Publication States ==
67 +== Federation Requirements ==
161 161  
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
69 +* **FR18**: Node autonomy.
70 +* **FR19**: Configurable data sharing.
71 +* **FR20**: Sync with conflict handling.
72 +* **FR21**: Node discovery.
167 167  
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
74 +== Non-Functional Requirements ==
179 179  
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
76 +* **NFR1 - Transparency**: Visible reasoning and AKEL labeling.
77 +* **NFR2 - Security**: Role-based access, secure storage.
78 +* **NFR3 - Privacy**: Minimal data retention, compliance hooks.
79 +* **NFR4 - Performance**: < 2s response (POC).
80 +* **NFR5 - Scalability**: Support thousands of users (Release 1.0).
81 +* **NFR6 - Interoperability**: Open API.
82 +* **NFR7 - Observability**: Metrics and logs.
83 +* **NFR8 - Maintainability**: Modular architecture.
84 +* **NFR9 - Usability**: Progressive disclosure of complexity.
187 187  
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
86 +== Release Levels ==
193 193  
194 -----
88 +* **POC (Fully Automated)**: Single node. **"Text to Truth Landscape"** workflow. Automated extraction, scenario generation, and verdict computation.
89 +* **Beta 0**: Few nodes, external testers. Expanded manual workflows and moderation.
90 +* **Release 1.0**: Scalable, Federated, High Automation. Multi-node federation.
195 195  
196 -== Contribution Rules ==
197 -
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
204 -
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
213 -
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
220 -
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
227 -
228 -----
229 -
230 -== Quality Standards ==
231 -
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
238 -
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
245 -
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
252 -
253 -----
254 -
255 -== Risk Tier Assignment ==
256 -
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
260 -
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
268 -
269 -**Tier B Indicators**:
270 -* Complex scientific causality
271 -* Contested policy domains
272 -* Historical interpretation with political implications
273 -* Significant economic impact claims
274 -
275 -**Tier C Indicators**:
276 -* Established historical facts
277 -* Simple definitions
278 -* Well-documented scientific consensus
279 -* Basic reference information
280 -
281 -----
282 -
283 -== Related Pages ==
284 -
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]]
289 -