> For the complete documentation index, see [llms.txt](https://guardian.hedera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guardian.hedera.com/docs/3.7.0/guardian/workspace/decentralized-guardian/how-decentralized-execution-differs-from-a-single-instance.md).

# How Decentralized Execution Differs from a Single Instance

* **Processing time**. Because the main policy lives in another instance, each action in the remote policy (choosing a role, submitting a form, approving a step) must be synchronized through Hedera. The UI shows "You have new remote policy actions. Wait for the event to be processed." Expect to wait briefly after each action.
* **Incoming Requests**. Actions arrive as requests that need approval. Role selections, document signing, and outgoing messages appear in the Incoming Requests queue and must be approved before the workflow moves on. This queue only exists for decentralized execution.
* **Main instance execution**. Operations for the policy inside the main instance are unchanged: policy execution in the main instance works exactly as a private policy, with no extra request approvals required or waiting times.
* **Ownership**. The instance that published the policy remains the main instance and continues to own the policy, regardless of how many external instances import and execute it.


---

# 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://guardian.hedera.com/docs/3.7.0/guardian/workspace/decentralized-guardian/how-decentralized-execution-differs-from-a-single-instance.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.
