> ## Documentation Index
> Fetch the complete documentation index at: https://docs.routor.io/llms.txt
> Use this file to discover all available pages before exploring further.

# What's Next

> Where the $ROUTOR ecosystem goes after launch, and the research behind it.

This tab covers what comes after the \$ROUTOR launch. Each item has a status. Nothing here is a commitment until it moves to the [Roadmap](/roadmap).

| Item | Status |
| - | - |
| [Finalise holder reward rules](#finalise-holder-reward-rules) | Next |
| [Token fees into the reward pool](#token-fees-into-the-reward-pool) | Proposed |
| [A router that learns from real outcomes](#a-router-that-learns-from-real-outcomes) | Planned, on the [Roadmap](/roadmap) |
| [Routing decision market](/future/routing-decision-market) | Research |

```mermaid theme={null}
flowchart LR
    L(["$ROUTOR launch"]):::positive --> R["Finalise reward rules\npool share · period · eligibility"]:::step
    R --> F["Token fees into the pool\nproposed"]:::warning
    L --> O["Router learns from outcomes\naccepted · retried · thumbs-down"]:::step
    O --> M["Routing decision market\nresearch"]:::warning

    classDef step fill:#0d0d0d,stroke:#9ca3af,color:#d1d5db
    classDef positive fill:#0d0d0d,stroke:#f3f4f6,color:#ffffff,stroke-width:2px
    classDef warning fill:#0d0d0d,stroke:#6b7280,color:#9ca3af,stroke-dasharray:3 3
```

***

## Finalise Holder Reward Rules

The mechanics in [Holder Rewards](/ecosystem/holder-rewards) are set. The numbers are not: the share of profit that goes to the pool, the length of a reward period, who is eligible, and how credits are split between holders. These will be published before rewards start.

## Token Fees Into the Reward Pool

The proposal is to direct \$ROUTOR token fees into the reward pool alongside Routor's profit. This would make the pool grow with token activity as well as product usage. It is not decided. The open question is whether it ties rewards too closely to trading rather than to real use of Routor.

## A Router That Learns From Real Outcomes

Every routed request has an outcome: the answer was accepted, retried, or rated down. That is the strongest signal for improving routing, and it needs no token and no crowd. The [Roadmap](/roadmap) covers how this ships: conversation storage first, then a trained scorer that learns from stored outcomes.

## Routing Decision Market

A research idea for letting \$ROUTOR holders predict which model is best for each kind of task, and rewarding them when they are right. The first version had a fatal flaw. A revised version fixes the main problem but has open risks. See [Routing Decision Market](/future/routing-decision-market) for the full write-up.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.