> For the complete documentation index, see [llms.txt](https://carec.gitbook.io/carec-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://carec.gitbook.io/carec-docs/documentation/safety/hazard-analysis.md). # Hazard Analysis ## Initial hazard families * Unintended motion, wrong direction, or excessive speed * Failure to stop, collision, entrapment, tip, or instability * Stair, curb, or drop-off approach * Incorrect mode or command authority * Takeover or emergency-stop failure * Missed obstacle or misleading clear indication * Localization, map, planner-recovery, or oscillation error * Electrical, battery, thermal, cable, or mount fault * Cybersecurity compromise or unsafe update * Privacy exposure or inaccessible/overwhelming alerts ## Hazard record Each entry includes ID, scenario, affected user, mode, severity, likelihood rationale, causes, preventive/detective controls, safe response, recovery, verification, owner, status, and residual-risk decision. Risk controls prioritize inherent design, then protective measures, then warnings and training. A warning alone is not adequate for a preventable motion hazard. --- # 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://carec.gitbook.io/carec-docs/documentation/safety/hazard-analysis.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.