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

# Roadmap

The ordered implementation milestones defined for RAKE.

RAKE develops from Pons V2 integration into a connected X and dApp ecosystem. The sequence starts with fee infrastructure. It then adds visibility, controlled execution, asset support, and automation.

This is an implementation sequence. It does not specify dates, completion percentages, or delivery guarantees.

### Implementation sequence

1. **Resolve Pons V2 ABIs**\
   Resolve the Pons V2 contract interfaces that RAKE needs to integrate. This establishes the contract-level basis for launch and fee handling.
2. **RakeVault + HarvestRouter + tests**\
   Build RakeVault and HarvestRouter, with tests. These components provide the route for harvested fees and the source-defined distribution process.
3. **Dummy harvest onchain**\
   Validate the harvest path onchain with a dummy harvest. This tests the connection from fee sources into the vault before public surfaces depend on it.
4. **Web launch + unclaimed page**\
   Add the web launch surface and unclaimed page. This gives the system a dApp entry point around the established launch infrastructure.
5. **Launch $RAKE**\
   Launch $RAKE after the core launch and vault path exist. The token then participates in the documented fee and burn flow.
6. **Indexer + leaderboard**\
   Add indexing and the leaderboard. This makes launched-token activity, fees, burns, harvest timing, and status visible.
7. **X bot launch + harvest**\
   Launch and harvest become available through [@rake\_agent](https://x.com/rake_agent). This extends established protocol actions to the X interface.
8. **Echo engine**\
   Build the Echo engine for exact confirmations. This introduces the safety control needed before money-moving commands execute.
9. **tip / swap / buy / burn / buyback**\
   Add the money-moving command set after Echo is available. These actions use exact confirmation before assets move.
10. **RWA stock whitelist**\
    Add the defined RWA stock-token whitelist. This extends the supported asset universe with the listed stock tokens.
11. **Prediction market**\
    Add YES/NO prediction markets around defined outcomes. This builds on the RWA stock-token registry and pricing path.
12. **Bridge ETH to Robinhood**\
    Add the ETH bridge path from outside into Robinhood. This expands how ETH enters the documented ecosystem.
13. **LLM persona**\
    Add the conversational persona layer. It remains separate from parser- and schema-controlled execution.
14. **Keeper auto-harvest**\
    Add automated keeper harvesting. This uses the existing harvest route when accumulated fees are worthwhile and gas is cheap.

### How the system comes together

```
Pons V2 integration
  -> vault and harvest infrastructure
  -> onchain validation
  -> web launch surface
  -> $RAKE
  -> indexing and visibility
  -> X execution
  -> Echo safety
  -> money-moving commands
  -> RWA support
  -> prediction markets
  -> ETH bridge
  -> persona layer
  -> automated harvesting
```

The resulting system connects launch, harvest, trading, Echo-confirmed actions, RWA stock tokens, prediction markets, bridging, persona interaction, and automated harvesting. Each capability depends on the infrastructure before it.


---

# 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://docs.rakelaunch.xyz/rake/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.