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

# Signal Tiers

Signal tiers help users scan confluence quickly.

## Prime

Prime means the token has enough market cap and wallet-quality evidence to deserve main-board attention.

## Building

Building means attention is forming and the token is viable enough to watch closely, but the evidence may be less complete than Prime.

## Early Watch

Early Watch is a lower market-cap exception. It appears only when wallet quality is strong enough to overcome the usual low-cap noise filter.

## Suppressed

Suppressed rows do not appear on the user-facing board. Common reasons include low market cap, pre-bond status, weak wallet quality, or risky-wallet dominance.

## How To Use Tiers

Tiers should guide attention, not replace judgment.

Prime deserves inspection. Building deserves monitoring. Early Watch deserves caution because it usually sits closer to the noisy end of the market. Suppressed means the system saw something but decided users should not see it on the main board.


---

# 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://dopameme.gitbook.io/docs/signals/signal-tiers.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.