Skip to content
Local twin / production path

Local twin on the left. Institutional delivery on the right.

Far Gradient’s architecture is designed to preserve the same conceptual structure across environments: pipeline first, temporal truth explicit, lineage visible, and delivery typed.

The local twin is optimized for proof and iteration. Production introduces network, security, and orchestration distance without changing the logic of the analytical surface.

Production architecture

Sovereign data root

A VPC-contained storage model with encrypted object persistence, immutable versioning, and graph-aware relationship context.

Amazon S3ArcticDBMemgraph / NebulaGraphClickHouse

Deterministic extraction plane

Parsing and inference services designed to preserve structural fidelity while enforcing typed outputs.

IBM DoclingTriton Inference ServerTensorRT-LLMvLLM + Outlines

Institutional delivery layer

Orchestration, distributed compute, and Arrow-native transport aligned to quant workflows and compliance review.

Dagster EnterpriseRay / KubeRayArrow Flight RPCvectorbt PRO / NautilusTrader

Local twin

Bare-metal research loop

A workstation-first twin that maximizes iteration speed, shared memory access, and experimental throughput.

Threadripper PRODual RTX 6000 AdaNVLinkUbuntu 24.04

Embedded temporal stack

The local twin preserves the same conceptual model as production while using embedded, Arrow-native components.

Dagster devArcticDB on NVMeKuzuArrow IPC

Prefix-cached inference

Local extraction and schema tasks run with cached context and deterministic sinks for fast, repeated analytical passes.

SGLangOutlinesDoclingPolars / vectorbt PRO

Temporal discipline

Two clocks, one analytical truth.

Bitemporal handling is not presented as an implementation detail. It is part of the reader-facing proof that the system does not collapse into look-ahead bias or unreplayable output.

Event time

When the fact occurred

The market event, filing date, covenant change, or contract fact that the system is representing.

Knowledge time

When the system knew it

The observed or extracted timestamp that keeps replayability and model governance honest.

Lineage posture

Cryptographic

Parser version, source hash, and asset identity stay attached to every meaningful downstream artifact.

Inference discipline

Schema constrained

The system treats structured output as a contract, not an aspiration.

Transport model

Arrow native

Typed batches are the default delivery primitive for high-trust consumers.

Operating stance

Research terminal

Public narrative and operator density share a token system without collapsing into the same UI mode.

Review path

Method explicit

Every chapter offers a route back to methods, provenance, and assumptions.

Delivery tempo

Market speed

The goal is fast movement under control, not ornamental complexity.

Delivery path

Stand up the shell now, then connect it to the governed system surface.

Discuss the deployment path