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

# Product Surfaces

> How the Centaur app maps to the underlying trading data concepts.

The Centaur app is organized around a small set of read surfaces. Each one answers a different question about the tracked trader universe.

| Surface              | Route          | Use it for                                                                                           |
| -------------------- | -------------- | ---------------------------------------------------------------------------------------------------- |
| **Trader Discovery** | `/traders`     | Finding traders by performance, focus, positioning, and trading style.                               |
| **Asset Discovery**  | `/assets`      | Finding assets with active trader involvement and current open-position skew.                        |
| **Feed**             | `/feed`        | Monitoring recent trade activity across all tracked traders or only followed traders.                |
| **Following**        | `/following`   | Managing the traders and assets you follow.                                                          |
| **Trader Profile**   | `/traders/...` | Reviewing one trader's current positions, historical position performance, and source-backed events. |
| **Asset Profile**    | `/assets/...`  | Reviewing one asset across all tracked traders.                                                      |
| **Assistant**        | In-app panel   | Asking tool-backed questions against Centaur data.                                                   |
| **Settings**         | `/settings/*`  | Managing API keys, connected apps, profile settings, and Telegram bot setup.                         |

The app home currently opens Trader Discovery. Live activity is a dedicated Feed surface rather than a three-panel home screen.

## Product data model

Centaur product surfaces combine four public concepts:

* **Messages** show source texture: what a trader said, when they said it, and any attached media.
* **Events** show structured trade actions: open, increase, decrease, and close.
* **Positions** group related events into current or historical trade records.
* **Stats** aggregate time-based performance, asset focus, and positioning metrics.

Use [Messages vs Events vs Positions](/docs/methodology/profile-trades) for the detailed relationship between these concepts.

## Current positioning

Current positioning comes from open positions, not generated summaries. When the app shows asset or trader positioning, it is using currently open long and short positions, usually expressed as counts or percentages.

## Performance

Performance surfaces use fixed **Time-Based Performance** windows: `1D`, `7D`, and `30D`. These measure each position at a fixed time after entry. They are distinct from current open-position return and from close-based realized return.

See [Positioning vs Performance](/docs/methodology/positioning-vs-performance) for the full distinction.

## Evidence

Where a data point comes from a source message, the app links back to the original source material when available. Event drawers and source previews expose the message text, timestamp, attachments, and original-source link without making the product a raw transcript browser.

See [Source Transparency](/docs/platform/source-transparency).