> For the complete documentation index, see [llms.txt](https://ss3d.gitbook.io/design/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ss3d.gitbook.io/design/entities/roles/crew/command.md).

# Command

## Command <img src="https://lh3.googleusercontent.com/Gu82RVgvMEJshQ79i0fFAW66sFtgTQLpF0AfwWAyR1F3l7HRUfMEF4FfTpmX8vjrk_9rxG7ehL-0jjHLnOS2A6S8CC0wLM7EWRi5OGGk5-j8qg-7am-LlKL4CxpPE6MiTQBYwsnmByIs66rAcKTFVw" alt="" data-size="line">

The command department is a leadership department which consists of 1 leader from each department. These department leaders have special permissions and access. They can access the command bridge and use various command-only equipment. They also have their own private offices tucked inside of their respective departments.

<details>

<summary>Captain</summary>

**Quantity: 1**

Supervisor to all other command roles.

Head honcho of the entire station. Everyone is subordinate to this role.

</details>

<details>

<summary>Head of Personnel (HOP)</summary>

**Quantity: 1**

Supervisor to all [civilian roles](#civilian).

Also in charge of administrative duties such as modifications to crewmember ID’s. Second in command behind the captain.

</details>

<details>

<summary>Head of Security (HOS)</summary>

**Quantity: 1**

Supervisor to all [security roles](#security).

</details>

<details>

<summary>Chief Engineer (CE)</summary>

**Quantity: 1**

Supervisor to all [engineering roles](#engineering).

</details>

<details>

<summary>Chief Medical Officer (CMO)</summary>

**Quantity: 1**

Supervisor to all [medical roles](#medical).

</details>

<details>

<summary>Research Director (RD)</summary>

**Quantity: 1**

Supervisor to all [science roles](#science).

</details>

<details>

<summary>Quartermaster (QM)</summary>

**Quantity: 1**

Supervisor to all [supply roles](#supply).

</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 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://ss3d.gitbook.io/design/entities/roles/crew/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.