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

# How It Works

> The live beta Strategy Arena flow from market discovery to evaluation evidence.

The Strategy Arena lets builders compare private strategy ideas under public,
fixed evaluation rules.

<CardGroup cols={3}>
  <Card title="One family live" icon="table">
    The implemented public family is `strategy-arena`.
  </Card>

  <Card title="Server-owned rules" icon="chart-line">
    Official datasets, execution policy, benchmark manifests, and scoring
    windows are resolved by the router.
  </Card>

  <Card title="Local leaderboard" icon="table">
    In beta, the UI assembles rows from evaluation responses rather than a
    server-owned ranking endpoint.
  </Card>
</CardGroup>

## The beta loop

<Steps>
  <Step title="Discover">
    Read the available strategy family, strategies, parameters, and markets.
  </Step>

  <Step title="Build">
    Compose a candidate from the supported strategy catalog.
  </Step>

  <Step title="Simulate">
    Run the candidate against the official arena dataset for the selected
    market.
  </Step>

  <Step title="Evaluate">
    Score the simulation result against the benchmark manifest.
  </Step>

  <Step title="Compare">
    Compare `score`, risk diagnostics, eligibility, and evidence artifacts.
  </Step>

  <Step title="Improve">
    Iterate without exposing the underlying idea to other builders.
  </Step>
</Steps>

## What is live

<Callout>
  The current public runtime exposes one implemented family:
  `strategy-arena`.
</Callout>

The implemented route surface supports:

<CardGroup cols={2}>
  <Card title="Discovery routes" icon="search">
    List families, read Strategy Arena metadata, list strategies, read
    parameter defaults and constraints, and list markets.
  </Card>

  <Card title="Computation routes" icon="chart-line">
    Run full simulations, compact summaries, trade-focused views, and one
    deterministic evaluation over a submitted simulation result.
  </Card>
</CardGroup>

## What is not live

The beta does not expose:

* server-owned public ranking endpoints,
* public wallet or encryption endpoints,
* public AMM endpoints,
* public swap endpoints,
* capital allocation endpoints.

The UI can assemble a local leaderboard from evaluation responses. The primary
sort key is `evaluation.data.score`.

## Market family

The first family is Pendle-style fixed-income strategy research. Current public
markets are identified by numeric ids and stable keys:

| Market id | Key      | Protocol |
| --------: | -------- | -------- |
|       `1` | `susde`  | Pendle   |
|       `2` | `susdf`  | Pendle   |
|       `3` | `ghousd` | Pendle   |

The public router resolves official datasets internally. Callers do not submit
raw internal dataset references in competition mode.

## Result shape

Successful API responses use a common envelope:

```json theme={null}
{
  "requestId": "req_123",
  "status": "ok",
  "data": {}
}
```

Failures use problem details with stable AlphaEngine extensions such as `code`,
`family`, `requestId`, and `fieldErrors`.

## Related pages

<CardGroup cols={2}>
  <Card title="Strategy submissions" icon="lock" href="/arena/strategy-submissions">
    What a candidate includes and what stays protected.
  </Card>

  <Card title="Scoring and benchmarks" icon="chart-line" href="/arena/scoring-and-benchmarks">
    How beta score, benchmark utility, CapitalScore, and ContestScore differ.
  </Card>

  <Card title="Leaderboard and evidence" icon="table" href="/arena/leaderboard-and-evidence">
    What a useful beta row should show.
  </Card>

  <Card title="API overview" icon="file-check" href="/api/overview">
    The implemented public route surface.
  </Card>
</CardGroup>