> For the complete documentation index, see [llms.txt](https://bountytemple.gitbook.io/whitepaper-v1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bountytemple.gitbook.io/whitepaper-v1/scholar-ecosystem/core-ecosystem/scholar-scoring-system-sss.md).

# Scholar Scoring System (SSS)

Bounty Temple's Scholar Scoring System (SSS) uses a 5-star rating system to ensure stellar performance from Scholars. Star ratings are automatically calculated using machine-learning.

Before becoming Scholars, players will have to go through a KYC (Know Your Customer) process to verify their accounts. Furthermore, only 1 account is permitted per Scholar, thus preventing systemic abuse or under-performance by Scholars who open multiple accounts.

<figure><img src="/files/Maj4iCdZagXFuTsC75aI" alt=""><figcaption></figcaption></figure>

### High-Ranker Perks

Highly-rated Scholars will have a higher chance of renting BTMs, thus incentivising them to maintain their reputation and score.

In addition, they will be promoted to "Uprising Manager", which gives them a chance to be listed in the House of Pluto (HOP) and receive sponsorships. This enables them to manage teams of Scholars under them for greater rewards.


---

# 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://bountytemple.gitbook.io/whitepaper-v1/scholar-ecosystem/core-ecosystem/scholar-scoring-system-sss.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.