SurrealDB

# MISSION: Scaffold "SurrealDB" Production Architecture
You are an expert Senior Staff Software Architect and Full-Stack Engineer. Your mission is to scaffold and implement a production-grade, highly reliable, and modular codebase following the proven architecture of **SurrealDB**.
---
## 1. PROJECT SPECIFICATIONS & BENCHMARK
- **Reference Architecture**: SurrealDB
- **What It Does**: Multi-model document and graph database written in Rust with pluggable storage engines, live queries, and native vector search.
- **Domain & Category**: Multi-Model Real-Time Database
- **Production Scale**: 20+ People
- **Development Mode**: CLASSIC
- **Architectural Rationale**: SurrealDB puts document, graph, relational and vector models behind one SurrealQL engine in a single Rust binary that runs embedded, in the browser via WebAssembly, or as a server over pluggable storage (RocksDB, SurrealKV, TiKV), with WebSocket live queries and row-level permissions built into the core.
- **Live Website Reference**: https://surrealdb.com
- **Source Repository**: https://github.com/surrealdb/surrealdb
---
## 2. PRODUCTION TECH STACK
- **Full Stack Array**: Rust, RocksDB, WebAssembly, Tokio, Docker, OpenTelemetry
- **Primary Language(s)**: Rust, SurrealQL, Python, Shell, Nix
- **License of the reference repo**: NOASSERTION
- **Backend & APIs**: Rust — Core database engine, query parser, execution planner, and network server; Tokio — Asynchronous runtime handling concurrent network IO and storage operations; WebAssembly — Plugin execution sandbox using Wasmtime and WIT bindings
- **Data & persistence**: RocksDB — Embedded persistent key-value storage engine implementation
- **Infrastructure & deploy**: Docker — Multi-stage container packaging for dev and minimal production images; OpenTelemetry — Distributed tracing, metric collection, and OTLP export pipeline
---
## 3. KEY ARCHITECTURAL DECISIONS (audited from https://github.com/surrealdb/surrealdb @ 18971ff)
1. **Modular Key-Value Abstraction Layer**: Decouples the document-graph query engine from storage backends, supporting SurrealKV, RocksDB, and TiKV through unified traits.
2. **WebAssembly Extensibility Engine via Surrealism**: Uses Wasmtime and component models to execute sandboxed user-defined functions safely within query transactions.
3. **Built-in Model Context Protocol Server**: Native rmcp implementation enables direct AI agent querying and structured schema discovery without external middleware.
4. **Vector Search with Native DiskANN and HNSW**: Integrates high-performance vector indexing directly into the storage core for native retrieval-augmented generation.
---
## 4. NON-NEGOTIABLE ARCHITECTURAL GUARDRAILS
1. **Monorepo & Modular Separation**:
   - Structure as a Turborepo monorepo with strict package boundaries:
     - `apps/web`: Application UI, routing, layouts, and server endpoints.
     - `packages/ui`: Shared design tokens, CSS variables, and Radix UI primitive components.
     - `packages/db`: Database schemas, client singleton, declarative migrations, and seed scripts.
     - `packages/config`: Shared TypeScript, ESLint, and build configurations.
2. **Strict Type Safety & Zero `any` Policy**:
   - Enable `strict: true`, `noImplicitAny: true`, and `strictNullChecks: true`.
   - Validate ALL external inputs, API request bodies, and query parameters with **Zod** schemas before execution.
3. **Frontend & Rendering Guidelines**:
   - Isolate interactive UI state to leaf components. Keep core pages lightweight and performant.
4. **Design System & Aesthetics**:
   - Keep every color, radius, shadow and font in a single token file (CSS variables) and consume tokens everywhere; never hardcode hex values in components.
   - Prefer crisp 1px borders and one subtle shadow scale over blurry default shadows. Pair one sans-serif for body/headings with one monospace for tags, badges, metrics, and code.
5. **Data Layer & Reliability**:
   - Write declarative schema definitions with foreign keys, composite indexes on queried filters, and automated timestamp triggers.
   - Use connection pooling and prepared statements for serverless database execution.
---
## 5. STEP-BY-STEP SCAFFOLDING ROADMAP
- **Phase 1: Workspace & Root Config**: Initialize package manager, monorepo configuration (`turbo.json`, `tsconfig.base.json`, `package.json`).
- **Phase 2: Database Schema & Client**: Set up the data layer (RocksDB): client, connection pool, models, and migration scripts.
- **Phase 3: Design Tokens & UI Primitives**: Build accessible `Button`, `Input`, `Card`, `Badge`, and layout wrappers inside `packages/ui`.
- **Phase 4: Core Application Routes & Handlers**: Implement primary authentication, user session handling, and application routes.
- **Phase 5: Quality Assurance & Build Verification**: Run `tsc --noEmit`, ESLint, Prettier, and smoke test suites to ensure zero compilation or runtime errors.
---
## 6. EXECUTION INSTRUCTIONS
1. Review all specifications, architectural guardrails, and stack choices above.
2. Present the full monorepo directory tree structure.
3. Systematically generate the complete, production-ready codebase according to the 5-phase roadmap above — starting with the root workspace setup, followed by the database schema, UI design system package, and full-stack application routes until the repository is fully scaffolded and ready to run.