> ## 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.

# Leaderboard and Evidence

> How beta leaderboard rows should present scores, diagnostics, and reproducible artifacts.

The beta leaderboard is a presentation layer over evaluation responses.

<Tabs>
  <Tab title="Sort">
    Use `evaluation.data.score` as the beta row order.
  </Tab>

  <Tab title="Explain">
    Show risk, cost, benchmark, and eligibility diagnostics alongside score.
  </Tab>

  <Tab title="Replay">
    Preserve hashes and manifests so strong results can be reproduced.
  </Tab>
</Tabs>

## Beta rule

Sort by:

<Callout>
  Use `evaluation.data.score` as the beta leaderboard row order.
</Callout>

The router does not currently expose a server-owned cross-submission leaderboard
endpoint. The UI or thin client assembles rows locally from simulation and
evaluation calls.

## What every row should show

A useful row should show more than one number:

| Field                                 | Why it matters                 |
| ------------------------------------- | ------------------------------ |
| `score`                               | current public beta sort key   |
| `scenarioResult.annualizedMeanReturn` | return contribution            |
| `scenarioResult.maxDrawdown`          | peak-to-trough risk            |
| `scenarioResult.cvar`                 | tail-loss diagnostic           |
| `scenarioResult.turnover`             | churn and friction proxy       |
| `scenarioResult.executionCost`        | modeled cost drag              |
| `benchmarkUtility`                    | comparison denominator         |
| `eligibility.eligible`                | gate result                    |
| `capitalScore.capitalScore`           | stricter robustness diagnostic |

## Evidence artifacts

Evidence should be reproducible. Artifact mode should preserve:

<CardGroup cols={2}>
  <Card title="Inputs" icon="file-check">
    Input hashes, config hashes, dataset or snapshot hashes, and strategy
    registry snapshot hash when the menu affects outcomes.
  </Card>

  <Card title="Outputs" icon="file-check">
    Output hashes, report hashes, and dependency/package version information.
  </Card>
</CardGroup>

If a report cannot be replayed from committed inputs and referenced artifacts,
it is not strong evidence.

## Interpreting eligibility

Eligibility means the strategy passed the configured gates for a review or next
step. It does not mean the strategy receives capital.

Use this line consistently:

<Callout>
  Evidence creates eligibility. It does not guarantee capital.
</Callout>

## Related pages

<CardGroup cols={3}>
  <Card title="Scoring and benchmarks" icon="chart-line" href="/arena/scoring-and-benchmarks">
    Understand score, benchmark utility, CapitalScore, and ContestScore.
  </Card>

  <Card title="Guarded vaults" icon="shield" href="/capital/guarded-vaults">
    See how future vault review should consume evidence.
  </Card>

  <Card title="Public settlement" icon="file-check" href="/trust/public-settlement">
    Understand what can become public at execution time.
  </Card>
</CardGroup>