> For the complete documentation index, see [llms.txt](https://docs.mrmylo.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mrmylo.xyz/standard-operating-procedures-department-of-corrections/s1/1.2-chain-of-command.md).

# 1.2 - Chain Of Command

{% hint style="success" %}
The San Andreas Department of Corrections has a simple rank structure. There is a clear definition of the authoritative power that comes connected with the assigned rank. The rank structure is as follows (starting from the top to the bottom):​
{% endhint %}

{% stepper %}
{% step %}

#### Wardens

**Wardens** have the highest level of authoritive power and are accountable to overseeing the entire department.

* Warden
* Deputy Warden
* Assistant Warden
  {% endstep %}

{% step %}

#### Captain

**Captains** work with the Wardens as members of High Command to efficiently manage the department. 
{% endstep %}

{% step %}

#### Lieutenant

**Lieutenants** are members of Low Command. They work with both High Command and Sergeants to ensure smooth day-to-day operations
{% endstep %}

{% step %}

#### Sergeant

**Sergeants** are department Supervisors. They ensure Correctional Officers follow the SOPs and take lead in situations.
{% endstep %}

{% step %}

### Correctional Officers

**Correctional Officers** are responsible for maintaining a safe prison environment. They are eligable to join divisions, and are allowed to operate alone.

* Senior Correctional Officer
* Correctional Officer

{% hint style="warning" %}
Corrections Officers are eligable to join the Field Training Divsion and Emergecy Response Team after 2 weeks of service as Corrections Officers.
{% endhint %}
{% endstep %}

{% step %}

### Corrections Cadet

**Correctional Cadets** are those in training. They fall under the supervision of the Field Training Program, and must have a Field Trainer on duty with them until they reach their Solo Phase.
{% endstep %}
{% endstepper %}


---

# 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://docs.mrmylo.xyz/standard-operating-procedures-department-of-corrections/s1/1.2-chain-of-command.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.