Architecture
Pantheon Module Domains
Every capability in Olympus has exactly one owner. This page explains which Pantheon Module is responsible for what — and how edge cases are resolved when a feature could belong to more than one.
Ownership
Who owns what
| Pantheon Module | Inspired by | Owns |
|---|---|---|
| ⚡ Zeus | King of the gods | Session orchestration, task delegation, workflow coordination |
| 🔗 Hermes | The messenger | Internal message bus, event dispatch between modules |
| 🌈 Iris | Divine messenger | AI model routing, external delivery, provider authentication |
| 🦉 Athena | Goddess of wisdom | Intent understanding, spec creation, completion validation |
| 🔨 Hephaestus | God of the forge | Code generation, file operations, branch management |
| 🧠 Mnemosyne | Goddess of memory | Persistent state, session recovery, cross-session history |
| 🛡️ Aegis | Zeus's shield | Security scanning, governance reviews, audit trails |
| 👁️ Argus | Hundred-eyed giant | Cost tracking, CI monitoring, usage metrics |
| 🐕 Cerberus | Guardian of the gate | Cost gates, preflight checks, circuit breakers |
| 🧩 Epimetheus | God of afterthought | Outcome analysis, pattern learning, improvement recommendations |
Zeus
⚡ Zeus — the thin coordinator
Zeus manages the big picture but never does the work himself. He starts sessions, delegates tasks to the right Pantheon Modules, and makes sure everything stays in sync.
| Zeus handles | Zeus delegates to |
|---|---|
| Starting, stopping, and resuming sessions | Security policy → Aegis |
| Deciding which module handles a task | Memory and state → Mnemosyne |
| Coordinating multi-module workflows | AI model selection → Iris |
| Managing the command registry | Code generation → Hephaestus |
Edge Cases
When a feature could belong to two Pantheon Modules
These rules are applied in order to determine ownership:
| Priority | Question | Owner |
|---|---|---|
| 1 | Does it enforce or evaluate trust? | 🛡️ Aegis |
| 2 | Does it persist state across sessions? | 🧠 Mnemosyne |
| 3 | Does it call an external service? | 🌈 Iris |
| 3a | Does it route internal messages? | 🔗 Hermes |
| 4 | Does it create or modify files? | 🔨 Hephaestus |
| 5 | Does it ask "should this proceed?" | 🐕 Cerberus |
| 6 | Is it read-only monitoring? | 👁️ Argus |
| 7 | Does it understand intent? | 🦉 Athena |
| 8 | Does it coordinate multiple Pantheon Modules? | ⚡ Zeus |
Examples
Common questions answered
| Capability | Owner | Why |
|---|---|---|
| Detecting secrets in code | 🛡️ Aegis | Trust and security concern |
| Compressing conversation context | 🧠 Mnemosyne | Memory management |
| Stopping runaway API costs | 🐕 Cerberus | Gate decision — "should this proceed?" |
| Masking API keys in logs | 🌈 Iris | External provider communication |
| Recording audit events | 🛡️ Aegis | Trust and compliance trail |
| Tracking token usage | 👁️ Argus | Read-only monitoring |
| Enforcing spending limits | 🛡️ Aegis | Security control |
| Classifying what you meant | 🦉 Athena | Intent understanding |
| Running governance reviews | 🛡️ Aegis | Trust and compliance |
| Saving session checkpoints | 🧠 Mnemosyne | Cross-session persistence |
Coming Soon
Future Pantheon Modules
| Pantheon Module | Planned role |
|---|---|
| 🔥 Prometheus | Static analysis and foresight — catching problems before execution |
| ☀️ Apollo | Code intelligence — deep understanding of codebases |
| 🍇 Dionysus | Creative and exploratory modes — brainstorming and divergent thinking |
| ⚔️ Ares | Adversarial testing — red-teaming and stress testing |
| ⚰️ Hades | Archival — long-term storage and dead code management |