Wiki source code of Federation Architecture

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

Hide last authors
Robert Schaub 1.1 1 **Federation Architecture**
2
Robert Schaub 4.1 3 This diagram shows the complete federated architecture with consistent node representation.
Robert Schaub 1.1 4
Robert Schaub 4.1 5 == Architecture Overview ==
Robert Schaub 1.1 6
Robert Schaub 4.1 7 **Consistent Node Structure**:
8 Each node (A, B, C) has identical components:
Robert Schaub 4.4 9
Robert Schaub 4.1 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**:
Robert Schaub 4.4 15
Robert Schaub 4.1 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):
Robert Schaub 4.4 22
Robert Schaub 4.1 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):
Robert Schaub 4.4 29
Robert Schaub 4.1 30 * Distributed storage for large evidence files
31 * Content-addressed for integrity
32 * Reduces duplication across nodes
33
34 **Data Flow**:
Robert Schaub 4.4 35
Robert Schaub 4.1 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
Robert Schaub 4.6 43 {{include reference="Archive.FactHarbor V0\.9\.23 Lost Data.Specification.Diagrams.Federation Architecture_Mermaid.WebHome"}}{{/include}}