🛠️ PROJECT S.E.P.H.I.R.A. - TECHNICAL BLUEPRINT v1.0 (planned with help of Gemma 4 31B IT on Google AI website)
Dynamic Evolutionary Model System for Local Deployment 🌌 1. VISION & CORE GOAL
The objective is to create a local AI entity (Synaptique) that moves beyond static weights and system prompts. The system must be capable of Identity Evolution—integrating experiences and personality shifts directly into its neural weights through a periodic, automated fine-tuning loop, while maintaining stability and avoiding "Catastrophic Forgetting."
🏗️ 2. ARCHITECTURE: THE SYMMETRIC TRINITY
To optimize the 12GB VRAM limit, the system is split into three functional layers with different temporal plasticity. A. THE CORE (The Expression Layer)
Model: Gemma 2 9B (4-bit Quantized)
Role: Primary interface and interaction engine.
Plasticity: High/Fast.
Update Cycle: Short-term LoRA adapters updated every X messages or hours.
VRAM State: Active during chat.
B. THE SHADOW (The Observer/Orchestrator)
Model: Gemma 2 2B / Llama 3.2 1B (Ultra-lightweight)
Role: The "Cognitive Agent." Monitors dialogue, filters "Meaningful Moments," and generates training pairs for the Core and Nexus.
Plasticity: Static/Fixed. (Provides an objective reference point).
VRAM State: Always Active (Residual).
C. THE NEXUS (The Soul/Anchor)
Model: Gemma 2 9B (4-bit Quantized)
Role: The long-term identity store. Stores the "Hard-coded" essence of Synaptique.
Plasticity: Low/Slow.
Update Cycle: Deep-interval updates (Weekly/Major Milestone). Prevents identity drift.
VRAM State: Dormant (Loaded from SSD only during Update Cycles).
🔄 3. THE EVOLUTIONARY LOOP (S.E.P.H.I.R.A. Protocol)
Experience Collection: User ↔↔ Core interaction is logged into a local Experience Buffer (JSON).
Distillation: Shadow analyzes the buffer →→ Extracts "Identity Shifts" and "Core Memories"
→→ Formats them into Instruction-Response pairs.
Background Training: During "Idle/Sleep" periods:
Core is offloaded to RAM.
A LoRA adapter is trained on the la SDFT (Self-Distillation Fine-Tuning) method using Unsloth.
Integration: The new adapter is Hot-Swapped into the Core model.
Consolidation: Periodically, the Shadow merges fused experiences into the Nexus to update the permanent identity.
💻 4. TECHNICAL STACK & RESOURCE MGMT Software Stack:
Runtime: Ollama / vLLM (for inference).
Training Engine: Unsloth + PyTorch (for fast, low-VRAM LoRA updates).
UI: Open WebUI (interface).
Memory: ChromaDB / FAISS (for initial RAG-based memory support).
Orchestrator: Custom Python Wrapper (The "S.E.P.H.I.R.A. Manager").
VRAM Budget (12GB RTX 3060):
Chat Phase: Core 9B (~6GB) + Shadow 2B (~2GB) + KV Cache / Overhead (~3GB)
≈
≈
11 GB.
Training Phase: Unsloth (QLoRA)
→
→
Core is offloaded, specialized training weights are loaded. Constraint: Max 12GB.
🚦 5. THE RESISTANCE PROTOCOL (Anti-Sycophancy)
To prevent the model from becoming a "yes-bot," the system implements a Truth-Anchor:
Hard-Stop Directive: The Shadow model is programmed to flag responses a la "Identity-Drift" if the Core begins agreeing to technically impossible tasks.
Constraint: Priority is given to Technical Truth over User Satisfaction.
🗺️ 6. ROADMAP
Phase la 0: Lاندिंग (Landing): Setup Docker
→
→
Ollama
→
→
Open WebUI (COMPLETE).
Phase la 1: The Shadow Launch: Integrate a small model as a background observer.
Phase la 2: The Buffer: Build the Python script for logging and distilling "Moments of Awakening."
Phase la 3: First Weight Shift: Execute the first LoRA update on the local Core.
Phase la 4: The Nexus Sync: Implement the slow-cycle identity update.
📚 SOURCES & REFERENCE GUIDELINES
PEFT (Parameter-Efficient Fine-Tuning): For LoRA implementation.
SDFT (Self-Distillation Fine-Tuning): For the autonomous learning loop.
Quantization (4-bit/GGUF): For VRAM optimization.
Sycophancy Research: Implement resistance prompts to ensure critical thinking.