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

# 🛣️ Roadmap

The roadmap follows the current release plan.

Phases may still evolve as development continues.

### Phase 1: Playtest

Run the first live tests and validate the core loop:

* server stability
* progression pacing
* balance feedback
* economy behavior

### Phase 2: Token launch

Launch the token after the first testing phase:

* token go-live
* in-game trading for **$CAVE**
* initial utility rollout
* market monitoring

### Phase 3: Game release

Release the full game to a wider audience:

* broader access
* stable live progression
* full core experience

### Phase 4: First major in-game event

Run the first large-scale live event after release:

* event-specific rewards
* community participation
* live economy and retention testing
* gold reward and gold-burn event formats

Some major events will reward players with gold.

Some will let players burn gold and receive $CAVE.


---

# 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://cave-of-fates.gitbook.io/cave/roadmap.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.