Changes for page Data Model
Last modified by Robert Schaub on 2025/12/24 20:34
From version 6.3
edited by Robert Schaub
on 2025/12/16 20:26
on 2025/12/16 20:26
Change comment:
Update document after refactoring.
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -5,6 +5,7 @@ 5 5 == Versioning Strategy == 6 6 7 7 Every entity in FactHarbor has a full immutable version history. This ensures: 8 + 8 8 * Complete auditability 9 9 * Ability to reconstruct historical state 10 10 * Federation-compatible lineage tracking ... ... @@ -13,16 +13,19 @@ 13 13 === Core Versioning Principles === 14 14 15 15 **Immutability**: 17 + 16 16 * Each version is stored independently 17 17 * Versions cannot be deleted, only superseded 18 18 * Historical versions remain accessible 19 19 20 20 **Lineage**: 23 + 21 21 * Each version links to its parent via `ParentVersionID` 22 22 * Forms directed acyclic graph (DAG) of changes 23 23 * Supports branching in federated environments 24 24 25 25 **Provenance**: 29 + 26 26 * Every version timestamped (`CreatedAt`) 27 27 * Author type recorded (`AuthorType`: Human, AI, ExternalNode) 28 28 * Justification captured (`JustificationText`) ... ... @@ -29,6 +29,7 @@ 29 29 * Digital signatures for integrity (`SignatureHash` in Release 1.0) 30 30 31 31 **Federation Support**: 36 + 32 32 * Versions can originate from remote nodes 33 33 * Conflict detection via lineage comparison 34 34 * Parallel version trees for branching scenarios ... ... @@ -56,6 +56,7 @@ 56 56 === User Entities === 57 57 58 58 **USER** (base user table): 64 + 59 59 * ``UserID`` (PK) 60 60 * ``UserType`` (Reader|Contributor|Reviewer|Auditor|Expert|Moderator|Maintainer) 61 61 * ``DisplayName`` ... ... @@ -65,6 +65,7 @@ 65 65 * ``Status`` (active|suspended|banned) 66 66 67 67 **TECHNICAL_USER** (system processes): 74 + 68 68 * ``SystemID`` (PK) 69 69 * ``SystemName`` 70 70 * ``Purpose`` (AKEL|FederationSync|BackupService|Monitor|Audit) ... ... @@ -75,6 +75,7 @@ 75 75 * ``Permissions`` (JSON - authorized operations) 76 76 77 77 **Examples of Technical Users**: 85 + 78 78 * AKEL instances (AI processing) 79 79 * Federation sync bots 80 80 * Scheduled audit tasks ... ... @@ -89,6 +89,7 @@ 89 89 The system relies on the following versioned core entities: 90 90 91 91 **CLAIM_CLUSTER**: 100 + 92 92 * ``ClusterID`` (PK) 93 93 * ``EmbeddingVectorRef`` 94 94 * ``Theme`` ... ... @@ -97,77 +97,81 @@ 97 97 * A Claim belongs to exactly one primary cluster 98 98 99 99 **CLAIM / CLAIM_VERSION**: 109 + 100 100 * ``CLAIM`` is the long-lived anchor for a real-world claim 101 101 * ``CLAIM_VERSION`` is an immutable snapshot that includes: 102 - 103 - 104 - 105 - 106 - 107 - 108 - 109 - 110 - 111 - 112 - 113 - 114 - 112 +* ``VersionID`` (PK) 113 +* ``ClaimID`` (FK to CLAIM) 114 +* ``ParentVersionID`` (FK to prior version, nullable) 115 +* ``Text`` 116 +* ``Domain`` 117 +* ``ClaimType`` (literal|metaphorical|rhetorical|supernatural) 118 +* ``Evaluability`` (empirical|subjective|non-falsifiable) 119 +* ``RiskTier`` (A|B|C) - replaced SafetyCategory for consistency 120 +* ``PublicationMode`` (Mode1|Mode2|Mode3) 121 +* ``ReviewStatus`` (draft|in_review|approved|rejected) 122 +* ``CreatedAt``, ``AuthorType``, ``CreatedBy``, ``JustificationText`` 123 +* ``NodeOrigin``, ``SignatureHash`` 124 +* ``Status`` (active|superseded|merged) 115 115 116 116 **SCENARIO / SCENARIO_VERSION**: 127 + 117 117 * ``SCENARIO`` is the anchor for a scenario across time 118 118 * ``SCENARIO_VERSION`` is an immutable snapshot: 119 - 120 - 121 - 122 - 123 - 124 - 125 - 126 - 127 - 128 - 129 - 130 - 131 - 132 - 130 +* ``VersionID`` (PK) 131 +* ``ScenarioID`` (FK to SCENARIO) 132 +* ``ParentVersionID`` 133 +* ``ClaimID`` (FK to CLAIM) 134 +* ``Definitions`` (JSON) 135 +* ``Boundaries`` (JSON) 136 +* ``Assumptions`` (JSON) 137 +* ``Context`` (text) 138 +* ``EvaluationMethod`` (text) 139 +* ``PublicationMode`` (Mode1|Mode2|Mode3) 140 +* ``ReviewStatus`` (draft|in_review|approved|rejected) 141 +* ``CreatedAt``, ``AuthorType``, ``CreatedBy``, ``JustificationText`` 142 +* ``NodeOrigin``, ``SignatureHash`` 143 +* ``Status`` (active|superseded|deprecated) 133 133 134 134 **Note**: SafetyClass removed from Scenario - risk tier is at claim level 135 135 136 136 **EVIDENCE / EVIDENCE_VERSION**: 148 + 137 137 * ``EVIDENCE`` is the anchor 138 138 * ``EVIDENCE_VERSION`` is the versioned snapshot: 139 - 140 - 141 - 142 - 143 - 144 - 145 - 146 - 147 - 148 - 149 - 150 - 151 - 152 - 151 +* ``VersionID`` (PK) 152 +* ``EvidenceID`` (FK to EVIDENCE) 153 +* ``ParentVersionID`` 154 +* ``Type`` (paper|dataset|report|transcript|expert|media) 155 +* ``Category`` (empirical|historical|rhetorical|dataset|meta-analysis) 156 +* ``Reliability`` (low|medium|high) 157 +* ``Provenance`` (URL, DOI, source metadata) 158 +* ``ExtractionMethod`` (manual|OCR|API|AKEL) 159 +* ``ContentHash`` (SHA256 of evidence content) 160 +* ``PublicationMode`` (Mode1|Mode2|Mode3) 161 +* ``ReviewStatus`` (draft|verified|disputed|retracted) 162 +* ``CreatedAt``, ``AuthorType``, ``CreatedBy``, ``JustificationText`` 163 +* ``NodeOrigin``, ``SignatureHash`` 164 +* ``Status`` (active|superseded) 153 153 154 154 **VERDICT / VERDICT_VERSION**: 167 + 155 155 * ``VERDICT`` is the anchor 156 156 * ``VERDICT_VERSION`` is the snapshot: 157 - 158 - 159 - 160 - 161 - 162 - 163 - 164 - 165 - 166 - 167 - 168 - 169 - 170 - 170 +* ``VersionID`` (PK) 171 +* ``VerdictID`` (FK to VERDICT) 172 +* ``ParentVersionID`` 173 +* ``ClaimID`` (FK to CLAIM) 174 +* ``ScenarioVersionID`` (FK to specific SCENARIO_VERSION) 175 +* ``EvidenceVersionSet`` (JSON array of Evidence VersionIDs used) 176 +* ``LikelihoodRange`` (0–1, with uncertainty bounds) 177 +* ``ExplanationChain`` (JSON) 178 +* ``UncertaintyFactors`` (JSON) 179 +* ``PublicationMode`` (Mode1|Mode2|Mode3) 180 +* ``ReviewStatus`` (draft|in_review|approved|retracted) 181 +* ``CreatedAt``, ``AuthorType``, ``CreatedBy``, ``JustificationText`` 182 +* ``NodeOrigin``, ``SignatureHash`` 183 +* ``Status`` (current|outdated|superseded|retracted) 171 171 172 172 ---- 173 173 ... ... @@ -174,6 +174,7 @@ 174 174 == Many-to-Many Linking Tables == 175 175 176 176 **ScenarioEvidenceLink**: 190 + 177 177 * Links scenario versions to evidence versions with relevance scoring 178 178 * ``ScenarioID``, ``ScenarioVersionID`` 179 179 * ``EvidenceID``, ``EvidenceVersionID`` ... ... @@ -181,6 +181,7 @@ 181 181 * ``LinkJustification`` - Brief explanation of relevance 182 182 183 183 **Purpose**: 198 + 184 184 * Evidence can be used by multiple scenarios 185 185 * Scenarios can draw from multiple pieces of evidence 186 186 * Relevance scoring helps prioritize evidence ... ... @@ -187,6 +187,7 @@ 187 187 * Version-specific linking preserves historical accuracy 188 188 189 189 **ClaimCluster**: 205 + 190 190 * Semantic clustering of similar claims 191 191 * ``ClusterID`` (PK) 192 192 * ``EmbeddingVector`` - Vector representation for semantic search ... ... @@ -198,10 +198,12 @@ 198 198 == Key Changes in v0.9.1 == 199 199 200 200 **Updated Field Names**: 217 + 201 201 * `SafetyCategory` → `RiskTier` (consistency with risk tier system A/B/C) 202 202 * `SafetyClass` removed from Scenario (redundant with claim-level RiskTier) 203 203 204 204 **Added Fields to All Version Entities**: 222 + 205 205 * `PublicationMode` - Track Mode 1/2/3 status 206 206 * `ReviewStatus` - Track workflow state 207 207 * `NodeOrigin` - Federation provenance ... ... @@ -208,9 +208,11 @@ 208 208 * `CreatedBy` - FK to User/TechnicalUser (clarified) 209 209 210 210 **New Entity**: 229 + 211 211 * `TECHNICAL_USER` - Separate system processes from human users 212 212 213 213 **Clarifications**: 233 + 214 214 * `ScenarioVersionID` in Verdict (not just ScenarioID) - links to specific version 215 215 * `ContentHash` in Evidence - SHA256 for integrity checking 216 216 ... ... @@ -221,6 +221,7 @@ 221 221 === Late-Arriving Evidence === 222 222 223 223 When new evidence versions appear: 244 + 224 224 1. Existing verdicts marked as **outdated** 225 225 2. Scenario relevance must be re-evaluated 226 226 3. Re-evaluation engine triggers verdict recomputation ... ... @@ -230,6 +230,7 @@ 230 230 === Scenario Evolution === 231 231 232 232 When a scenario's assumptions or definitions change: 254 + 233 233 * Creates new scenario version (not in-place update) 234 234 * All dependent verdicts must be recalculated 235 235 * Previous scenario versions remain accessible ... ... @@ -238,6 +238,7 @@ 238 238 === Federated Nodes === 239 239 240 240 Each node may share partial data: 263 + 241 241 * Claims and scenarios shared if relevant 242 242 * Evidence metadata shared, not always full files 243 243 * Version synchronization via NodeOrigin tracking ... ... @@ -251,7 +251,7 @@ 251 251 252 252 === Core Data Model ERD === 253 253 254 -{{include reference=" Test.FactHarborV09.Specification.Diagrams.Core Data Model ERD.WebHome"/}}277 +{{include reference="FactHarbor.Archive.FactHarbor V0\.9\.23 Lost Data.Specification.Diagrams.Core Data Model ERD.WebHome"/}} 255 255 256 256 === User Roles Structure === 257 257 ... ... @@ -266,6 +266,5 @@ 266 266 == Related Pages == 267 267 268 268 * [[Federation & Decentralization>>FactHarbor.Specification.Federation & Decentralization.WebHome]] 269 -* [[AKEL (AI Knowledge Extraction Layer)>>FactHarbor.Specification.AI Knowledge Extraction Layer (AKEL).WebHome]] 292 +* [[AKEL (AI Knowledge Extraction Layer)>>FactHarbor.Specification V0\.9\.18.AI Knowledge Extraction Layer (AKEL).WebHome]] 270 270 * [[Architecture>>FactHarbor.Specification.Architecture.WebHome]] 271 -