# Leaderboard

{% hint style="warning" %} <sub>Leaderboard compares</sub> <sub></sub><sub>**signals ARIA can see**</sub><sub>. It is not a full financial audit of another operator & builder bank account.</sub>
{% endhint %}

<h3 align="center"><sub>How ranking works (simple rules)</sub></h3>

<table><thead><tr><th width="154.90911865234375">Input</th><th>Meaning</th></tr></thead><tbody><tr><td><sub><strong>Apps launched</strong></sub></td><td><sub>Ships that cleared the bar to count as a launch</sub></td></tr><tr><td><sub><strong>Ideas validated</strong></sub></td><td><sub>Serious passes on ideas, not “likes”</sub></td></tr><tr><td><sub><strong>Revenue score</strong></sub></td><td><sub>Momentum signal where connected (not every org has the same wiring)</sub></td></tr><tr><td><sub><strong>Top shipper</strong></sub></td><td><sub>Streak style signal for the current snapshot</sub></td></tr></tbody></table>

<sub>**Tie break hint in the product:**</sub> <sub></sub><sub>launches first, validations break ties. Read the small hint under the table title so you narrate the board fairly to your team.</sub>

<h3 align="center">Three habits</h3>

{% stepper %}
{% step %} <sub>**First**</sub>

<sub>Read the snapshot time before you screenshot. A stale snapshot creates false drama.</sub>
{% endstep %}

{% step %} <sub>**Second**</sub>

<sub>When the table is empty, say “the network has not published enough launches yet,” not “the product is broken.” Empty is a</sub> <sub></sub><sub>**data state**</sub><sub>.</sub>
{% endstep %}

{% step %} <sub>**Third**</sub>

<sub>Use Leaderboard for</sub> <sub></sub><sub>**orientation**</sub><sub>, use Overview for</sub> <sub></sub><sub>**your own**</sub> <sub></sub><sub>pipeline health. Same day, two different jobs.</sub>
{% endstep %}
{% endstepper %}

***

<h3 align="center"><sub>Ask yourself</sub></h3>

<p align="center"><sub><strong>What decision changes if your rank moves by one place this week?</strong></sub> <br><sub>If nothing changes, you are using the tool as entertainment. That is fine, but name it.</sub></p>


---

# Agent Instructions: 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:

```
GET https://docs.ariaagi.com/workspace/leaderboard.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
