> 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/environment/atmospherics.md). # Atmospherics The Atmospherics system (atmos). Gasses must be able to be transferred through a complex network of pipes, and must regulate pressure between rooms. For example, if a low pressure room is adjacent to a high pressure room, and the door between them is open, **air should flow from the high pressure room into the low pressure room, until pressure is equalized**. Ideally, this should cause wind that, if strong enough, should blow anything not buckled down in the direction of the airflow.

First steps for good atmos are progressing. The cubes' height indicate pressure level.

The gas in the atmosphere may not be a singular gas, actually that will rarely be the case. Most atmosphere will be made up of a mix of gases. Gases naturally mix together and equalize over time, much in the way pressure equalizes overtime.

A representation of a mixture of gasses. The higher the box of a certain color, the more of the according gas is in that tile.

It is important to manage both the pressure and gas mixture of the atmosphere in your work station. --- # 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://ss3d.gitbook.io/design/environment/atmospherics.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.