> For the complete documentation index, see [llms.txt](https://docs.gpubase.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gpubase.network/platform-architecture/workflow-overview.md).

# Workflow Overview

The platform workflow is designed to optimize the user experience and ensure efficient resource allocation:

1. **Task Submission**: Users submit computational tasks through the platform.
2. **Smart Contract Initiation**: Smart contracts automatically trigger agreements between users and providers.
3. **Resource Allocation**: The resource matching engine finds the best-suited GPU provider for the task, distributing the workload across available nodes as needed.
4. **Task Execution**: Providers execute the tasks, and the platform facilitates real-time progress monitoring for users.
5. **Completion and Payment**: Once a task is completed, the payment is processed securely through the blockchain, and providers receive their earnings.

This architecture supports the flexibility and scalability required for high-performance computing, making GPUBase Network an innovative solution in the world of decentralized applications.


---

# 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.gpubase.network/platform-architecture/workflow-overview.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.