> 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/develop/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 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://guardian.hedera.com/docs/develop/guardian/workspace/decentralized-guardian/how-decentralized-execution-differs-from-a-single-instance.md?ask=&goal= ``` `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.