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

# 3. How maicrotrader Works

## The Multi-Agent Engine (MAE)

The Multi-Agent Engine is the trading infrastructure that runs every vault on the platform. It is not a single AI model making decisions. It is a structured system of four specialist agents, each with a defined role and scope, coordinated by a Master Agent that validates every output against the vault's deployed policy before any action reaches execution.

The architecture deliberately mirrors how a systematic hedge fund desk is organized:

| Agent           | TradFi Counterpart                 | Role                                                                                                         |
| --------------- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| Master Agent    | Chief Investment Officer           | Orchestrates the full workflow, validates consistency, enforces policy compliance                            |
| Quant Agent     | Research Desk                      | Signal generation via technical indicators, funding rates, volatility, on-chain liquidity, and ML adaptation |
| Portfolio Agent | Portfolio Manager                  | Asset selection, diversification, rebalancing, cash buffer management                                        |
| Risk Agent      | Risk Officer (with veto authority) | VaR enforcement, drawdown circuit breakers, stress testing, position sizing, hedging                         |
| Execution Agent | Trading Desk                       | Order routing, slippage optimization, timing, TWAP for large positions                                       |

Every agent action is logged, timestamped, and tagged to the signal or condition that triggered it. This event log is what makes full decision attribution possible: every trade in the platform's history can be traced back to the specific agent, signal, and risk check that produced it.

The Risk Agent holds structural veto authority. No trade reaches the Execution Agent without passing a risk check. This is not a soft alert. It is an architectural constraint.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.maicrotrader.com/3.-how-maicrotrader-works.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.