> 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/11.-glossary.md).

# 11. Glossary

**ATA (Allocation Trading Agent):** The cross-STA capital optimization layer. An ATA dynamically manages a depositor's capital across multiple published STAs based on live performance and user-defined risk parameters. The on-chain wealth management surface for depositors who do not want to configure individual strategies.

**Backtest Gate:** The mandatory pre-deployment simulation step in the Strategy Builder. Every STA must pass a historical performance simulation before deployment is permitted. Results show cumulative return, Sharpe ratio, maximum drawdown, regime breakdown, and estimated fee and funding rate drag.

**Creator Bonding:** The mechanism by which strategy creators stake $MAICRO as a slashable bond to publish an STA to the Permissionless Vault Network. The bond is subject to slashing if the strategy is found to have been misrepresented.

**DeFAI:** Decentralized Finance AI. The category describing AI-native protocols that operate autonomously on-chain, distinct from AI tools that assist human traders.

**Execution Agent:** The MAE sub-agent responsible for order routing, slippage optimization, timing decisions, and trade execution on-chain.

**MAE (Multi-Agent Engine):** The trading infrastructure beneath every vault on the platform. Comprises four specialist agents (Quant, Portfolio, Risk, Execution) coordinated by a Master Agent.

**Master Agent:** The orchestrating agent in the MAE. Validates consistency across sub-agent outputs, enforces policy compliance, and manages workflow sequencing.

**Permissionless Vault Network:** The strategy marketplace where published STAs are available for third-party deposits. Entry requires completion of the seasoning period. All track records are on-chain and verifiable.

**Policy DSL:** Mode C of the Strategy Builder. A constrained, structured scripting language for expressing agent hand-off conditions and composite signal logic that widget forms cannot capture. Token-gated at the Power staking tier.

**Policy Hash:** A cryptographic hash of an STA's deployed configuration, recorded on-chain at deployment. Any configuration change produces a new hash and a new on-chain record.

**Portfolio Agent:** The MAE sub-agent responsible for asset selection, position sizing, diversification, rebalancing, and cash buffer management.

**Quant Agent:** The MAE sub-agent responsible for signal generation via technical indicators, funding rates, volatility analysis, on-chain liquidity data, and ML-driven adaptation.

**Risk Agent:** The MAE sub-agent responsible for VaR enforcement, drawdown circuit breakers, stress testing, and position-level risk controls. Holds structural veto authority over every trade before it reaches the Execution Agent.

**Seasoning:** The mandatory live operation period an STA must complete before it can be published to the Permissionless Vault Network. Requires real capital deployment over a minimum number of days.

**STA (Strategy Trading Agent):** A deployed trading vault running on the MAE. Each STA has its own configuration policy, on-chain policy hash, capital, and immutable track record.

**Strategy Builder:** The core product surface for configuring, backtesting, and deploying STAs. Offers three depth modes: Mode A (templates), Mode B (guided widget form), Mode C (Policy DSL, V1.1+).


---

# 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/11.-glossary.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.