Federation Architecture
Last modified by Robert Schaub on 2025/12/24 20:34
Federation Architecture
This diagram shows the complete federated architecture with consistent node representation.
Architecture Overview
Consistent Node Structure:
Each node (A, B, C) has identical components:
- Database: Local storage for claims, scenarios, evidence, verdicts
- AKEL Instance: AI processing specific to that node
- Users: Local community (Contributors, Reviewers, Experts, Moderators)
Federation Sync Layer:
- Coordinates data exchange between nodes
- Handles version bundles with cryptographic signatures
- Enforces trust model (Trusted/Neutral/Untrusted)
- Manages conflict resolution and branching
AKEL Knowledge Exchange (dotted lines):
- Direct peer-to-peer between AKEL instances
- Shares embeddings and contradiction alerts
- Independent from content synchronization
- Never shares model weights or training data
Optional Storage (IPFS/S3):
- Distributed storage for large evidence files
- Content-addressed for integrity
- Reduces duplication across nodes
Data Flow:
- Node creates new version
2. Sync Layer packages as signed bundle
3. Pushed to trusted nodes
4. Remote validation and import
5. AKEL instances exchange knowledge
6. Large files via shared storage
graph TB
subgraph Node_A[Node A]
A_DB[(Database)]
A_AKEL[AKEL Instance]
A_Users[Users]
end
subgraph Node_B[Node B]
B_DB[(Database)]
B_AKEL[AKEL Instance]
B_Users[Users]
end
subgraph Node_C[Node C]
C_DB[(Database)]
C_AKEL[AKEL Instance]
C_Users[Users]
end
subgraph Federation_Layer[Federation Infrastructure]
Sync[Sync Layer
Version Bundles
Signatures & Trust]
Storage[(IPFS / S3
Evidence Files)]
end
Node_A <-->|Content Sync| Sync
Node_B <-->|Content Sync| Sync
Node_C <-->|Content Sync| Sync
A_AKEL -.->|Knowledge Exchange| B_AKEL
B_AKEL -.->|Knowledge Exchange| C_AKEL
A_AKEL -.->|Knowledge Exchange| C_AKEL
Sync -.->|Large Files| Storage
Storage -.-> Node_A
Storage -.-> Node_B
Storage -.-> Node_C