Market GraphRAG Workspace

Precise — Market Data GraphRAG Workspace

A static operations UI, API relay, and Server B GraphRAG runtime are separated to connect ingestion, retrieval, analysis, backtesting, and status checks.

31 routes78 tables12 hypertables120 tests

Snapshot

API

31 routes

Schema

78 tables

Time-Series

12 hypertables

Validation

120 tests

Counts are based on Server B routes, SQL DDL, and test-code snapshots.

System Workflow

01BrowserUsers run ingest, analyze, backtest, and status actions from the static /precise screen.

02Server CRenders the static /precise/* UI and makes same-origin API calls only.

03Server A RelayApplies exact allowlists, CSRF, request IDs, relay tokens, and selected payload encryption.

04Server BThe FastAPI GraphRAG runtime handles only /graphrag/* requests.

05Result UIJob status, analysis results, and backtest results return to the workspace.

Server C Presentation

Static Pages/precise, data, research, analyze, backtest

Browser Contractsame-origin /precise/api/* calls only

No Secretsno DB, model, or private-origin credential

Server A Relay

API Relay/precise/api/* → Server B /graphrag/*

Request Guardsame-origin, CSRF, request_id, relay token

Exact Routesreject unlisted method/path pairs

Server B Runtime & Data

FastAPI31-route private GraphRAG API surface

TimescaleDBmarket OHLCV, indicators, pattern signals

Workersingest, query, backtest, job/result

Public UI and GraphRAG runtime are not placed in the same tier.

Server B rejects requests without a relay token and request ID.

Results are returned through a job/result contract for review in the UI.

Server C owns rendering, Server A owns the relay boundary, and Server B owns the private GraphRAG runtime and market-data processing.

KPI & Evidence

System

31 FastAPI routes
Server C static UI + Server A API relay
Server B GraphRAG runtime separation

Data

78 SQL table DDL files
12 Timescale hypertables
67 SQL indexes

Validation

120 test functions
relay token, CSRF, and request ID verification
order-book query payload encryption boundary

Case Study

An Operations System for Market Data and Investment Evidence

Problem

Market data, research notes, analysis results, and backtests were scattered across screens and stores.
The public screen and internal GraphRAG runtime required a clear security boundary.

Build

Placed the static UI on Server C, the relay on Server A, and GraphRAG, DB, and workers on Server B.
Connected ingest, analyze, backtest, status, and order-book requests into one workflow.

Result

Built a review workspace from data-load status to analysis, backtests, and job/result checks.
Kept the internal runtime private by separating relay authentication and encrypted requests.

Evidence

Architecture

Based on the /precise static UI, /precise/api/* relay, and Server B /graphrag/* API boundary.

Data Model

Table, hypertable, and index counts were checked from server-b-db/timescaledb/initdb SQL DDL.

Validation

Based on tests, server-b/tests, server-b-market/tests, and server-b-pattern/tests.