> For the complete documentation index, see [llms.txt](https://peeps-2.gitbook.io/peeps-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://peeps-2.gitbook.io/peeps-docs/peeps-whitepaper/how-it-works/discovery-and-community.md).

# discovery and community

PEEPS is built around the idea that token discovery and community formation should happen together.

## Discovery views

* **New launches** — recently created tokens;
* **Trending** — activity-based discovery using disclosed ranking criteria;
* **Final stretch** — launches approaching graduation;
* **Graduated** — tokens trading in external pools;
* **Live activity** — recent launches, buys, sells and milestones; and
* **Communities** — pages organized around active token groups.

## Ranking transparency

Sponsored placements, if introduced, must be labeled. Organic ranking criteria should be described at a high level so users can distinguish activity from paid promotion.

## Community tools

Planned community tools may include follows, comments, creator posts, share cards, launch milestones and reporting. Community activity is not due diligence; users must verify contracts and risks independently.


---

# 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://peeps-2.gitbook.io/peeps-docs/peeps-whitepaper/how-it-works/discovery-and-community.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.