Cosmo’s architecture is built around a central core that coordinates modular systems without forcing every part of the robot into one monolithic process.
Cosmo Core
|-- Runtime
|-- Event Bus
|-- State Manager
|-- Voice Pipeline
|-- Memory Layer
|-- SQLite Persistence
|-- WebUI
|-- Automation
`-- Robotics BridgeCore blocks
Runtime is the main asynchronous process. It starts services, schedules tasks, and keeps the system alive.
Event Bus handles communication between modules so that perception, cognition, UI, and automation can react to shared events.
State Manager controls the operational state of the robot and prevents overlapping behavior.
Voice Pipeline coordinates wake word detection, STT, cognition, and TTS.
Memory Layer stores and retrieves context, personality traits, interaction notes, and future long-term records.
SQLite Persistence provides durable logs, history, and persistent state.
WebUI gives Cosmo a visual interface for observation, control, debugging, and future interaction.
Automation runs local actions, routines, and system tasks.
Robotics Bridge is the future communication path between the laptop-based core and an ESP32 or physical robotic body.