> For the complete documentation index, see [llms.txt](https://whitepaper.huralya.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.huralya.com/introduction.md). # Introduction What is Huralya? **HURA** is a next-generation psychological companion app that blends self-awareness, therapeutic journaling, lucid dreaming, and emotional gamification into a single AI-powered platform. At the heart of HURA is a deeply personal experience—where every mood, dream, thought, and behavioral pattern becomes a doorway to insight, guided not by rigid diagnostics, but by a living relationship with a mindful AI squirrel companion. Unlike traditional mental health tools, HURA is not built to label or treat—it is designed to *explore*, *mirror*, and *evolve*. Through encrypted, anonymous interactions, users engage in reflective dialogue, dream analysis, mood tracking, and guided practices like breathwork or emotional rewiring—each step gently shaped by insights from psychology, neuroscience, and philosophy. HURA is not just an app. It is a philosophy: that mental clarity, meaning, and transformation emerge when technology honors subjectivity, playfulness, and inner freedom. Whether you’re tracking feelings, confronting inner patterns, or building the habits of a more conscious self, HURA grows with you—learning not to fix who you are, but to help you better *become*. --- # 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://whitepaper.huralya.com/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.