MindsHub (formerly MindsDB)

# MISSION: Scaffold "MindsHub (formerly MindsDB)" 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 **MindsHub (formerly MindsDB)**.
---
## 1. PROJECT SPECIFICATIONS & BENCHMARK
- **Reference Architecture**: MindsHub (formerly MindsDB)
- **What It Does**: MindsHub (formerly MindsDB) is an agent workspace: an Electron and React desktop and web app backed by a Python FastAPI server on SQLite and the anton agent runtime, shipped as a superproject over four git submodules.
- **Domain & Category**: Desktop & Web AI Agent Workspace
- **Production Scale**: 20+ People
- **Development Mode**: AI-AGENT
- **Architectural Rationale**: Splitting the client, API and agent into separately versioned git submodules lets each ship on its own cadence (a signed desktop app, a PyPI server package, an agent package), while one Makefile and one docker-compose.yml still bring the whole stack up together.
- **Live Website Reference**: https://mindsdb.com
- **Source Repository**: https://github.com/mindsdb/mindshub
---
## 2. PRODUCTION TECH STACK
- **Full Stack Array**: Python, TypeScript, Electron, React, Vite, Tailwind CSS, FastAPI, Uvicorn, SQLModel, Alembic, SQLite, Keycloak, Anthropic, Docker, Nginx
- **Primary Language(s)**: Makefile, Dockerfile
- **License of the reference repo**: MIT
- **Frontend**: Electron — Desktop shell for macOS and Windows; its main process starts cowork-server as a local sidecar and talks to it over HTTP on 127.0.0.1:26866.; React — The renderer SPA, identical in the desktop app and the web build (BUILD_TARGET=web).; Vite — Builds and serves the renderer (vite dev / vite build src/renderer).; Tailwind CSS — Styling for the renderer, through PostCSS.; Keycloak — Sign-in for the app through keycloak-js and @react-keycloak/web.; electron-builder — Packages the signed macOS and Windows installers built by the release workflows.
- **Backend & APIs**: Python — Language of cowork-server (the API) and anton (the agent).; FastAPI — cowork-server: projects, conversations, files, scheduling, memory and agent orchestration.; Uvicorn — Runs cowork.server:app in development and inside the api container.; uv — Syncs the module virtualenvs in development, installs cowork-server as a uv tool for the desktop app, and installs core_agent and core_api in the api image.; Anthropic — Model provider SDK used by anton, alongside the OpenAI SDK.; Typer — Command-line interface of anton, which also runs standalone in a terminal.
- **Data & persistence**: SQLite — cowork-server data store; docker-compose.yml points DATABASE_URI at a file in a named volume.; SQLModel — ORM layer of cowork-server.; Alembic — Schema migrations for the cowork-server database (alembic.ini, cowork/migrations.py).
- **Infrastructure & deploy**: Docker — docker-compose.yml builds an api image (cowork-server + anton) and a web image (the SPA).; Nginx — Serves the built SPA in the web image and proxies /v1/ requests to the api service.
- **Tooling, testing & ops**: Git submodules — Pin frontend, core_api, core_agent and data-vault to specific commits; Makefile use, pin and baseline targets manage them.; GitHub Actions — The superproject runs CodeQL and docs deployment; the cowork repo builds and uploads macOS and Windows installers.
---
## 3. KEY ARCHITECTURAL DECISIONS (audited from https://github.com/mindsdb/mindshub @ 780bbcb)
1. **The repository is a thin superproject over four git submodules**: The tree lists frontend, backend/core_api, backend/core_agent and backend/data-vault as submodule entries, declared in .gitmodules as the mindsdb/cowork, cowork-server, anton and data-vault repositories, and the Makefile use, pin and baseline targets manage them. Application source lives in those repositories at the pinned commits.
2. **The desktop app runs the API as a local sidecar**: The cowork README states that the Electron main process spawns cowork-server and talks to it over HTTP on 127.0.0.1:26866; packaged apps install cowork-server from PyPI as a uv tool, which the Makefile server target mirrors.
3. **Desktop and web clients share one backend process**: The Makefile dev and dev-web targets both run uv run --directory backend/core_api uvicorn cowork.server:app --reload, differing only in whether the frontend starts as an Electron app (npm run dev) or a browser build (BUILD_TARGET=web npm run dev:renderer).
4. **The agent runtime is a separately versioned dependency**: cowork-server depends on anton-agent (pyproject.toml, with a git tag source for mindsdb/anton), and the Makefile can install anton from a git reference with uv, so the agent in backend/core_agent updates independently of the API that hosts it.
5. **Local storage defaults to SQLite, not a client-server database**: cowork-server uses SQLModel with Alembic migrations, and docker-compose.yml sets DATABASE_URI to sqlite:////home/cowork/.cowork/cowork.db inside a named cowork-data volume, so the default deployment needs no separate database server.
6. **The former MindsDB query engine is pinned but not run**: backend/data-vault points at mindsdb/data-vault, which contains the mindsdb Python package, the SQL parser dependency and the handler tree of the earlier MindsDB engine. The superproject pins it, but make dev, docker/api.Dockerfile and docker-compose.yml only build frontend, core_api and core_agent.
7. **The Docker Compose stack serves the web build through Nginx**: docker/web.Dockerfile builds the SPA with npm run build:web and copies it into an nginx:alpine image whose docker/nginx.conf proxies /v1/ to api:26866; compose maps host port 3000 to it and starts it only after the api service passes its /health check.
8. **Per-developer branch overrides are opt-in via an untracked file**: The Makefile reads REF, API_REF, AGENT_REF and FRONTEND_REF from an -include dev.env line, and dev.env.example documents the pattern, so contributors can point a checkout at submodule feature branches without changing shared defaults.
---
## 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**:
   - Utilize Vite 6 with TanStack Router for fully type-safe routing. Manage server state and caching via TanStack Query v5 with optimistic UI updates.
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 (SQLite, SQLModel, Alembic): 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.