> For the complete documentation index, see [llms.txt](https://t2-world.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://t2-world.gitbook.io/docs/onboarding/get-started-as-a-reader/what-is-a-territory.md).
# What is a Territory?
Territories are decentralised article clubs. As repositories of content, these house the different on-chain articles that you can read grouped according to a specific topic.
At the same time, territories are also living reader-writer communities. Once you join one, you not only can read everything within it. Eventually, you’ll be able to engage with writers and your fellow readers, suggest articles, pitch ideas or sub-territories (aka Spaces), and more.
When you join a territory, you can read all the content you want, and get rewarded with Time Points for the time you spend reading.
When you accumulate enough Time Points, you can be a Territory member. We currently define a Territory member as someone who has over 120 Time Points in a territory—we will diversify this logic soon.
---
# 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://t2-world.gitbook.io/docs/onboarding/get-started-as-a-reader/what-is-a-territory.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.