> For the complete documentation index, see [llms.txt](https://www.designreference.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.designreference.xyz/cognitive-tools/universal/managing-people/hanlons-razor.md).
# Hanlon's Razor
Not everyone is out to get you
Hanlon's Razor is a principle that suggests
> Never attribute to malice that which can be adequately explained by stupidity.
In simpler terms, it means that when faced with a situation where someone's actions seem harmful or malicious, it's often more likely that they were simply acting carelessly or without fully understanding the consequences, rather than intentionally trying to cause harm.
This principle encourages us to consider the possibility of human error or misunderstanding before jumping to conclusions about malicious intent.
#### Further Reading
{% embed url="" %}
{% embed url="" %}
{% embed url="" %}
{% embed url="" %}
---
# 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://www.designreference.xyz/cognitive-tools/universal/managing-people/hanlons-razor.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.
