> 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.md).

# GamePad's White Paper

- [1. Abstract](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/1.-abstract.md)
- [2. Market Background](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/2.-market-background.md)
- [2.1 The Evolution of AI and Autonomous Agents in Decentralized Finance](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/2.-market-background/2.1-the-evolution-of-ai-and-autonomous-agents-in-decentralized-finance.md)
- [2.2 Market Pain Points](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/2.-market-background/2.2-market-pain-points.md)
- [3. About GamePad.co](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/3.-about-gamepad.co.md)
- [3.1 What is GamePad?](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/3.-about-gamepad.co/3.1-what-is-gamepad.md)
- [3.2 Our Vision](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/3.-about-gamepad.co/3.2-our-vision.md)
- [3.3 Design Concept and System Principles](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/3.-about-gamepad.co/3.3-design-concept-and-system-principles.md)
- [4. System Architecture](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/4.-system-architecture.md)
- [4.1 Computing Power and Resource Layer](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/4.-system-architecture/4.1-computing-power-and-resource-layer.md)
- [4.2 Intelligent Execution Layer](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/4.-system-architecture/4.2-intelligent-execution-layer.md)
- [4.2.1 Operational Model](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/4.-system-architecture/4.2-intelligent-execution-layer/4.2.1-operational-model.md)
- [4.2.2 System Structure](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/4.-system-architecture/4.2-intelligent-execution-layer/4.2.2-system-structure.md)
- [4.2.3 Security and Boundary Control](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/4.-system-architecture/4.2-intelligent-execution-layer/4.2.3-security-and-boundary-control.md)
- [4.3 Runtime Interface Layer](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/4.-system-architecture/4.3-runtime-interface-layer.md)
- [4.3.1 Interface Abstraction](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/4.-system-architecture/4.3-runtime-interface-layer/4.3.1-interface-abstraction.md)
- [4.3.2 Agent and Execution Lifecycle Integration](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/4.-system-architecture/4.3-runtime-interface-layer/4.3.2-agent-and-execution-lifecycle-integration.md)
- [4.3.3 Real-time performance, stability, and risk constraints](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/4.-system-architecture/4.3-runtime-interface-layer/4.3.3-real-time-performance-stability-and-risk-constraints.md)
- [4.3.4 Permissions and Execution Boundaries](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/4.-system-architecture/4.3-runtime-interface-layer/4.3.4-permissions-and-execution-boundaries.md)
- [4.4 Cross-layer operation capability](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/4.-system-architecture/4.4-cross-layer-operation-capability.md)
- [4.4.1 Status and Execution Receipt Mechanism](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/4.-system-architecture/4.4-cross-layer-operation-capability/4.4.1-status-and-execution-receipt-mechanism.md)
- [4.4.2 Model and Strategy Lifecycle Management](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/4.-system-architecture/4.4-cross-layer-operation-capability/4.4.2-model-and-strategy-lifecycle-management.md)
- [4.4.3 Operational Observability and Control](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/4.-system-architecture/4.4-cross-layer-operation-capability/4.4.3-operational-observability-and-control.md)
- [4.4.4 Isolation and Security Boundaries](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/4.-system-architecture/4.4-cross-layer-operation-capability/4.4.4-isolation-and-security-boundaries.md)
- [5. Operational Mechanism and Ecological Collaboration](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/5.-operational-mechanism-and-ecological-collaboration.md)
- [5.1 Incubation and Launch System](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/5.-operational-mechanism-and-ecological-collaboration/5.1-incubation-and-launch-system.md)
- [5.1.1 Phased Path](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/5.-operational-mechanism-and-ecological-collaboration/5.1-incubation-and-launch-system/5.1.1-phased-path.md)
- [5.1.2 System Validation and Expansion Preparations for Operational Capabilities](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/5.-operational-mechanism-and-ecological-collaboration/5.1-incubation-and-launch-system/5.1.2-system-validation-and-expansion-preparations-for-operational-capabilities.md)
- [5.1.3 Launch Structure](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/5.-operational-mechanism-and-ecological-collaboration/5.1-incubation-and-launch-system/5.1.3-launch-structure.md)
- [5.1.4 Token and TGE Design](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/5.-operational-mechanism-and-ecological-collaboration/5.1-incubation-and-launch-system/5.1.4-token-and-tge-design.md)
- [5.1.5 Evolution after launch](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/5.-operational-mechanism-and-ecological-collaboration/5.1-incubation-and-launch-system/5.1.5-evolution-after-launch.md)
- [5.2 Application and scheduling of runtime resources](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/5.-operational-mechanism-and-ecological-collaboration/5.2-application-and-scheduling-of-runtime-resources.md)
- [5.2.1 Types and Use Cases of Running Resources](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/5.-operational-mechanism-and-ecological-collaboration/5.2-application-and-scheduling-of-runtime-resources/5.2.1-types-and-use-cases-of-running-resources.md)
- [5.2.2 Division of Roles within the Operating Unit](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/5.-operational-mechanism-and-ecological-collaboration/5.2-application-and-scheduling-of-runtime-resources/5.2.2-division-of-roles-within-the-operating-unit.md)
- [5.2.3 Scheduling and Execution Path](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/5.-operational-mechanism-and-ecological-collaboration/5.2-application-and-scheduling-of-runtime-resources/5.2.3-scheduling-and-execution-path.md)
- [5.3 Incentive and Participation Mechanisms During Operation](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/5.-operational-mechanism-and-ecological-collaboration/5.3-incentive-and-participation-mechanisms-during-operation.md)
- [5.4 Governance and Long-Term Evolution](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/5.-operational-mechanism-and-ecological-collaboration/5.4-governance-and-long-term-evolution.md)
- [5.5 Developer Toolchain](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/5.-operational-mechanism-and-ecological-collaboration/5.5-developer-toolchain.md)
- [5.5.1 Access Layer: SDK/API and Runtime Interface Specifications](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/5.-operational-mechanism-and-ecological-collaboration/5.5-developer-toolchain/5.5.1-access-layer-sdk-api-and-runtime-interface-specifications.md)
- [5.5.2 Agent Integration](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/5.-operational-mechanism-and-ecological-collaboration/5.5-developer-toolchain/5.5.2-agent-integration.md)
- [5.5.3 Resource and Status Visualization](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/5.-operational-mechanism-and-ecological-collaboration/5.5-developer-toolchain/5.5.3-resource-and-status-visualization.md)
- [5.5.4 Testing, Gray-Scale Deployment and Launch](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/5.-operational-mechanism-and-ecological-collaboration/5.5-developer-toolchain/5.5.4-testing-gray-scale-deployment-and-launch.md)
- [6. Economic Model](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/6.-economic-model.md)
- [6.1 Main Token: GPAD](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/6.-economic-model/6.1-main-token-gpad.md)
- [6.2 Sub-Token: IPAD](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/6.-economic-model/6.2-sub-token-ipad.md)
- [6.3 Division of Uses and Collaboration Between Dual-Tokens](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/6.-economic-model/6.3-division-of-uses-and-collaboration-between-dual-tokens.md)
- [7. Roadmap](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/7.-roadmap.md)


---

# 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://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper.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.
