# Architecture by Layers

Zooming out, the architecture is quite straightforward. The 4P App client sits on the top, powered by the [OCC SDK](https://wiki.4thtech.io/docs/integration/sdk), [OCC Protocol v.1](https://wiki.4thtech.io/docs/architecture/protocol), [encryption,](https://docs.the4thpillar.io/developers/architecture-by-layers/encryption) [PollinationX ](https://wiki.pollinationx.io/overview/px-storage-nft)decentralized storage service, and [blockchain networks](/dapps-and-clients/multi-chain-deployment.md). 4P smart contracts enable Four Token RTA (i.e. right-to-access) models within the system, enabling users to access the 4P Super App Pro features.

<figure><img src="/files/DvS63rGZ3biMNmPgVsv9" alt=""><figcaption></figcaption></figure>


---

# 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://docs.the4thpillar.io/developers/architecture-by-layers.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.
