Skip to Content

Changes for page Data Model

Last modified by Robert Schaub on 2025/12/24 21:46
From version 1.1
edited by Robert Schaub
on 2025/12/18 12:03
Change comment: Imported from XAR
To version 4.1
edited by Robert Schaub
on 2025/12/19 14:58
Change comment: Imported from XAR

Summary

Details

Page properties
Content
... ... @@ -157,8 +157,6 @@
157 157  * **description** (text): Human-readable description of the scenario
158 158  * **assumptions** (JSONB): Key assumptions that define this scenario context
159 159  * **extracted_from** (UUID): Reference to evidence that this scenario was extracted from
160 -* **verdict_summary** (text): Compiled verdict for this scenario
161 -* **confidence** (decimal 0-1): Confidence level for verdict in this scenario
162 162  * **created_at** (timestamp): When scenario was created
163 163  * **updated_at** (timestamp): Last modification
164 164  **How Found**: Evidence search → Extract context → Create scenario → Link to claim
... ... @@ -168,7 +168,34 @@
168 168  * Scenario 2: "Real-world data (diverse population, Omicron variant)" from hospital data
169 169  * Scenario 3: "Immunocompromised patients" from specialist study
170 170  **V2.0 Evolution**: Many-to-many relationship can be added if users request cross-claim scenario sharing. For V1.0, keeping scenarios tied to single claims simplifies queries and reduces complexity without limiting functionality.
171 -=== 1.5 User ===
169 +
170 +=== 1.5 Verdict ===
171 +
172 +**Purpose**: Assessment of a claim within a specific scenario context. Each verdict provides a conclusion about whether the claim is supported, refuted, or uncertain given the scenario's assumptions and available evidence.
173 +
174 +**Core Fields**:
175 +* **id** (UUID): Primary key
176 +* **scenario_id** (UUID FK): The scenario being assessed
177 +* **likelihood_range** (text): Probabilistic assessment (e.g., "0.40-0.65 (uncertain)", "0.75-0.85 (likely true)")
178 +* **confidence** (decimal 0-1): How confident we are in this assessment
179 +* **explanation_summary** (text): Human-readable reasoning explaining the verdict
180 +* **uncertainty_factors** (text array): Specific factors limiting confidence (e.g., "Small sample sizes", "Lifestyle confounds", "Long-term effects unknown")
181 +* **created_at** (timestamp): When verdict was created
182 +* **updated_at** (timestamp): Last modification
183 +
184 +**Change Tracking**: Like all entities, verdict changes are tracked through the Edit entity (section 1.7), not through separate version tables. Each edit records before/after states.
185 +
186 +**Relationship**: Each Scenario has one Verdict. When understanding evolves, the verdict is updated and the change is logged in the Edit entity.
187 +
188 +**Example**:
189 +For claim "Exercise improves mental health" in scenario "Clinical trials (healthy adults, structured programs)":
190 +* Initial state: likelihood_range="0.40-0.65 (uncertain)", uncertainty_factors=["Small sample sizes", "Short-term studies only"]
191 +* After new evidence: likelihood_range="0.70-0.85 (likely true)", uncertainty_factors=["Lifestyle confounds remain"]
192 +* Edit entity records the complete before/after change with timestamp and reason
193 +
194 +**Key Design**: Verdicts are mutable entities tracked through the centralized Edit entity, consistent with Claims, Evidence, and Scenarios.
195 +
196 +=== 1.6 User ===
172 172  Fields: username, email, **role** (Reader/Contributor/Moderator), **reputation**, contributions_count
173 173  === User Reputation System ==
174 174  **V1.0 Approach**: Simple manual role assignment
... ... @@ -224,8 +224,8 @@
224 224  * Threshold-based promotions
225 225  * Reputation decay for inactive users
226 226  * Track record scoring for contributors
227 -See [[When to Add Complexity>>FactHarbor.Specification.When-to-Add-Complexity]] for triggers.
228 -=== 1.6 Edit ===
252 +See [[When to Add Complexity>>Test.FactHarbor.Specification.When-to-Add-Complexity]] for triggers.
253 +=== 1.7 Edit ===
229 229  **Fields**: entity_type, entity_id, user_id, before_state (JSON), after_state (JSON), edit_type, reason, created_at
230 230  **Purpose**: Complete audit trail for all content changes
231 231  === Edit History Details ===
... ... @@ -258,9 +258,9 @@
258 258  * Legal compliance (audit trail)
259 259  * Rollback capability
260 260  See **Edit History Documentation** for complete details on what gets edited by whom, retention policy, and use cases
261 -=== 1.7 Flag ===
286 +=== 1.8 Flag ===
262 262  Fields: entity_id, reported_by, issue_type, status, resolution_note
263 -=== 1.8 QualityMetric ===
288 +=== 1.9 QualityMetric ===
264 264  **Fields**: metric_type, category, value, target, timestamp
265 265  **Purpose**: Time-series quality tracking
266 266  **Usage**:
... ... @@ -270,7 +270,7 @@
270 270  * **A/B testing**: Compare control vs treatment metrics
271 271  * **Improvement validation**: Measure before/after changes
272 272  **Example**: `{type: "ErrorRate", category: "Politics", value: 0.12, target: 0.10, timestamp: "2025-12-17"}`
273 -=== 1.9 ErrorPattern ===
298 +=== 1.10 ErrorPattern ===
274 274  **Fields**: error_category, claim_id, description, root_cause, frequency, status
275 275  **Purpose**: Capture errors to trigger system improvements
276 276  **Usage**:
... ... @@ -279,8 +279,13 @@
279 279  * **Improvement workflow**: Analyze → Fix → Test → Deploy → Re-process → Monitor
280 280  * **Metrics**: Track error rate reduction over time
281 281  **Example**: `{category: "WrongSource", description: "Unreliable tabloid cited", root_cause: "No quality check", frequency: 23, status: "Fixed"}`
307 +
308 +== 1.4 Core Data Model ERD ==
309 +
310 +{{include reference="Test.FactHarbor.Specification.Diagrams.Core Data Model ERD.WebHome"/}}
311 +
282 282  == 1.5 User Class Diagram ==
283 -{{include reference="FactHarbor.Specification.Diagrams.User Class Diagram.WebHome"/}}
313 +{{include reference="Test.FactHarbor.Specification.Diagrams.User Class Diagram.WebHome"/}}
284 284  == 2. Versioning Strategy ==
285 285  **All Content Entities Are Versioned**:
286 286  * **Claim**: Every edit creates new version (V1→V2→V3...)
... ... @@ -543,6 +543,6 @@
543 543  * Source names (autocomplete)
544 544  Synchronized from PostgreSQL via change data capture or periodic sync.
545 545  == 4. Related Pages ==
546 -* [[Architecture>>FactHarbor.Specification.Architecture.WebHome]]
547 -* [[Requirements>>FactHarbor.Specification.Requirements.WebHome]]
548 -* [[Workflows>>FactHarbor.Specification.Workflows.WebHome]]
576 +* [[Architecture>>Test.FactHarbor.Specification.Architecture.WebHome]]
577 +* [[Requirements>>Test.FactHarbor.Specification.Requirements.WebHome]]
578 +* [[Workflows>>Test.FactHarbor.Specification.Workflows.WebHome]]