# High-Level Architecture

The illustration below shows how the <mark style="color:$info;">Alphix Hook</mark> connects with **Uniswap v4**, users, and external partners. By building directly on the protocol, Alphix introduces new financial products and capabilities that synergistically enhance the entire Uniswap ecosystem.

<figure><img src="https://2585924356-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkT5rrR3T549DQrmc5r1F%2Fuploads%2FnhZeUWegMBCudTho8kfc%2FDocumentation-1.png?alt=media&#x26;token=ea45d258-e132-4a22-bd61-f4595e4e1f8e" alt=""><figcaption></figcaption></figure>

On the left is the <mark style="color:$primary;">**Uniswap V4**</mark> infrastructure consisting of Pool Manager, Position Manager and Router. **Unified Pools** are launched on top of this infrastructure, but they rely on the single, shared **Alphix Hook** that adds powerful products.

The illustration below shows user interaction flows to explain how Alphix works in tandem with Uniswap. It traces the process from a trader's (and Liquidity Provider's) initial action through the stack to the **Alphix Hook**, which interacts with a **Fee Manager** to enable the Dynamic Fee feature.

<figure><img src="https://2585924356-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkT5rrR3T549DQrmc5r1F%2Fuploads%2FpovmFp9XC6TdMAGxtQ8S%2FDocumentation-2.png?alt=media&#x26;token=283ff30d-de90-4b33-8237-f67dedb4024e" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Depending on the feature, the Alphix Hook requires an externally owned address to call functions. In the Dynamic Fee product, this role is filled by a Fee Manager who executes the algorithm randomly depending on Pool Type.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://alphix.gitbook.io/docs/the-basics/architecture.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
