> For the complete documentation index, see [llms.txt](https://wp.warped.games/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wp.warped.games/lore/lore-introduction.md).
# Lore Introduction
The Beginnings of a New Universe
Re-emerging from the remnants of a chaotic, ancient realm, this universe challenges the boundaries of space and time as we know them. Overseen by the Oracle, an enigmatic artificial intelligence, humanity is called upon to face a daunting task: restoring balance to a fragile and volatile universe. Among the many, only the most creative and determined individuals are chosen by the Oracle to embark on this transformative mission. The ingenuity and resolve of these select individuals will be tested as they navigate mysteries, harness volatile forces, and contend with a relentless adversary threatening to erase anything and everything in its path.
Those brave enough to heed the Oracle’s call are drawn to Celadon Station, a repurposed oil rig concealing a cutting-edge particle enrichment laboratory deep beneath the Pacific Ocean. There, armed with knowledge provided by the Oracle, scientists have engineered the Celadon Gate, a portal leading to a new dimension so incomprehensible that it could only be described as the Warped Universe.
Image of Celadon Gate - the portal to the Warped Universe.
---
# 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://wp.warped.games/lore/lore-introduction.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.
