TradingChassis is an open-source trading infrastructure project for building small-scaled professional-adjacent Research-to-Production trading systems.

It addresses infrastructure problems that arise when building such systems: data pipelines, deterministic Event processing, versioned Configuration, reproducible Research, audit trails, structured logging, monitoring, operations, scalable orchestration, explicit architecture documentation. The goal is not to provide another trading bot or Strategy collection, but rather to approach the infrastructure discipline required to make trading consistent, explainable, maintainable, and operationally reliable.

Successful trading is not only about Strategy logic. It depends on the surrounding infrastructure: how market data is captured and promoted, how Events are ordered, how State is derived, how Configuration is versioned, how Research results are reproduced, how Live behavior is monitored, how operational failures are investigated, how trading can be audited after the fact.

A trading project may focus on an isolated part: Strategy logic, Backtesting, exchange connectivity, signal generation. This project uses some of these isolated parts, while adding its own integration to form a coherent infrastructure. It is production-like but not fully production-grade; it is a solo-maintained setup built to approximate professional standards.

Terminology note: This README follows the terminology used in the main documentation.

This diagram is intentionally high-level. It shows how infrastructure fits together to create a Research-to-Production workflow. Terms and detailed architecture are defined in the documentation.

flowchart TD
    subgraph DATA[Data]
        A[Raw Market Data] --> B[Validation & Normalization]
        B --> C[Canonical Storage]
    end

    subgraph RUNTIME[Runtime Contexts]
        F[Backtesting]
        G[Live]
    end

    subgraph CORE[Shared Core Semantics]
        I[State]
        I --> K[Strategy]
        K --> M[Risk]
        M --> N[Execution Control]
    end

    subgraph EXECUTION[Execution]
        O[Venue Adapter]
        O --> P[Venue]
    end

    subgraph OBSERVABILITY[Auditability, Analysis, Operations]
        Q[Audit Trails]
        Q --> R[Analysis]
        Q --> S[Logging & Metrics]
        S --> T[Monitoring & Operations]
        T --> U[Runbooks & Recovery]
    end

    DATA --> RUNTIME
    RUNTIME --> CORE
    CORE --> EXECUTION
    CORE --> OBSERVABILITY

TradingChassis is structured as a set of related infrastructure repositories rather than a single monolithic application:

A repository may contain local documentation focused on understanding the respective codebase, implementation structure, and development context. The main documentation remains the authoritative source for canonical semantics, architecture, Stack definitions, Operations, and project evolution. It covers:

Concept documents define semantics. Stack documents explain how those semantics are realized. Operations documents explain how the infrastructure is used, maintained, monitored, and recovered.

TradingChassis is organized around the following infrastructure concerns and working principles:

TradingChassis is under active development.

Before expanding to any higher-level workflows, the focus is on stabilizing the architectural foundation, canonical concepts, Runtime semantics, documentation structure, infrastructure boundaries, and operational model.

The roadmap gives the clearest view of where TradingChassis is heading.

Contributions, feedback, and technical discussion are welcome, especially around trading infrastructure, deterministic systems, market data, Research-to-Production workflows, observability, reproducibility, and operations.

See CONTRIBUTING.md for guidance.

For project inquiries, use the relevant repository discussions or issues.