> For the complete documentation index, see [llms.txt](https://combat-alert-scorpion.gitbook.io/combat-alert-scorpion-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://combat-alert-scorpion.gitbook.io/combat-alert-scorpion-docs/rules/game-mechanics/headquarters-hq.md).

# Headquarters (HQ)

## Rules of Engagement

1. **Main Base Limitations**: Each side is allowed a maximum of one main base.
2. **HQ Regulations**:
   * The HQ is a designated NO COMBAT zone.
   * Attacking or attempting to capture the HQ is strictly prohibited.
   * **Minimum HQ Requirements**:
     * Clearly marked boundaries.
     * A command tent.
     * A designated medical point for respawning.
     * A specified entrance gate.
   * Additional structures and items may be added at the HQ.
3. **Infiltration and Intelligence**:
   * Infiltrating the enemy HQ for intelligence gathering is permitted.
   * The infiltrating unit must consist of no more than three individuals.
4. **Prohibited Actions**:
   * Destruction of enemy HQ equipment is not allowed under any circumstances.


---

# 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://combat-alert-scorpion.gitbook.io/combat-alert-scorpion-docs/rules/game-mechanics/headquarters-hq.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.