> 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/5.-the-strategy-builder/5.2-live-vault-dashboard.md).

# 5.2 Live Vault Dashboard

The dashboard is where a deployed STA is monitored. The design philosophy is a **trading floor desk view**, not a crypto portfolio tracker.

**Living org chart**, the central visual element. Four agent nodes displayed in the coordination structure, each showing: current state (Running / Watching / Standby), last action with timestamp, and individual PnL contribution.

**PnL attribution bar**, which splits total vault returns, by agent contribution:

* Quant Agent: signal-driven alpha contribution
* Portfolio Agent: rebalancing value
* Risk Agent: avoided drawdown value (the losses prevented are the contribution)
* Execution Agent: slippage savings versus market order baseline

This is how a multi-strategy fund reports to LPs. It is the only surface in on-chain trading that attributes returns to specific decisions rather than showing a single net number.

**Decision attribution feed**, a chronological log of every agent action, formatted as:

*"Execution Agent filled ETH long 0.42 ETH, limit order, 0.09% slippage, funding window avoided. Risk Agent approved (VaR post-trade 3.2%, within policy limit). Outcome: +$18.40"*

Every trade has an entry. Every entry shows which agent acted, what data triggered it, what the risk check produced, and the post-hoc P\&L result.


---

# 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.maicrotrader.com/5.-the-strategy-builder/5.2-live-vault-dashboard.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.