> For the complete documentation index, see [llms.txt](https://velora-2.gitbook.io/velora-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://velora-2.gitbook.io/velora-docs/police-rules/code-0.md).

# CODE 0

* A patrol must have at least 2 officers, with at least 1 holding the rank of Soldier or higher.
* An officer can only approach suspects when they have a numerical advantage of at least 1 more officer.
* It is mandatory to handcuff a suspect before any safety checks. Act quickly to prevent other criminals from intervening.
* A backpack or gang shirt cannot be used as a reason to stop someone.
* Searches should only occur in situations of clear suspicion.
* Wearing a mask or a holster requires a mandatory search. Police officers who act toxic during a stop will receive a warning.
* A stop can be made as long as there is suspicion (e.g., wearing a mask, a holster, or clothes that conceal weapons) and as long as the Get Out and Fight rule is respected.
* Police can only perform stops during robbery hours, and they must respect the hours defined for the South and North regions.


---

# 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://velora-2.gitbook.io/velora-docs/police-rules/code-0.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.