> For the complete documentation index, see [llms.txt](https://docs.optimumsec.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.optimumsec.xyz/deployment/never-deploy-without-review.md).

# Never Deploy Code That Was Not Reviewed Externally

External code reviews are essential because they provide an unbiased, fresh perspective, often uncovering vulnerabilities or flaws that internal teams may overlook due to familiarity with the code.

Third-party auditors bring expertise, diverse experiences, and specialized tools to identify security risks, logical errors, and compliance issues. In the context of smart contracts, where flaws can lead to significant financial losses, relying solely on **internal review is insufficient**.

A rigorous, external review ensures that the code adheres to best practices and industry standards, mitigating the risk of exploits, bugs, or unintended behaviors.


---

# 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.optimumsec.xyz/deployment/never-deploy-without-review.md?ask=<question>&goal=<endgoal>
```

`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.
