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

# Developer

This section gives technical readers a high-level view of how `perps.` is structured.

It is intentionally public-facing. It does not document private infrastructure, secrets, deployment procedures, or internal operational runbooks.

## Design Principles

* On-chain state is the source of truth for trading and lifecycle state.
* Indexed data supports fast reads, charts, search, and profile views.
* The app is chain-explicit so users and developers can reason about the active network.
* Product surfaces should distinguish lifecycle state from trading readiness.

## Core Public Components

* Creator profile and identity layer.
* Social token launch and bonding-curve lifecycle.
* Perpetual market engine for supported markets.
* Market data indexing and read models.
* XP, badge, and rank progression.

## Out of Scope

* Private deployment topology.
* Secret management.
* Internal monitoring procedures.
* Admin-only actions.
* Incident response runbooks.


---

# 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://perps.gitbook.io/perps./overview-1.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.