> For the complete documentation index, see [llms.txt](https://rocketry.gitbook.io/public/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rocketry.gitbook.io/public/join/intro-projects/documentation.md). # Operations The Operations intro project will reflect what a member of operations should expect to do. It consists of three sections: documentation, safety, and logistics; and should take under two hours to complete. If any of the project is confusing or ambiguous, please reach out to Rocklin (Ops Lead) on discord. ### Documentation Complete Overleaf’s 30 minute LaTeX tutorial: ### Safety Fill in a risk assessment matrix for something hazardous that we work with. Examples: fiberglass, power tools, black powder, cryogens. Include the following: * Risks: hazardous material handling, transportation and storage procedures of propellants, and any other aspects of the design which pose potential hazards to operating personnel. * Mitigation approach: – by process and/or design – shall be defined for each hazard identified. ### Logistics Plan out a club launch event at a nearby Tripoli/NAR prefecture. Note: This will take place on a single day. Provide times and locations for departing, arriving and returning, important contacts on the team and of those managing the site, and a basic packing list --- # 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://rocketry.gitbook.io/public/join/intro-projects/documentation.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.