Skip to Content

Wiki source code of Versioning Architecture

Last modified by Robert Schaub on 2025/12/24 20:34
Show last authors
1 **Versioning Architecture**
2
3 This diagram shows how each entity type maintains its version history with parent-child relationships.
4
5 == Versioning Architecture Explanation ==
6
7 **Version Chains**:
8
9 * Each entity type (Claim, Scenario, Evidence, Verdict) maintains independent version history
10 * **ParentVersionID** creates directed acyclic graph (DAG) of changes
11 * Arrow direction: Old version → New version (evolution over time)
12
13 **Version Metadata** (stored with every version):
14
15 * **VersionID**: Unique identifier for this specific version
16 * **ParentVersionID**: Links to previous version (null for v1)
17 * **AuthorType**: Human, AI, or ExternalNode
18 * **Timestamp**: Creation datetime (UTC)
19 * **JustificationText**: Brief explanation of changes
20
21 **Entity Relationships** (dotted lines):
22
23 * Claims **have** Scenarios: One claim can have multiple scenario interpretations
24 * Scenarios **use** Evidence: Each scenario version references specific evidence versions
25 * Scenarios **produce** Verdicts: Each scenario version gets verdict based on evidence
26
27 **Branching Support**:
28
29 * In federated environments, versions can branch:
30 - Node A: Version 1 → Version 2a
31 - Node B: Version 1 → Version 2b (parallel branch)
32 * Both branches preserved for conflict resolution
33
34 **Immutability**:
35
36 * Versions never deleted, only superseded
37 * Historical versions remain accessible
38 * Complete audit trail for all changes
39
40 {{include reference="Archive.FactHarbor V0\.9\.23 Lost Data.Specification.Diagrams.Versioning Architecture_Mermaid.WebHome"}}{{/include}}