> 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-legal/reglement-forces-de-lordre/reglement-convoi-fdo.md).

# Règlement Convoi FDO

Règles concernant les convois côté forces de l'ordre

{% hint style="info" %}
Ces règles encadrent les négociations lors d'attaques de convois par des groupes illégaux.
{% endhint %}

### 🚔 Côté Police

L'objectif principal pour les groupes est de taper le véhicule transportant la cargaison, et non le dernier véhicule du convois.

| Situation                                   | Règle de négociation                                   |
| ------------------------------------------- | ------------------------------------------------------ |
| Véhicule tapé = **dernier véhicule**        | Interdiction de donner plus de **15%** de la cargaison |
| Véhicule tapé = **véhicule de marchandise** | Négociation habituelle (jusqu'à 100%)                  |

{% hint style="warning" %}
Pour être équitable, le **nombre d'otages** ne doit pas être le critère déterminant sur la négociation, mais le **véhicule transportant les marchandises**.
{% endhint %}

### 🔫 Côté Illégal

| Règle                                                                                                       | Statut |
| ----------------------------------------------------------------------------------------------------------- | ------ |
| Interdiction de taper un convoi à proximité du lieu de départ (poste de police, zone de perquisition, etc.) | ❌      |


---

# 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-legal/reglement-forces-de-lordre/reglement-convoi-fdo.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.