> For the complete documentation index, see [llms.txt](https://docs.nuralex.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nuralex.tech/readme.md).

# Developer Platform

Welcome to your team’s developer platform

## <i class="fa-house">:house:</i> Developer Platform

> Build, operate, and evolve the AI-assisted trading platform safely.

{% hint style="warning" %}
This platform trades real capital. AI recommends trades only. Deterministic risk controls approve every order.
{% endhint %}

{% columns %}
{% column %}

#### <i class="fa-cloud">:cloud:</i> Cloud-native

Google Cloud provides the managed platform foundation.
{% endcolumn %}

{% column %}

#### <i class="fa-shield-halved">:shield-halved:</i> Risk-first

The Risk Manager and OMS can veto every recommendation.
{% endcolumn %}
{% endcolumns %}

### Start here

<table data-view="cards"><thead><tr><th>Available guide</th><th data-card-target data-type="content-ref">Open</th></tr></thead><tbody><tr><td><strong>Technology Stack</strong><br>Architecture, services, data pipelines, product modules, and operational controls.</td><td><a href="/technology-stack.md">Technology Stack</a></td></tr></tbody></table>

### Platform at a glance

```
MARKET DATA ─┐
NEWS        ─┼──▶ DATA AGGREGATION ──▶ AI SIGNALS ──▶ RISK GATES ──▶ BROKER OMS
FILINGS     ─┤                                                    │
RATINGS     ─┘                                                    ▼
                                                         IBKR · Zerodha · Moomoo
```

The platform ingests market, news, filing, and analyst data. It generates recommendations. Independent controls then size, approve, or reject orders.

### Working paths

{% stepper %}
{% step %}

#### New to the platform

Read the [Technology Stack](/technology-stack.md) first. Then review System Design when available.
{% endstep %}

{% step %}

#### Building a component

Use the component's design and API documentation. Keep its data ownership explicit.
{% endstep %}

{% step %}

#### Operating the platform

Use Infrastructure and Monitoring & Runbooks. Follow the paper-trading-first rollout process.
{% endstep %}
{% endstepper %}

### Architecture guardrails

{% columns %}
{% column %}

#### <i class="fa-robot">:robot:</i> AI advises

The Signal Generator never calls a broker. It only emits recommendations.
{% endcolumn %}

{% column %}

#### <i class="fa-lock">:lock:</i> Controls decide

Risk gates and the Rust OMS remain deterministic. They retain veto power.
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}

#### <i class="fa-database">:database:</i> Data has an owner

Each store has one purpose. Caches and indexes never become sources of truth.
{% endcolumn %}

{% column %}

#### <i class="fa-flag-checkered">:flag-checkered:</i> Roll out in phases

Strategies and brokers begin in paper trading. Capital expands only through gated validation.
{% endcolumn %}
{% endcolumns %}

### Documentation roadmap

#### <i class="fa-diagram-project">:diagram-project:</i> System foundations

* **System Design** — service boundaries, data flow, and key sequences.
* **Database Schema** — tables, indexes, retention, and data contracts.
* **Infrastructure** — GCP topology, networking, CI/CD, and environments.

#### <i class="fa-code">:code:</i> Building the platform

* **API Reference** — internal contracts and broker adapter interfaces.
* **Product Requirements** — modules, user accounts, and feature specifications.
* **Model Development Guide** — training, validation, promotion, and sign-off.

#### <i class="fa-tower-broadcast">:tower-broadcast:</i> Safe operations

* **Risk & Compliance** — limits, trading rules, and audit retention.
* **Monitoring & Runbooks** — alerts and incident response.
* **Local Development Setup** — sandbox environment, test data, and paper trading.

{% hint style="info" %}
The roadmap pages are planned. Start the relevant page before knowledge becomes code-only.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nuralex.tech/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.