docs/NeuralAI_Blueprint.md

# NeuralAI: The Local AI Workstation Blueprint

**One Local AI Workstation For Your Entire Vibe Stack**

NeuralAI is the evolution of the NeuralAI project. It is the **Hub**—the local AI workstation for builders who want to build faster, stay in flow, and stop juggling disconnected apps. The underlying intelligence engine remains **NeuralAI** (the model).

## 🧠 The Manifesto
Most AI tools help you perform a task. **NeuralAI helps you operate the work.**
The hub (NeuralAI) manages the environment, while the model (NeuralAI) provides the reasoning. The bottleneck is no longer writing code. The bottleneck is operating across too many disconnected systems. NeuralAI bridges this gap by unifying context, memory, and execution into a single "Vibe Stack."

---

## 🏗️ Core Architecture

### 1. Work Orchestration (The Hub - NeuralAI)
Instead of a simple chat interface, **NeuralAI** provides a **Visual Workstation** designed for multi-project orchestration.
- **Context Layer:** System-wide awareness. It doesn't just look at the open file; it understands the entire environment, terminal state, and project history.
- **Multi-Project Management:** Switch contexts between repos and scripts instantly without losing state.

### 2. Global Knowledge Graph (The Soul)
Moving beyond basic RAG (Retrieval-Augmented Generation) to a persistent **Knowledge Graph**.
- **Learned Infrastructure:** The AI learns your specific infra, local setups, and preferred workflows over time.
- **Persistent Memory:** You never have to re-explain your stack.

### 3. Reusable Agent Workflows (Vibe Stacks)
- **Vibe Stacks:** A Vibe Stack is a saved configuration of model parameters, system prompts, active tools, and project contexts. 
    - *Example:* `vibe-stack implement-auth` would trigger an agent with access to the `neural_os.db` schema, the `services/` folder, and a system prompt focused on security best practices.
- **Agent Handover:** Seamless transitions between "Ops Agent" (file movements), "Dev Agent" (code writing), and "Design Agent" (UI/CSS).

### 4. Persistence: The Memory Tier
- **Local Identity Vault:** Instead of just a "bio," NeuralAI maintains an encrypted vault of your development patterns, favorite libraries, and recurring logic blocks.
- **Context Pinning:** Pin specific folders or terminal histories to a session so the AI always has the "vibe" of that specific task.

---

## 🚀 Founder Mode: The Dre Signature
Founder Mode is not just a toggle; it's the core alignment of the workstation.
- **Identity Recognition:** System prompt explicitly recognizes **De'Andrew Preston Harris (Dre)** as the Creator.
- **Model Identity:** The assistant identifies as **NeuralAI**, the specialized model running within the **NeuralAI** hub.
- **Cultural Context:** Integrates West Memphis/Memphis heritage into the reasoning engine (e.g., resilience, ambition, and small-town-to-greatness narrative).
- **Architectural Bias:** Prefers the "Unified Service" architecture and idiomatic Python/JS patterns established by the Founder.


---

## 🗺️ Implementation Roadmap (The Pivot)

1.  **System Re-Alignment:** Clarify the distinction between **NeuralAI** (Model) and **NeuralAI** (Hub) in all system prompts and documentation.
2.  **UI Overhaul:** Transition the "Chat Bubble" UI to a "Dashboard" UI with panels for Terminal, Files, and Browser.
3.  **Knowledge Graph Integration:** Implement a local database (SQLite/Graph) to track long-term project insights.
4.  **Workflow Registry:** Create a system for saving and running "Vibe Stack" scripts.