# Overview

Messaging is one of the most complicated software pieces. In this [Architecture section](broken://pages/N6T9ju2uFRq6H7apEBud), we will explain how does beoble maintain its core objectives, including but not limited to high privacy and feature richness, while remaining a stable software solution.

### High-level Architecture (BUIDLING)

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

[Communication Delivery Graph (CDG) section](/architecture/communication-delivery-graph-cdg.md) explains how beoble is aiming to maintain a high level of privacy in terms of message delivery while being decentralized. We are continuously building this!

{% content-ref url="/pages/AgJpGqXuDIzPIVPKJ6tY" %}
[Communication Delivery Graph  (CDG)](/architecture/communication-delivery-graph-cdg.md)
{% endcontent-ref %}

[Privacy & Encryption section](/architecture/privacy-and-encryption.md) explains how beoble is aiming to remain secure in terms of message content encryption.

{% content-ref url="/pages/U99ZpF9U4afhJRBX11aF" %}
[Privacy and Encryption](/architecture/privacy-and-encryption.md)
{% endcontent-ref %}

[Decentralized Identity & Social Graph section](/architecture/decentralized-identity-and-social-graph.md) explains how beoble allows users to create Web 3.0 identities with massive social graphs.

{% content-ref url="/pages/pWfE4h1qnztOpDTjCbl6" %}
[Decentralized Identity & Social Graph](/architecture/decentralized-identity-and-social-graph.md)
{% endcontent-ref %}

[Cross-Chain Data Connectivity section](/architecture/cross-chain-data-connectivity.md) explains how beoble maintains connections with existing popular blockchain networks like Ethereum, BSC, Polygon, Avalance, Solana, Aptos, Sui, etc.

{% content-ref url="/pages/NIltuzVqFGpG6PBEBp3c" %}
[Cross-Chain Data Connectivity](/architecture/cross-chain-data-connectivity.md)
{% endcontent-ref %}


---

# 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.beoble.io/architecture/overview.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.