Changes for page Federation Architecture

Last modified by Robert Schaub on 2025/12/24 20:34

From version 2.1
edited by Robert Schaub
on 2025/12/12 08:32
Change comment: Imported from XAR
To version 4.2
edited by Robert Schaub
on 2025/12/16 20:28
Change comment: Renamed back-links.

Summary

Details

Page properties
Content
... ... @@ -1,24 +1,43 @@
1 1  **Federation Architecture**
2 2  
3 -{{mermaid}}
4 -graph TD
5 - Sync[Federation Sync Layer
6 -- Version Bundles
7 -- Merkle Trees
8 -- Signatures/Trust]
9 -
10 - IPFS((IPFS / S3 / P2P
11 -Evidence Files - Optional))
3 +This diagram shows the complete federated architecture with consistent node representation.
12 12  
13 - NodeA[Node A
14 -Community/Domain] --> Sync
15 - NodeB[Node B
16 -Community/Domain] --> Sync
17 - NodeC[Node C
18 -Org/Region] --> Sync
5 +== Architecture Overview ==
19 19  
20 - Sync -.-> IPFS
21 - IPFS -.-> NodeA
22 - IPFS -.-> NodeB
23 - IPFS -.-> NodeC
24 -{{/mermaid}}
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="FactHarbor.Archive.FactHarbor V0\.9\.23 Lost Data.Specification.Diagrams.Federation Architecture_Mermaid.WebHome"}}{{/include}}