> For the complete documentation index, see [llms.txt](https://masterverses.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://masterverses.gitbook.io/docs/introduction/publish-your-docs.md).

# History of Masterverse

Masterverse was conceptualized in 2025 to address the growing fragmentation in digital spirituality. While various meditation apps and religious forums existed, they lacked engagement, inclusivity, and reward mechanisms to truly immerse users in a gamified spiritual journey.

**The Early Days – A Tap-to-Earn Spiritual Game**

Masterverse initially launched as a "Tap-Tap" game, where users could:

1. Earn points by tapping on the screen.
2. Complete daily spiritual tasks to enhance engagement.
3. Participate in partner tasks to earn additional rewards.

This early iteration aimed to gamify spiritual practices and encourage daily participation, but the team quickly realized the potential for a more expansive and meaningful platform

<br>


---

# 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://masterverses.gitbook.io/docs/introduction/publish-your-docs.md?ask=<question>&goal=<endgoal>
```

`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.
