High-Level Architecture

High-Level Architecture

graph TB
 subgraph Interface_Layer["🖥️ Interface Layer"]
 UI[Web UI
Browse & Submit]
 API[REST API
Programmatic Access]
 AUTH[Authentication
& Authorization]
 end
 subgraph Processing_Layer["⚙️ Processing Layer"]
 AKEL[AKEL Pipeline
Parallel Processing
10-18 seconds]
 LLM[LLM Abstraction Layer
Multi-Provider Support
Anthropic OpenAI Google]
 BG[Background Jobs
Source Scoring,
Cache, Archival]
 QM[Quality Monitoring
Automated Checks]
 end
 subgraph Data_Layer["💾 Data & Storage Layer"]
 PG[(PostgreSQL
Primary Database
All Core Data)]
 REDIS[(Redis
Cache & LLM Config)]
 S3[(S3
Archives)]
 end
 UI --> AUTH
 API --> AUTH
 AUTH --> AKEL
 AUTH --> QM
 AKEL --> LLM
 LLM --> PG
 LLM --> REDIS
 AKEL --> PG
 AKEL --> REDIS
 BG --> PG
 BG --> S3
 QM --> PG
 REDIS --> PG
 style Interface_Layer fill:#e1f5ff
 style Processing_Layer fill:#fff4e1
 style Data_Layer fill:#f0f0f0
 style AKEL fill:#ffcccc
 style LLM fill:#ccffcc
 style PG fill:#9999ff

Three-Layer Architecture - Clean separation with LLM abstraction: Interface Layer (user interactions), Processing Layer (AKEL + LLM Abstraction + background jobs), Data Layer (PostgreSQL primary + Redis cache/config + S3 archives). LLM Abstraction Layer provides provider-agnostic access to Anthropic, OpenAI, Google, and local models with automatic failover.