> 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/2.-vision-and-goals/2.2-goals.md). # 2.2 Goals maicrotrader aims to: Establish the Strategy Builder as the definitive configuration and deployment tool for multi-agent trading vaults, making institutional-grade strategy infrastructure accessible without requiring a quant team, a prime broker, or a trusted intermediary. Build the Permissionless Vault Network as the first strategy marketplace where every published vault carries a mandatory live seasoning record and an on-chain track history, so depositors can evaluate real performance before allocating capital. Launch ATA-based on-chain wealth management, giving depositors a single interface to hold a dynamically optimized portfolio of strategies, with full attribution across all positions. Set a new standard for auditability in on-chain trading: every trade traceable to its originating signal, every deployment policy-hashed on-chain, every strategy's track record immutable and publicly verifiable. --- # 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/2.-vision-and-goals/2.2-goals.md?ask=&goal= ``` `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.