Raphael v1.0

Origin

Raphael started as something different. The original concept was a studio operating system — a voice and text interface built directly into the BOSS dashboard that would let us control Aylian Studios infrastructure through conversation. Deploy services, check server health, trigger workflows, get context-aware suggestions about the ecosystem. The persona was sharp and deliberate: hyper-competent, slightly arrogant, fiercely loyal — addressing us as "Master" or "Partner." Three visual states were fully designed: a Blue Halo for idle, a spinning red/gold geometric mandala for processing, and a waveform visualizer while speaking.

It was a compelling vision. But it had a hard dependency — BOSS needed to reach a certain level of maturity before Raphael had a meaningful surface to operate on. That wasn't there yet, and waiting on it meant the project would stall indefinitely.

The Pivot

Rather than block, we redirected. Discord was already the daily hub of Aylian Studios — conversations were happening constantly, knowledge was being shared and immediately lost. That was the real problem worth solving.

The new direction: build Raphael as a self-hosted knowledge management system that captures everything discussed in Discord and transforms it into a structured, searchable wiki. A digital memory that writes itself. The persona shifted too — away from the arrogant studio assistant and toward the Great Sage archetype from That Time I Got Reincarnated as a Slime: analytical, advisory, growing more capable as the knowledge base expands.

The BOSS integration and the three visual states aren't gone — they're waiting for the right surface. This first version builds the foundation those features will eventually sit on.

v1.0 — What Was Built

• Docker Compose Stack: Full multi-service stack running on RS4000 with an internal network at 172.21.0.0/16 and health checks on all containers.
• PostgreSQL 16 + pgvector: Schema initialized with 9 tables — messages, pages, page_relations, embeddings, skills, page_evolution, page_corrections, processing_logs — with vector search support baked in from day one.
• Redis 7: In-memory cache and session store with AOF persistence enabled.
• Rust Backend Scaffold: Axum 0.7 server with SQLx, Serde, and Tokio wired up and compiling clean.
• Next.js Wiki Shell: Basic frontend container running and reachable on the internal network — the bones of what becomes the wiki UI.