SYSTEM ARCHITECTURE
End-to-end view: Vue UI → Kong gateway → FastAPI → MCP servers → live and scenario data sources. Langfuse traces every agent run.
MCP SERVER TOPOLOGY
Three servers scoped by access domain. Each exposes tools, resources, and prompts. FCE connects to shared + passenger. Handover connects to shared + ops.
FCE AGENT — BEHIND EVERY DEPARTURE
Passenger notification agent. Triages flight status, gathers context from 5 parallel tool calls (including live weather and FAA data), synthesizes an empathetic notification.
SHIFT HANDOVER AGENT
Ops briefing agent. Scans all hubs in parallel, scores issues by severity × time sensitivity, categorizes into IMMEDIATE / MONITOR / FYI, generates a structured brief.
DATA FLOW — REAL vs MOCK
Weather and FAA airport status are live (no API key). Flight, crew, passenger, and maintenance data are scenario-based fixtures switchable from the UI.
DEPLOYMENT
Kind cluster for dev (Tilt), docker-compose for quick start, EC2 for production demo. Entry point: localhost:8040.
REPOSITORY STRUCTURE
Monorepo: MCP servers, agents, IRROP engine, API, Vue UI (with shared component framework), and deployment configs.
