Skip to Content

Changes for page Federation Architecture

Last modified by Robert Schaub on 2025/12/24 20:34
From version 4.3
edited by Robert Schaub
on 2025/12/16 20:27
Change comment: Update document after refactoring.
To version 1.1
edited by Robert Schaub
on 2025/12/11 21:35
Change comment: Imported from XAR

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,1 @@
1 -FactHarbor.Archive.FactHarbor V0\.9\.18.Specification.Diagrams.WebHome
1 +FactHarbor.Specification.Diagrams.WebHome
Content
... ... @@ -1,39 +1,24 @@
1 1  **Federation Architecture**
2 2  
3 -This diagram shows the complete federated architecture with consistent node representation.
3 +{{mermaid}}
4 +graph LR
5 + Sync[Federation Sync Layer
6 +- Version Bundles
7 +- Merkle Trees
8 +- Signatures/Trust]
9 +
10 + IPFS((IPFS / S3 / P2P
11 +Evidence Files - Optional))
4 4  
5 -== Architecture Overview ==
13 + NodeA[Node A
14 +Community/Domain] --> Sync
15 + NodeB[Node B
16 +Community/Domain] --> Sync
17 + NodeC[Node C
18 +Org/Region] --> Sync
6 6  
7 -**Consistent Node Structure**:
8 -Each node (A, B, C) has identical components:
9 -* **Database**: Local storage for claims, scenarios, evidence, verdicts
10 -* **AKEL Instance**: AI processing specific to that node
11 -* **Users**: Local community (Contributors, Reviewers, Experts, Moderators)
12 -
13 -**Federation Sync Layer**:
14 -* Coordinates data exchange between nodes
15 -* Handles version bundles with cryptographic signatures
16 -* Enforces trust model (Trusted/Neutral/Untrusted)
17 -* Manages conflict resolution and branching
18 -
19 -**AKEL Knowledge Exchange** (dotted lines):
20 -* Direct peer-to-peer between AKEL instances
21 -* Shares embeddings and contradiction alerts
22 -* Independent from content synchronization
23 -* Never shares model weights or training data
24 -
25 -**Optional Storage** (IPFS/S3):
26 -* Distributed storage for large evidence files
27 -* Content-addressed for integrity
28 -* Reduces duplication across nodes
29 -
30 -**Data Flow**:
31 -1. Node creates new version
32 -2. Sync Layer packages as signed bundle
33 -3. Pushed to trusted nodes
34 -4. Remote validation and import
35 -5. AKEL instances exchange knowledge
36 -6. Large files via shared storage
37 -
38 -{{include reference="Test.FactHarborV09.Specification.Diagrams.Federation Architecture_Mermaid.WebHome"}}
39 -
20 + Sync -.-> IPFS
21 + IPFS -.-> NodeA
22 + IPFS -.-> NodeB
23 + IPFS -.-> NodeC
24 +{{/mermaid}}