> 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.md).
# Core Ecosystem
Bounty Temple is built on a mutually beneficial core ecosystem of Sponsors, Managers, and Scholars. It is a three-way symbiotic cycle that benefits all parties.
Sponsors
Sponsors are individuals who do not want to invest time playing the game, preferring to pump in funds to Managers via the House of Pluto (HOP) system, who will then outsource the grind to Scholars. Sponsors will then enjoy the rewards earned in-game via profit-sharing, thus exerting little to no effort at all.
Managers
Managers are BTM owners who rent out BTMs to Scholars through the Rental System. They then take a share of the rewards farmed by the Scholars.
Scholars
Scholars are usually Bounty Temple players who do not own their own BTMs. Instead, they rent Scholar-owned BTMs from Managers to play the game. The rewards that they earn from playing the game will then be shared with the Manager and Scholar.
---
# 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.md?ask=&goal=
```
`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.