> For the complete documentation index, see [llms.txt](https://docs.realmtoken.vip/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmtoken.vip/3.-land-protocol/spatial-sovereignty.md).

# Spatial Sovereignty

In REALM.AI, land is not just a static background image. It is a finite, programmable asset that grants you sovereign control over a specific slice of the hyper-realistic world.

Unlike infinite-world games where space is worthless, REALM.AI is built on a Master Plan. The world size is fixed. The districts are curated. Scarcity is hard-coded.

#### The Technical Standard

* Asset Type: ERC-721 Non-Fungible Token
* Coordinates: Every parcel is defined by permanent (X, Y) coordinates on the Global Grid.
* Adjacency: Location matters. Owning land next to the "Genesis Plaza" or a major "Transport Hub" ensures higher organic foot traffic from other players.

#### Why Own Land?

1. Permanence: Your structures remain in the world 24/7, even when you log off.
2. Discovery: Your location appears on the global map and GPS navigation system.
3. Monetization: Only landowners can host commercial activities, sell items, or display advertising.


---

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

```
GET https://docs.realmtoken.vip/3.-land-protocol/spatial-sovereignty.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.