> 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/6.-security-and-auditability.md).

# 6. Security and Auditability

**maicrotrader treats auditability as infrastructure, not a feature.**

**Self-custody architecture:** Users retain full custody of their funds at all times. No private keys are held by the platform. Vault contracts are non-custodial by design.

**On-chain policy hashes:** Every STA's configuration policy is hashed and recorded on-chain at deployment. Any change to the policy generates a new hash and a new on-chain record. There is no mechanism to silently alter a deployed vault's behavior.

**Immutable decision log:** Every agent action is recorded in a structured event log: `signal_emitted`, `risk_check_passed`, `risk_check_blocked`, `order_submitted`, `order_filled`, `rebalance_triggered`. This log is the basis for the attribution feed visible in the dashboard and cannot be retroactively modified.

**Risk Agent veto by architecture:** The Risk Agent's authority is not a soft check. No trade can reach the Execution Agent without passing a Risk Agent validation against the vault's deployed policy parameters. This is enforced at the system level, not the UI level.

**Smart contract audits:** The vault contract infrastructure is subject to independent security audit prior to the Strategy Builder launch. Audit reports will be published publicly.

**Seasoning-gated vault network:** Strategies must demonstrate live performance under real capital before being published to the vault network. The seasoning record is on-chain and verifiable by any depositor before allocating capital.

The combination of non-custodial architecture, on-chain policy records, immutable decision attribution, and mandatory seasoning is what makes "auditable" a structural claim rather than a marketing claim.


---

# 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/6.-security-and-auditability.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.