The Pantheon

Pantheon Modules

Olympus is built from specialized Pantheon Modules, each named after a figure from Greek mythology. Every Pantheon Module has a single job. They communicate through a secure internal bus and share persistent memory — but never depend on each other directly.

Active

Core Pantheon Modules

These Pantheon Modules are active in the current release and work together to deliver the full Olympus experience.

Icon	Pantheon Module	Role	What it does for you
⚡	Zeus	Coordinator	Manages your session from start to finish — receives your requests, delegates to the right Pantheon Modules, and keeps everything in sync. Zeus never does the work himself; he makes sure the right specialist handles it.
🦉	Athena	Intent & Validation	Understands what you actually mean and turns it into concrete, verifiable specs. After the work is done, Athena checks that it truly matches your original request. This is the Pantheon Module that prevents AI agents from closing issues with stub implementations.
🌈	Iris	AI Model Routing	Picks the best AI model for each task. Routes to local models first (free, under 200ms), then subscription providers, then pay-per-token APIs as a last resort. Also handles delivering PRs and managing external authentication.
🔗	Hermes	Internal Communication	The secure message bus that connects all Pantheon Modules. Each Pantheon Module has its own cryptographic signing key, so messages can't be spoofed or tampered with. Hermes only carries internal messages — nothing external.
🔨	Hephaestus	Code & Files	The hands that do the work. Handles code generation, branch management, merge conflict resolution, diff creation, and file operations. When Olympus writes or modifies code, Hephaestus is the Pantheon Module doing it.
🛡️	Aegis	Security & Governance	Your security team. Scans for vulnerabilities, detects secrets in code, validates prompts against injection attacks, runs governance review panels, and maintains audit trails. When you see the green indicator, Aegis is why.
👁️	Argus	Observability	The unified observability module. Owns budget enforcement, cost/token tracking with anomaly detection, reasoning traces, autonomy analysis, persona drift detection, and the monitoring dashboard. Registers in the kernel boot sequence at StageReasoning and feeds cost data to Prometheus during the agentic loop.
🐕	Cerberus	Gate Authority	The unified gate authority. Owns three sub-gates: DispatchGate (coverage, batch, pool capacity), CapacityGate (tier-based phase gating fed by the StateMachine), and CostGate (blocks paid LLM calls when free local models are available). Registers in the kernel boot sequence. Runner and Prometheus receive their gates from the unified Cerberus instead of creating them independently.
🧠	Mnemosyne	Memory	The reason Olympus survives crashes and remembers last Tuesday. Stores session state, checkpoints, your preferences, and project history. Encrypted at rest, with optional cloud sync for multi-machine support.
🧩	Epimetheus	Learning	Analyzes what happened after the work is done. Identifies cost patterns, failure modes, and successful strategies — then feeds these insights back so Olympus gets smarter over time.
🔥	Prometheus	Loop Engine	Drives the agentic execution loop from start to finish — phase cycle (preflight → execute → evaluate → iterate), iteration ceiling, execution context isolation, and telemetry. Every autonomous task runs inside a Prometheus loop.
☀️	Apollo	Model Routing	Selects the right AI model for each task based on capability tier, plan entitlements, and cost constraints. Resolves capability requirements (vision, tool-use, context length) to concrete model identifiers before Iris dispatches the request.

Infrastructure

Release Infrastructure

These components support the development and release process. They are not runtime Pantheon Modules — they do not communicate through Hermes or persist through Mnemosyne — but they are essential to verifying that Olympus does what it claims.

Icon	Component	Role	What it does
🔮	Pythia	Release Gate	The Oracle of Delphi — the final arbiter of whether Olympus can do what it claims. Given minimal, ambiguous input, Pythia judges whether the system correctly derived the intent and produced the verified outcome. Five independent scoring dimensions (intent, process, outcome, consistency, integrity) must all clear their thresholds before a release is marketable. Pythia is not a unit test — it is a full functional stress test based on research from LHAW, SWE-bench, CLEAR, and AgentPRM.

Coming Soon

Planned Pantheon Modules

These Pantheon Modules are designed and will follow the same pattern: single responsibility, secure communication, persistent memory.

