> 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/grey-ocean-local.md). # Grey Ocean – Local ## **Description** The shallowest and the smallest ocean undergoing cyclical transformations. ## **Features** Low evaporation, large freshwater inflow with a limited connection to the other oceans. Coastal villages are a lower form of port cities enabling the minimum of trading and also rest during changing conditions. Affected by environmental changes, players often trade during the appropriate season (defrosting to reach new islands or freezing to stay in temporary trade zones) Ships can get trapped or crushed by ice due to icebergs formation. ## **Typical behaviour** It does not favour transit or trade but opens local potential It's easy to start in the grey ocean as a company, but it's extremely difficult to acclimatize to an entry to the other oceans. Self-sufficient players also do best here especially when they understand their customers' needs and preferences. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://multi-ocean-strategy.designcriticalthinking.com/oceans/grey-ocean-local.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.