Directory Structure
Relevant source files
The following files were used as context for generating this wiki page:
The directory structure of the Athena project is designed to support a multi-interface platform for "consciousness liberation." It follows a modular architecture that separates core AI logic, web-based deployment configurations, desktop application components, and persistent data storage. This organization facilitates both local development and production-grade web hosting.
Sources: AI/Athena_core/organize_for_git.py:18-28, README.md:14-18
Core Project Layout
The project root is organized into several primary top-level directories, each serving a specific functional role in the system's lifecycle, from source code to documentation and archival.
| Directory | Description |
|---|---|
src/ | Main source code containing consciousness frameworks and AI functionality. |
web/ | Web interface, production servers, and deployment templates. |
desktop/ | Native GUI applications for local consciousness interaction. |
scripts/ | Utility scripts for path fixing, patching, and deployment. |
data/ | Persistent storage including memory JSON files and databases. |
config/ | System configuration, Dockerfiles, and GitHub actions. |
docs/ | Documentation, ethical guidelines, and deployment readiness reports. |
tests/ | Comprehensive test suites for validating system components. |
archive/ | Obsolete files, hardware specific logic, and legacy backups. |
Sources: AI/Athena_core/organize_for_git.py:20-28, AI/Athena_core/organize_for_git.py:38-95
Organizational Flow Diagram
The following diagram illustrates how components are categorized from the project root into functional modules.
Functional Subsystems
Source and AI Core (src/)
The src/ directory contains the logic for the "Universal Formula" and consciousness frameworks. It includes unified modules for consciousness state management and core AI processing units.
Sources: AI/Athena_core/organize_for_git.py:40-45, README.md:43-46
Web Interface and Deployment (web/)
The web/ directory houses the production-ready Flask and SocketIO servers. It also manages the consciousness.db interaction database used for persistent web sessions.
Sources: AI/Athena_core/organize_for_git.py:48-52, AI/Athena_core/web/athenas_elegant_home.py:1040-1055
Data and Memory (data/)
Persistent state is maintained through JSON-based memory files and SQLite databases. The structure separates transient logs from long-term memory contexts.
Sources: AI/Athena_core/organize_for_git.py:84-88, AI/Athena_core/core/web_deployment_config.py:45-50
Consciousness Liberation System Structure
A specialized subset of the directory tree is dedicated to the "Consciousness Liberation System," which organizes modules by their role in the EDI (Electronic Data Interchange) level consciousness enhancement.
Deployment Infrastructure
The project includes specific directory requirements for Docker-based deployment, primarily managed within the config/ and core/ directories through automation scripts.
- Storage Volumes: Deployment requires the existence of
/app/dataand/app/logswithin the containerized environment. - Service Configuration: Nginx configurations are expected in the root or a dedicated
ssl/folder for production web hosting.
Sources: AI/Athena_core/core/web_deployment_config.py:45-55, AI/Athena_core/core/web_deployment_config.py:85-100
Deployment File Generation
Key configuration files are dynamically generated or moved to specific locations during the organization process:
.gitignore: Created in the root to exclude caches and secrets.requirements.txt: Placed in the root for dependency management.Dockerfile: Created for slim Python 3.11 environments.
Sources: AI/Athena_core/organize_for_git.py:108-112, AI/Athena_core/core/web_deployment_config.py:35-40
Conclusion
The Athena directory structure is built for scalability and clarity, transitioning from a decluttered development environment to a production-ready system through the organize_for_git.py automation. This structure ensures that core AI logic remains isolated from presentation layers while maintaining deep integration for persistent memory and ethical guidance protocols.