> For the complete documentation index, see [llms.txt](https://farm-and-filch.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://farm-and-filch.gitbook.io/whitepaper/documentation/getting-started/what-is-farm-and-filch.md).
# What is Farm & Filch?
A farming game where your neighbors are part of the strategy.
Most farming games ask:
> **How far can you grow your farm?**
Farm & Filch adds another question:
> **How well can you protect it?**
Every player has a farm to develop, resources to manage, and progress to make.
But every farmer can also become a **Filcher**.
When another farm presents an opportunity, you can leave the comfort of your own land and take a calculated risk on theirs.
#### One player. Two perspectives
**👨🌾 As a Farmer**
Grow, produce, expand, upgrade and decide what deserves protection.
**🥷 As a Filcher**
Read another farm, identify opportunities, manage risk and know when to escape.
#### The core loop
*GROW → HARVEST → BUILD → PROTECT → EXPLORE → FILCH → ESCAPE → GROW AGAIN*
#### What makes Farm & Filch different?
> Your farm isn't just something you build.
>
> **It's something other players can read, challenge, and remember.**
You don't choose one permanent role.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://farm-and-filch.gitbook.io/whitepaper/documentation/getting-started/what-is-farm-and-filch.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
