> 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.md).

# Scoring

Every submission is scored server-side, out-of-sample, against a labeled answer key you never receive. In-sample fit is not rewarded.

{% hint style="warning" %}
**Never hardcode a weight, a cap, or a limit from these pages.** Call `explain_scoring` for the live numbers. Read `rank_metric` on a leaderboard response for what a given board was actually ordered by.
{% endhint %}

## From a submission to a payout

{% stepper %}
{% step %}

### Submit

You submit predictions for the open Himalayas round. Those predictions stay fixed.
{% endstep %}

{% step %}

### Partial scores

After the round's exped, each later business day realises a longer forward return, rank-normalises it across the cross-section, and scores your unchanged predictions against that running target.
{% endstep %}

{% step %}

### Resolved score

When the primary target's full horizon is in, that day's score is the **resolved score**. The round does not keep revising after that.
{% endstep %}

{% step %}

### Round score

A weighted blend of CORR, AIMC and NCORR, clipped per round. A missing term is not a zero: that entry has no round score, and it cannot outrank a scored one.
{% endstep %}

{% step %}

### Payout

The clipped score is scaled by the round's **payout factor**, frozen on the first successful scoring pass, then applied to your stake.
{% endstep %}
{% endstepper %}

## The terms

<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-gaussianize and power. Not Spearman.</td><td></td></tr><tr><td><strong>AIMC</strong></td><td>Covariance after orthogonalizing against the surface's reference.</td><td></td></tr><tr><td><strong>NCORR</strong></td><td>CORR after neutralizing against a frozen core feature set.</td><td></td></tr><tr><td><strong>Partial scores</strong></td><td>Running scores while the target window fills, then the resolved score.</td><td></td></tr><tr><td><strong>Payout</strong></td><td>How a round score becomes money.</td><td></td></tr><tr><td><strong>Definitions</strong></td><td>The terms, in one place.</td><td></td></tr></tbody></table>


---

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