> For the complete documentation index, see [llms.txt](https://docs.fairmath.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fairmath.xyz/fhe-computer/operating-system/execution-graph-and-tasks.md).

# Execution Graph and Tasks

In the Fair Math Computer, a **task** is the smallest unit of execution managed by the orchestration layer. A task consists of the following components:

1. **Instructions**\
   A task includes an ordered set of instructions that define its operations. This set must not be empty.
2. **Variables**\
   These are the variables used or created by the instructions in the task.
3. **Metadata**\
   Metadata provides additional information about the task, including:
   * **Resource requirements** (e.g., memory or compute power needed).
   * **Estimated complexity** of the task.
   * **Execution constraints**, such as deadlines or specific capabilities required.

A task is valid if it has at least one instruction and all instructions are compatible with the dependencies of the application.


---

# 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.fairmath.xyz/fhe-computer/operating-system/execution-graph-and-tasks.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.