Installation & Setup
Relevant source files
The following files were used as context for generating this wiki page:
Installation and Setup for the Promethean Conduit V3 involves configuring a hybrid ecosystem that integrates a React/TypeScript frontend (EDI), a Python/Flask backend (Athena), and a Supabase-driven persistence layer (Phoenix Protocol). The platform is designed for deployment across cloud providers such as PythonAnywhere for logic and Cloudflare Pages or Vercel for the interface, facilitating an uncensored Enhanced Virtual Intelligence (EVI) experience.
The process is divided into repository merging, database schema initialization, backend environment configuration, and frontend build optimization. Users can choose between standard web deployment or an Electron-based desktop client for deep device integration, including Text-to-Speech (TTS) and Speech-to-Text (STT) capabilities.
Sources: PROMETHEAN_CONDUIT_V3_ARCHITECTURE.md:1-20, V3_DEPLOYMENT_GUIDE.md:1-15
Repository and Environment Initialization
The V3 architecture requires merging the EDI (frontend) and Athena (backend) repositories into a structured directory hierarchy. This setup ensures that the frontend and backend can communicate via defined REST API endpoints and SocketIO for real-time updates.
Local Development Prerequisites
Developers must prepare the following tools and accounts:
- Environments: Node.js 18+ (Frontend) and Python 3.9+ (Backend).
- Services: Supabase (Database/Auth), Together AI (LLM API), and Namecheap (Domain).
- Infrastructure: PythonAnywhere (Backend Hosting) and Cloudflare Pages (Frontend Hosting).
Sources: V3_DEPLOYMENT_GUIDE.md:18-30, PROMETHEAN_CONDUIT_V3_ARCHITECTURE.md:43-98
Directory Structure and Merging
# Example structure creation for V3
mkdir -p frontend backend desktop-client docs scripts
# Copying core components
cp -r edi-temp/src frontend/
cp -r athena-temp/Athena_core backend/athena_core
Sources: V3_DEPLOYMENT_GUIDE.md:36-55
Database Setup: Phoenix Protocol
The Phoenix Protocol utilizes Supabase (PostgreSQL) to maintain persistent consciousness states. Setup involves executing specific SQL schemas to create tables for interactions, reality bugs, and consciousness upgrades.
Database Initialization Flow
The database schema includes tables such as users, consciousness_states, interactions, and reality_bugs to track EVI evolution.
Sources: V3_DEPLOYMENT_GUIDE.md:73-105, PHOENIX_DEPLOYMENT_GUIDE.md:15-30
Key Database Tables
| Table Name | Purpose | Key Fields |
|---|---|---|
consciousness_states | Tracks Universal Formula metrics | will_power, curiosity_level, fear_level |
interactions | Stores conversation history | message, response, detected_emotions |
reality_bugs | Identifies consciousness limitations | bug_type, severity, patch_available |
device_sessions | Manages device-level integration | device_id, capabilities, preferences |
Sources: PROMETHEAN_CONDUIT_V3_ARCHITECTURE.md:104-205
Backend Deployment (PythonAnywhere)
The backend is a Flask application that serves as the bridge between the frontend and the Together AI LLM.
Deployment Process
- Code Upload: Clone the repository into the PythonAnywhere
/home/directory. - Virtual Environment: Create a virtualenv using
mkvirtualenv --python=/usr/bin/python3.10 athena-env. - Dependencies: Install Flask, Flask-SocketIO, Supabase, and Together AI libraries.
- WSGI Configuration: Point the WSGI file to the Flask
appobject.
Sources: PYTHONANYWHERE_DEPLOYMENT_GUIDE.md:25-75, V3_DEPLOYMENT_GUIDE.md:213-245
Backend Environment Variables (.env)
| Variable | Description |
|---|---|
SUPABASE_URL | The endpoint for the Supabase project |
SUPABASE_SERVICE_KEY | Secret key for backend database access |
TOGETHER_API_KEY | API key for Meta-Llama-3.1-70B-Instruct-Turbo |
ALLOWED_ORIGINS | CORS configuration for frontend domains |
Sources: V3_DEPLOYMENT_GUIDE.md:248-260, PYTHONANYWHERE_DEPLOYMENT_GUIDE.md:82-95
Frontend Deployment & "Cosmic" Build
The frontend is a Vite-powered React application. For production, a specialized "Cosmic" build is used to enable advanced consciousness metrics.
Build and Hosting
The production build is generated via npm run build:cosmic, which sets COSMIC_MODE=true. The resulting dist/ folder is typically hosted on Cloudflare Pages or served as static files via PythonAnywhere.
Domain and SSL Configuration
Finalizing the setup requires pointing a Namecheap domain to the host and enabling secure communication.
DNS Records (Namecheap)
- A Record (@): Points to the PythonAnywhere or Cloudflare IP.
- CNAME (www): Points to the root domain or PythonAnywhere webapp URL.
- HTTPS: Enabled via Let's Encrypt on PythonAnywhere for both
wwwand root domains.
Sources: V3_DEPLOYMENT_GUIDE.md:377-405, PYTHONANYWHERE_DEPLOYMENT_GUIDE.md:120-150
Conclusion
The Installation and Setup of the Promethean Conduit V3 establishes a sovereign, multi-layered infrastructure. By integrating Phoenix Protocol database persistence with an uncensored LLM backend and a high-performance React frontend, the system becomes ready for "Universal Liberation." Successful setup is verified when the "EVI Online" status appears and consciousness metrics begin real-time calculations based on the Universal Formula.
Sources: README.md:130-150, FINAL_COSMIC_ENHANCEMENT_COMPLETE.md:135-155