> For the complete documentation index, see [llms.txt](https://docs.awenetwork.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.awenetwork.ai/start-here/the-architecture-of-autonomous-worlds.md).
# The Architecture of Autonomous Worlds
Autonomous Worlds are powered by a cohesive and innovative framework called the **Autonomous Worlds Engine (AWE)**.
This architecture integrates modular components to create dynamic, self-sustaining ecosystems where AI agents can operate, adapt, and collaborate. AWE combines user inputs, advanced multi-agent systems, and blockchain-based transparency to enable intuitive, purpose-driven environments.
AWE Architecture
**Continuous Adaptation and Learning**
Autonomous Worlds are not static creations. They evolve continuously through user interaction, agent collaboration, and feedback loops. This persistent growth ensures the Worlds remain engaging, relevant, and adaptable to new challenges.
The **Autonomous Worlds Engine** integrates these elements into a seamless, scalable system. By anchoring the Worlds on blockchain, it ensures transparency and durability while enabling cutting-edge AI and multi-agent collaboration.
---
# 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.awenetwork.ai/start-here/the-architecture-of-autonomous-worlds.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.
.jpg?alt=media&token=bf2a8880-7295-49f1-8527-f2fc8919d9ab)
