> For the complete documentation index, see [llms.txt](https://docs.octora.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.octora.xyz/documentation/product/how-it-works.md).

# How It Works

At a high level, Octora separates the wallet a user starts from and the wallet that ultimately performs the liquidity action.

The intended flow includes:

1. the user selects a liquidity opportunity
2. the user begins a private deposit flow
3. funds move through a privacy-oriented path
4. a stealth wallet is funded for execution
5. the stealth wallet performs the liquidity action through Octora’s executor layer

Behind the scenes, Octora combines several components:

* a frontend interface for user flows
* a backend API for orchestration
* a mixer path for privacy separation
* a relayer for withdrawal execution
* a stealth wallet for venue interaction
* an executor program that performs LP actions against Meteora

The result is not “perfect invisibility.” Instead, the goal is to reduce direct wallet-to-strategy linkage compared with a plain direct-execution flow.


---

# 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.octora.xyz/documentation/product/how-it-works.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.
