> For the complete documentation index, see [llms.txt](https://auralite.gitbook.io/auralite-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://auralite.gitbook.io/auralite-docs/reglement-auralite/reglement-global/zone-safe.md).

# Zone Safe

Les zones safes désignent des lieux particuliers où toute activité illégale ainsi que certains comportements sont formellement proscrits. Voici quelques règles essentielles à respecter dans ces zones.

<mark style="color:red;">**Comportements Interdits**</mark> <mark style="color:red;"></mark><mark style="color:red;">:</mark> Il est formellement interdit de kidnapper, de commettre un braquage, d’engager un combat <mark style="color:$danger;">(même de manière "amicale")</mark> ou de réaliser toute autre action illégale au sein d’une zone safe.

<mark style="color:$danger;">**Abus de Zone Safe**</mark> : Se réfugier volontairement dans une zone safe pour fuir une poursuite ou échapper à une situation conflictuelle est interdit. Ces zones ne doivent en aucun cas servir de cachette pour éviter une scène en cours.

<details>

<summary>Liste des zone safes valides</summary>

* 🚔 Commissariat.
* 🏛️ Gouvernement.
* 🏥 Hôpital.
* 🚗 Fourrières.
* 🅿️ Parking central.
* 🏪 Entreprises ou lieux de farm.
* 🏪 Magasin de vêtements/tatouage/LTD.

Aussi toutes les zones considérées comme *safe* grâce au script du serveur.

</details>


---

# 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://auralite.gitbook.io/auralite-docs/reglement-auralite/reglement-global/zone-safe.md?ask=<question>&goal=<user_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.