OpenBB

# MISSION: Scaffold "OpenBB" 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 **OpenBB**.
---
## 1. PROJECT SPECIFICATIONS & BENCHMARK
- **Reference Architecture**: OpenBB
- **What It Does**: OpenBB (Open Data Platform) is an open-source Python toolkit that connects financial, economic, and alternative data sources behind one interface, usable from Python, a CLI, a REST API, MCP, or a Tauri desktop app.
- **Domain & Category**: Financial Data Platform
- **Production Scale**: 6-20 people
- **Development Mode**: HYBRID
- **Architectural Rationale**: A Poetry-managed core package with router-based provider extensions keeps roughly thirty data sources independently versioned, while the CLI, FastAPI/Uvicorn REST server, MCP server, and Tauri desktop app all wrap that same core library instead of reimplementing it.
- **Live Website Reference**: https://openbb.co
- **Source Repository**: https://github.com/OpenBB-finance/OpenBB
---
## 2. PRODUCTION TECH STACK
- **Full Stack Array**: Python, FastAPI, Pydantic, Poetry, React, TypeScript, Vite, Tauri, Rust, Tailwind CSS, Pandas
- **Primary Language(s)**: Python
- **License of the reference repo**: NOASSERTION
- **Frontend**: React — Renders the Tauri desktop app UI.; TypeScript — Language for the desktop renderer, type-checked with tsc before Vite build.; Vite — Bundles the desktop app renderer (npm run build runs tsc && vite build).; Tailwind CSS — Utility CSS for the desktop app, configured alongside PostCSS and autoprefixer.
- **Backend & APIs**: Python — Only language reported for the repository; hosts the core openbb package and every provider extension.; FastAPI — openbb-core depends on a pinned FastAPI version, exposed as a REST server via the openbb-api command.; Pydantic — openbb-core depends on Pydantic 2 for the data models returned by every provider extension.; Uvicorn — ASGI server that openbb-core depends on to run the FastAPI app started by openbb-api.; Poetry — Every package in the workspace (core, cli, cookiecutter, each extension) is a separate Poetry project.; Pandas — openbb-core depends on pandas directly; provider results convert to DataFrames via obb output.to_dataframe().
- **Infrastructure & deploy**: Tauri — Wraps the React renderer and a Rust backend into cross-platform desktop binaries.; Rust — desktop/src-tauri manages the local backend process, updater, and OS integration for the desktop app.; GitHub Actions — Per-platform workflows (build-desktop-osx64/osxARM/win64.yml, release-desktop.yml) build and release the desktop app.
- **Tooling, testing & ops**: Model Context Protocol — openbb-mcp-server is an optional extra of the openbb package, exposing the platform to MCP-based AI agents.
---
## 3. KEY ARCHITECTURAL DECISIONS (audited from https://github.com/OpenBB-finance/OpenBB @ 3e071fc)
1. **A single core package plus ~30 separately versioned extensions**: openbb_platform/pyproject.toml lists the openbb-core dependency alongside about twenty required provider extensions (openbb-fmp, openbb-sec, openbb-fred, openbb-yfinance, and similar) and roughly a dozen more behind optional extras such as alpha_vantage, cboe, and tmx, so each data source ships and versions independently under one umbrella package.
2. **The CLI is a thin wrapper around the same library, not a fork**: cli/pyproject.toml depends on openbb = { version = "^4.7.2", extras = ["all"] } and adds only CLI-specific packages (prompt-toolkit, rich, pywry), so openbb-cli always tracks the installed openbb library instead of duplicating provider logic.
3. **REST access is opt-in via a bundled FastAPI/Uvicorn server**: openbb-core depends on fastapi and uvicorn directly (openbb_platform/core/pyproject.toml), and the README documents running `openbb-api` to start that server on 127.0.0.1:6900 for the OpenBB Workspace UI to connect to, rather than the library requiring a server to function.
4. **The desktop app is a Tauri shell managing a local Python process, not a reimplementation**: desktop/src-tauri/Cargo.toml depends on tokio, reqwest, and tokio-tungstenite for process and websocket management around a locally running backend, while desktop/package.json is a plain React + Vite renderer that talks to it through @tauri-apps/plugin-* packages.
5. **AI-agent access is a separate optional package, not baked into core**: openbb-mcp-server is listed as an optional extra (mcp_server = ["openbb-mcp-server"]) in openbb_platform/pyproject.toml, matching the examples/openbbPlatformAsLLMTools.ipynb notebook that shows the platform being consumed as LLM tools.
---
## 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: 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.