> 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/oceans/red-ocean-established.md). # Red Ocean – Established ## **Description** An active ocean that connects most shallow waters. ## **Features** Highly competitive and transited zone. High-end goods and services are being traded and circulated. The shallow water provides access to rich fishing grounds and abundant resources, but it can make navigation difficult and increase the risk of running aground. Port Cities are numerous, with fewer islands than most oceans. Successful navigation consists in having clear and direct routes. Lighthouses perform a historical, yet important function in providing guidance in zones with unpredictable conditions. ## **Typical behaviour** Rich in monsters (both real and fictitious) and aggressive players who can be merciless if you are small. You may need to be backed by big players to persevere. Clarity and practicality take precedence over visionary thinking. The customers are experienced and exigent. Success in Red Ocean relies heavily on strong and stable partnerships that often increase profitability by joining forces. "Unicorns" are less tolerated than pirates, despite heavy regulations. The most common players: The Buyer and The Protector. Pirates cannot last long in the Red Ocean: With few islands, there are only few places where they can get resources or hide from the navy. They often expose themselves to high risks (monsters) but are able to enjoy moderate gains through quick raids and evasion tactics. --- # 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/oceans/red-ocean-established.md?ask=&goal= ``` `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.