> For the complete documentation index, see [llms.txt](https://gamepad-2.gitbook.io/gamepad-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/4.-system-architecture/4.2-intelligent-execution-layer.md).

# 4.2 Intelligent Execution Layer

The intelligent execution layer inherits the schedulable computing power provided by the computing power and resource layer, addressing the core operational needs of decentralized finance (DeFi) and providing a unified environment for AI inference and long-term agent execution. In DeFi scenarios, AI is no longer merely used for offline analysis or decision support, but directly participates in strategy execution, risk control, and system regulation; agents, in the form of long-term operating units, continuously participate in the operation of the financial system.

The design goal of the intelligent execution layer is to upgrade the above capabilities from "discrete invocation" to a sustainable financial execution system, so that strategy reasoning, behavior scheduling and state feedback can run stably for a long time after the protocol goes online, and always remain within the observable and governable engineering boundaries.


---

# 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://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/4.-system-architecture/4.2-intelligent-execution-layer.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.