> For the complete documentation index, see [llms.txt](https://docs.mawari.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mawari.net/infrastructure/mawari-network-architecture.md).
# Mawari Network Architecture
The Mawari Network is architected from the ground up to meet the rigorous demands of AI powered, immersive, real-time 3D content delivery, particularly with regard to high levels of interactivity. Traditional internet infrastructure and cloud systems are not optimized for the streaming of high-fidelity interactive content required by Extended Reality applications. These applications depend on a continuous stream of low-latency data to deliver responsive, context-aware experiences, particularly those involving Augmented Reality and real-time interaction with the physical environment.
At the core of the Mawari architecture is the Mawari Engine, a proprietary streaming technology that enables the real-time orchestration of 3D content delivery. The system dynamically allocates computational, storage, and bandwidth resources based on proximity to the end user and real-time network conditions. This is accomplished through a distributed orchestration layer that interfaces with a global network of compute and storage nodes, removing single points of failure and increasing both scalability and resiliency.
By being distributed by design, the Mawari Network eliminates the bottlenecks typical of centralized content delivery systems. It allows for hyper-localized compute aggregation, enabling near-instant rendering and delivery of content to XR devices across any geography. This architecture supports a new paradigm of the embodied internet, where physical and digital experiences are seamlessly integrated in real time.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.mawari.net/infrastructure/mawari-network-architecture.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.