> 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/introduction/the-architecture-of-autonomous-worlds/system-components.md). # System Components The AWE framework is tied together by several supporting layers: * **Simulation Layer**: Facilitates real-time simulations, tracking agent interactions, learning processes, and emergent behaviors within the defined environment. * **Feedback System**: Continuously refines agent behavior, simulation rules, and World parameters based on user input and system observations. * **Settlement Layer**: Logs all agent activities, state changes, and decisions onchain, ensuring transparency, verifiability, and support for tokenized economies. * **Visualization Interface**: Provides users with an interactive graphical interface to monitor agent behaviors, interact with the World, and gain actionable insights. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.awenetwork.ai/introduction/the-architecture-of-autonomous-worlds/system-components.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.