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