Skip to Content

Changes for page Versioning Architecture

Last modified by Robert Schaub on 2025/12/24 20:34
From version 2.1
edited by Robert Schaub
on 2025/12/12 09:32
Change comment: Imported from XAR
To version 3.6
edited by Robert Schaub
on 2025/12/24 20:34
Change comment: Renamed back-links.

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,1 @@
1 -FactHarbor.Specification.Diagrams.WebHome
1 +Archive.FactHarbor V0\.9\.18 copy.Specification.Diagrams.WebHome
Content
... ... @@ -1,26 +1,40 @@
1 1  **Versioning Architecture**
2 2  
3 -{{mermaid}}
4 -graph TD
5 - subgraph Claims
6 - C1[Claim v1] --> C2[Claim v2] --> C3[Claim v3]
7 - end
8 -
9 - subgraph Scenarios
10 - S1[Scenario v1] --> S2[Scenario v2]
11 - end
12 -
13 - subgraph Evidence
14 - E1[Evidence v1] --> E2[Evidence v2] --> E3[Evidence v3]
15 - end
16 -
17 - subgraph Verdicts
18 - V1[Verdict v1] --> V2[Verdict v2] --> V3[Verdict v3]
19 - end
20 -
21 - Note[Each Version Stores:
22 -- ParentVersionID
23 -- AuthorType
24 -- Timestamp
25 -- Justification]
26 -{{/mermaid}}
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}}