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

# Phase 4

The fourth phase of our developmental roadmap begins upon the completion of the mobile release at the end of 2024, and runs concurrent with [phase five](/the-business/developmental-roadmap/phase-5.md). This phase embellishes on the PC/Mac and Android/iOS builds, with the focus being on solo career, achievements, player progression, and the announcement of the seasonal Coinracer Championship tournaments.

{% hint style="info" %}
Expected deliverables for the fourth developmental phase will be listed in the coming months. For the time being, refer to the top-level scope to understand the objectives of this production window.
{% endhint %}


---

# 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://documentation.coinracer.io/the-business/developmental-roadmap/phase-4.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.