Federation Architecture

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:

1. 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