Icon	Pantheon Module	Role	What it will do
🔮	Pythia	Release Gate	The final arbiter of whether Olympus can do what it claims. Given minimal input, Pythia judges whether the system correctly derived the intent and produced the verified outcome. A release is marketable only when Pythia clears all five scoring dimensions: intent, process, outcome, consistency, and integrity.
🌙	Artemis	Optimization	Finds the most efficient routing paths, tunes latency, and optimizes resource usage.
⚰️	Hades	Archival	Long-term storage for project history that's no longer active but shouldn't be forgotten.
🍎	Persephone	Data Lifecycle	Manages what memory stays active and what gets archived, with configurable retention policies.
🌾	Demeter	Data Ingestion	Processes structured inputs — repository scanning, file parsing, and context extraction.
🍇	Dionysus	Creative Generation	Exploratory and divergent thinking — brainstorming, creative problem-solving, and alternative approaches.
⚔️	Ares	Adversarial Testing	Red team operations and stress testing — finds what breaks before production does.
🏆	Nike	Success Evaluation	Defines and evaluates victory conditions — declares when the work is truly complete.
🌐	Atlas	Workload Distribution	Distributes work across resources for parallel execution and load balancing.
⚙️	Helios	Scheduling	Timed execution, cron jobs, and scheduled tasks — reliable, on-time, every time.
🌘	Selene	Snapshots	Checkpoint and rollback capabilities — rewind to any previous state.
🧬	Metis	Strategy	Meta-reasoning and plan optimization — higher-level strategic thinking.
⚖️	Themis	Policy	Rules and compliance enforcement — ensures every action meets organizational policies.
💤	Hypnos	Background Tasks	Low-priority work that runs while you're away — idle optimization, deferred processing.
☁️	Morpheus	Simulation	What-if analysis and branching scenarios — explore possibilities before committing.
📢	Echo	Replay	Event recording and session playback — review exactly what happened, when, and why.

Integration

How everything connects

flowchart TD subgraph Developer["YOU"] DEV["Natural conversation"] end subgraph TUI["OLYMPUS"] OLY["⚡ Zeus\nCoordinator"] end subgraph Bus["🔗 HERMES — Secure Message Bus"] direction LR E1["security events"] E2["intent events"] E3["code events"] E4["CI events"] E5["gate events"] E6["routing events"] end subgraph Modules["PANTHEON MODULES"] direction LR ATHENA["🦉 Athena\nIntent"] AEGIS["🛡️ Aegis\nSecurity"] HEPH["🔨 Hephaestus\nCode"] ARGUS["👁️ Argus\nMonitor"] CERB["🐕 Cerberus\nCost"] EPIM["🧩 Epimetheus\nLearning"] end subgraph External["🌈 IRIS — AI Model Routing"] direction LR LOCAL["Local Model\nfree · <200ms"] SUB1["Subscription\nno per-token cost"] SUB2["Subscription Fallback\nno per-token cost"] PAID["Pay-per-token\nlast resort"] DELIVERY["Delivery\nPRs · Issues"] end subgraph Memory["🧠 MNEMOSYNE — Persistent Memory"] direction LR SESSIONS["sessions"] INTENTS["intents"] PRSTATE["pr_state"] CIHISTORY["ci_history"] CONFLICTS["conflict_log"] PREFS["preferences"] end DEV --> OLY OLY --> Bus Bus --> Modules Modules --> Bus OLY --> External External --> OLY Modules --> Memory Memory --> Modules OLY --> Memory style Developer fill:#1F2328,color:#E5E7EB,stroke:#6B7280 style TUI fill:#0A3D62,color:#E5E7EB,stroke:#3FA7D6 style Bus fill:#2F343A,color:#FF6A00,stroke:#FF6A00 style Modules fill:#1F2328,color:#3FA7D6,stroke:#3FA7D6 style External fill:#082C4A,color:#E5E7EB,stroke:#145DA0 style Memory fill:#2F343A,color:#FFD2A6,stroke:#FF8C1A style OLY fill:#0A3D62,color:#FF6A00,stroke:#FF6A00 style ATHENA fill:#145DA0,color:#E5E7EB,stroke:#3FA7D6 style AEGIS fill:#145DA0,color:#E5E7EB,stroke:#3FA7D6 style HEPH fill:#145DA0,color:#E5E7EB,stroke:#3FA7D6 style ARGUS fill:#145DA0,color:#E5E7EB,stroke:#3FA7D6 style CERB fill:#145DA0,color:#E5E7EB,stroke:#3FA7D6 style EPIM fill:#145DA0,color:#E5E7EB,stroke:#3FA7D6 style SESSIONS fill:#3A4047,color:#FFD2A6,stroke:#FF8C1A style INTENTS fill:#3A4047,color:#FFD2A6,stroke:#FF8C1A style PRSTATE fill:#3A4047,color:#FFD2A6,stroke:#FF8C1A style CIHISTORY fill:#3A4047,color:#FFD2A6,stroke:#FF8C1A style CONFLICTS fill:#3A4047,color:#FFD2A6,stroke:#FF8C1A style PREFS fill:#3A4047,color:#FFD2A6,stroke:#FF8C1A

In Practice

How modules collaborate

Example: Hephaestus hits a merge conflict

🔨(Hephaestus): "I've hit a merge conflict"
🧠(Mnemosyne): "Last time, the developer preferred 'theirs' for this file"
🔨(Hephaestus): Resolves using historical preference
🧠(Mnemosyne): Stores this resolution for next time
🔗(Hermes): Notifies all Pantheon Modules — conflict resolved

Example: Self-healing needs a paid model

🔨(Hephaestus): "I need AI help to resolve this conflict"
🐕(Cerberus): "Local models are down — cloud would cost money"
🐕(Cerberus): Pauses and asks you: wait, pay, or skip?
You choose "wait"
🐕(Cerberus): Polls local models every 30 seconds
🔨(Hephaestus): Local model is back — conflict resolved for free