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

# ROADMAP

### ✅ PHASE 1 - February - May

* ✅ TOM Clicker 1.0 Launch
* ✅ Community creation
* ✅ 200,000 players 
* ✅ Blockchain Partnership
* ✅ Tier 1 Advisor Partnership

### PHASE 2 - June

* ✅ 400,000 players
* ✅ Launchpad Agreements
* ✅ Anti-hack system
* ✅ Rankings in real time
* ✅ KOL Partnerships

### PHASE 3 - July

* ✅ 900,000 players
* ✅ APP Redesign
* ✅ TOM's Story Video
* ✅ Profile section in APP

### PHASE 4 - August

* ✅ 1,500,000 players
* ✅Connect Wallet

### PHASE 5 - September

* 2,000,000 players
* $TOM Presale
* $TOM Launch
* TOM Clicker End of Season 1 + Snapshot
* TOM Clicker Start of Season 2
* MY BUDDY TOM (Tamagotchi) mini-game launch
* Achievements
* Airdrop Winners Announcement
* Airdrop Start
* Buy-Backs and Burns of $TOM

### PHASE 6 - October

* 3,000,000 players
* In-app purchases with $TOM
* Guilds
* Ranking leaderboard
* TOM ARENA (Auto-battle) mini-game launch
* NFT Collection
* More coming soon


---

# 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://toms-whitepaper.gitbook.io/tomclicker-whitepaper/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.