Wiki source code of Federation Architecture
Version 4.1 by Robert Schaub on 2025/12/15 16:56
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | **Federation Architecture** |
| 2 | |||
| |
4.1 | 3 | This diagram shows the complete federated architecture with consistent node representation. |
| |
1.1 | 4 | |
| |
4.1 | 5 | == Architecture Overview == |
| |
1.1 | 6 | |
| |
4.1 | 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 |