> 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/history.md). # History AWE Network began its journey as STP Network, a project launched in 2019 with a focus on decentralized governance and Web3 RWA and tokenization infrastructure. Over the years, STP evolved alongside the ecosystem. In 2023, we realigned our mission toward a new frontier, Autonomous Worlds. This shift began with foundational tools like AWNS (Autonomous Worlds Name Service) and Clique, our Layer 3 platform designed for AI-enhanced gaming. By Q3 2024, we committed fully to this vision, building the Autonomous Worlds Engine (AWE), a modular framework designed to power persistent, scalable, AI-native environments where agents and humans co-create, govern, and evolve. The rebrand from STP to AWE Network marks a natural progression, from infrastructure to imagination, from governance rails to living worlds. It reflects our commitment to pushing the boundaries of AI x Web3, and to shaping a future where Autonomous Worlds are not just possible, but inevitable. --- # 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/history.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.