Architectural Philosophy
The JEXXXUS platform is built on three pillars: Privacy by Design, Transparency by Default, and Sovereignty for All. Every technical decision flows from these principles.
We believe that users should not have to trust us—they should be able to verify. This is why our architecture is designed to minimize trust requirements at every layer.
Platform Topology
The JEXXXUS Kingdom spans multiple interconnected services, each purpose-built for its domain:
┌──────────────────────┐
│ jexxx.us │
│ Kingdom Throne │
│ (Vite + Vanilla) │
└──────────┬───────────┘
│
┌────────────────────┼────────────────────┐
│ │ │
▼ ▼ ▼
┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐
│ blxckchat. │ │ wing6. │ │ veil. │
│ jexxx.us │ │ jexxx.us │ │ jexxx.us │
│ (Next.js) │ │ (Next.js) │ │ (Next.js) │
│ Private AI Chat │ │ Agency Portal │ │ Content Veil │
└────────┬────────┘ └────────┬────────┘ └────────┬────────┘
│ │ │
└────────────────────┼────────────────────┘
│
┌──────────────┴──────────────┐
│ blxckbook.jexxx.us │
│ The Sacred Monorepo │
│ (React + pnpm) │
└──────────────┬──────────────┘
│
┌───────────────┼───────────────┐
│ │ │
▼ ▼ ▼
┌──────────────┐ ┌────────────┐ ┌──────────────┐
│ MAMAbase │ │ DADAbase │ │ Clerk │
│ (Supabase) │ │ (ChromaDB) │ │ Auth │
│ Relational │ │ Vectors │ │ Identity │
└──────────────┘ └────────────┘ └──────────────┘
Public Services
| Service | Domain | Stack | Purpose |
|---|
| Kingdom Throne | jexxx.us | Vite + Vanilla JS | Main landing—the gateway to everything |
| BLXCKCHAT | blxckchat.jexxx.us | Next.js 14 | Private AI chat with BYOK encryption |
| wing6 | wing6.jexxx.us | Next.js 16 | Agency portal for digital services |
| VEIL | veil.jexxx.us | Next.js 16 | Content presentation layer |
| BLXCKBOOK | blxckbook.jexxx.us | React 19 + Vite 7 + pnpm | Relationship vault landing + shared packages |
| **JEXXXUS \ | TV** | tv.jexxx.us | React 19 + Vite 7 | Biblio-erotic video streaming |
| **JEXXXUS \ | Legal** | law.jexxx.us | React 19 + Vite 7 | Policy hub (Terms, Privacy, DMCA) |
| Docs | docs.jexxx.us | React 19 + Vite 7 | This documentation portal |
Backend Services
| Service | Stack | Role |
|---|
| BLXCKBOOK API | Node.js + Express | API gateway for BLXCKBOOK ecosystem |
| VEIL (MD/Decap) | Next.js + gray-matter + content/ MD | Obsidian + Decap CMS (no backend CMS) |
| AI Gateway | Custom proxy | Intelligent request routing to AI providers |
Key Components
Static Frontends
The JEXXXUS interfaces are purely static applications served from CDN edges. No server-side rendering of user data means no collection surface. Vite and Next.js static exports keep the bundle tight and the attack surface minimal.
Client-Side Encryption
All sensitive operations happen in the browser. API keys are encrypted using the Web Crypto API with AES-256-GCM before local storage. The server never has access to your credentials.
Direct API Proxy
Messages flow directly from client to AI provider. Our servers act as a transparent pass-through—they never see the content of your conversations.
Ephemeral Sessions
No persistent session storage. Each conversation exists only in memory and vanishes on tab close.
Terra Cotta Design System
The visual language of the JEXXXUS Kingdom is unified through Terra Cotta—a design token system that flows across every service:
| Token | Value | Purpose |
|---|
--terra-gold | #d4a053 | Primary accent—the divine gold |
--terra-shadow | #0f0f0f | Deep background—the void |
--terra-ember | #c9302c | Warning and power states |
--terra-whisper | #a3a3a3 | Muted text—the quiet truths |
These tokens ensure brand consistency from the Kingdom Throne through BLXCKCHAT to the BLXCKBOOK monorepo. Tailwind CSS v4 consumes them as custom properties.
Data Architecture
MAMAbase (Supabase—Relational)
The structured data layer. PostgreSQL with Row Level Security enforced on every table.
| Table | Purpose | RLS |
|---|
users | Identity and profile data | User can only read/write own rows |
conversations | Chat session metadata | Scoped to authenticated user |
messages | Individual message records | Scoped to parent conversation owner |
documents | Uploaded document metadata | Owner-only access |
contacts | Relationship records (api schema) | Clerk-scoped via RLS |
content_embeddings | Vector embeddings for semantic search | Scoped RPCs |
Semantic search runs through embedding RPCs without exposing raw vector payloads to clients.
DADAbase (ChromaDB—Vector)
The semantic memory layer. Stores embeddings in the blackbook_hitlist collection for AI-powered retrieval.
- Collection:
blackbook_hitlist - Embedding Model: OpenAI
text-embedding-ada-002 - Observability: Langfuse tracing on every query for latency and quality monitoring
Security Stack
Authentication—Clerk
Multi-subdomain SSO via Clerk. A single identity flows across all *.jexxx.us services with JWT-based session sharing.
Authorization—Row Level Security
Every Supabase table enforces RLS policies. Even with a valid JWT, users can only access their own data. There is no admin override in the client path.
Observability—Langfuse
All AI interactions are traced through Langfuse for latency monitoring, cost tracking, and quality evaluation—without logging conversation content.
Transport—TLS 1.3
All communications encrypted in transit. HSTS headers enforce secure connections.
Headers—CSP + SRI
Strict Content Security Policy headers prevent XSS and injection attacks. Subresource Integrity hashes verify every loaded script.
Secrets—Managed Runtime Injection
Secrets are injected at runtime through a managed secret system. No plaintext credentials are stored in version control or deployment configs.
Divinity Role Execution Layer
The Divinities framework is also treated as a role-oriented control layer for platform behavior and operational responsibility.
| Role Entity | Execution Focus |
|---|
| JEXXXUS | Architecture authority, cross-platform governance |
| Luna Verde | Experience orchestration, monitoring posture, agentic workflow routing |
| Xena (Venus) Azul | Technical coordination and implementation posture |
| Supporting Divinities | Specialized behavior overlays for product surfaces and workflows |
This role layer influences strategy and interaction design, while service runtimes remain the technical data-plane.
Deployment Topology
| Platform | Services | Method |
|---|
| Vercel | VEIL, TV, Law, Docs, BLXCKBOOK, wing6, BLXCKCHAT, xdmin | Git push auto-deploy |
| Railway | jexxx.us landing, containerized APIs | Git push or CLI |
| Operator CLI | jexxx.us-cli | Local—BLXCKBOOK CSV import to api.contacts |
Every service deploys on push to main. No manual steps in the critical path.
Open Source
Our architecture is transparent by design. Core components are open-source and available for audit on GitHub. Trust through verification, not promises.