> For the complete documentation index, see [llms.txt](https://multi-ocean-strategy.designcriticalthinking.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://multi-ocean-strategy.designcriticalthinking.com/players-behaviours/the-protector-control.md).

# The Protector – Control

## Description

The protector archetype strives in established market/value spaces, and either regulates or enforces norms erected as rules. It is good at deploying and maintaining an existing infrastructure.

## Features

* Partially dependent on infrastructures/partially autonomous: range of action;
* Seek coordination with other established forces;
* Can endure longer-term conflicts;
* Resource & infrastructure specialist;
* Aim at enemy strategic resources: either destroy to confuse or acquire to control;
* Explicit internal rules/procedures/rituals to respond to difficult/unclear situations;
* Specialised crew members;

## Typical behaviour

* Rely on the known
* Uses existing or creates new governing constraints
* Risk minimiser
* Pattern identifier and strategic/tactical planer
* Identify → Acquire → Secure
* In high-conflict with pirates

## Affinity

* Ocean: Red and Grey Oceans
* Players: Buyer, Seeker
* Monsters: Greed, Fear, Obsession


---

# 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://multi-ocean-strategy.designcriticalthinking.com/players-behaviours/the-protector-control.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.