> For the complete documentation index, see [llms.txt](https://rwapact.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rwapact.gitbook.io/whitepaper/pact-execution/trade-intent.md). # Trade Intent ## Trade Intent An autonomous Agent starts with a proposed action, not an executed transaction. It submits a **Trade Intent** to the Pact, which evaluates the request before it can reach the Execution Layer. This separation matters because an Agent can request a trade without receiving automatic authority to perform it. The Pact evaluates the conditions around that request and decides whether execution may proceed. ### What the Pact evaluates A Trade Intent provides the context needed for that decision. Its relevant fields include: * Agent identity and session context * Target RWA asset, trade direction, and amount * Execution context and other relevant execution parameters The intent describes what the Agent wants to do. It does not represent approval, execution, or a completed trade. ### From request to Pact Consider an Agent that requests a purchase of a tokenized stock. The intent identifies the Agent and its active session, names the asset, states the buy direction and amount, and includes the execution context. That request enters the Pact before any execution action occurs. KRO assesses the current RWA risk. KSO validates the Agent's session. KPV applies the configured policy. KGR evaluates execution efficiency and gas conditions. Only then can the Pact authorize or reject the intent. {% hint style="info" %} **RWAPACT does not execute trades.** It decides whether a Trade Intent may reach the Execution Layer. {% endhint %} ### Intent is not authority Autonomous trading needs a boundary between deciding to act and being allowed to act. A strategy may identify an opportunity, but it cannot bypass risk conditions, delegated session authority, or owner-defined policy. The Trade Intent is that boundary's input. The following stages evaluate whether the request satisfies the Pact's requirements. *** --- # 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://rwapact.gitbook.io/whitepaper/pact-execution/trade-intent.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.