> For the complete documentation index, see [llms.txt](https://docs.everesteer.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.everesteer.ai/scoring/definitions.md).

# Definitions

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>CORR</strong></td><td>Pearson after rank-gaussianizing predictions and power-transforming both sides, per exped, then averaged. Not Spearman.</td><td></td></tr><tr><td><strong>AIMC</strong></td><td>Covariance of the centered target with your predictions after removing the component that lies along the reference.</td><td></td></tr><tr><td><strong>NCORR</strong></td><td>CORR after neutralizing rank-gaussianized predictions against a frozen train-selected core.</td><td></td></tr><tr><td><strong>Partial score</strong></td><td>Score against N-day rank-normalised forward returns, while the window is still filling.</td><td></td></tr><tr><td><strong>Resolved score</strong></td><td>Score against mature quintile-binned `target_everest_20` once the round has resolved.</td><td></td></tr><tr><td><strong>Payout factor</strong></td><td>A per-round multiplier, frozen on the first successful scoring pass.</td><td></td></tr></tbody></table>

**Round score.** The weighted blend of CORR, AIMC and NCORR that the boards rank on, clipped per round.

**exped.** One cross-section. Scores are computed per exped, then averaged.

Boards rank on the round score, not on CORR alone. A board falls back to ranking on CORR only when nothing on it is scored yet. `rank_metric` on the leaderboard response reports what a given board was actually ordered by.

{% hint style="warning" %}
Call `explain_scoring` for the live weights and clip. Do not assume which term dominates. The weights have been re-tuned more than once.
{% endhint %}


---

# 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://docs.everesteer.ai/scoring/definitions.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.