> For the complete documentation index, see [llms.txt](https://docs.eitherway.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eitherway.ai/documentation/ai-companion/safety-model.md). # Safety Model The companion operates with tiered permissions. Low-risk actions, such as formatting, isolated edits, or well-understood changes, can be handled directly. Higher-risk actions, such as anything involving money, production deployment, or destructive changes, pause for approval first. These boundaries are being tuned with a bias toward caution. As a rule, asking too often is a manageable inconvenience. Acting too far without approval is not. This matters because the more useful an AI system becomes, the less acceptable it is for it to behave like a black box or take important actions without the user understanding what is happening. The aim is not to make the system passive. The aim is to make it useful while keeping decision-making where it belongs when risk is involved. The companion should be able to move quickly on safe tasks, slow down when needed, and remain transparent throughout. --- # 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://docs.eitherway.ai/documentation/ai-companion/safety-model.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.