> For the complete documentation index, see [llms.txt](https://contact-182.gitbook.io/last-resort/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://contact-182.gitbook.io/last-resort/systems/long-term-vision.md).

# Long term vision

The goal of the project is to decentralize as much as possible of Central command's activity to players.

This starts with the [shops ](/last-resort/city-life/crafting-and-shop-licenses.md)being operated directly by players and will continue in <mark style="background-color:yellow;">subsequent seasons</mark> with:

* User Generated Content: Each season, players will be able to propose new equipment for different new item tiers. Holders of HC will be able to vote and the most voted will be introduced in the next update. A reward will be awarded to the creator and all backers will be offered a discount on the new gear crafting.<br>
* Decentralized Autonomous Operation: A city council will be formed, and a mayor nominated each season. They will be in charge of making regular choices for the entire community of players and will be recognizable by everyone thanks to a visible badge.


---

# 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://contact-182.gitbook.io/last-resort/systems/long-term-vision.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.