> For the complete documentation index, see [llms.txt](https://rifle-optics-notes.gitbook.io/rifle-optics-notes-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rifle-optics-notes.gitbook.io/rifle-optics-notes-docs/readme.md).

# Picking a Red Dot for Your AR

General notes on choosing and setting up a red dot on an AR-pattern rifle.

Start with the dot size. A larger dot, measured in MOA, is quicker to pick up at close range, while a smaller dot covers less of the target and suits more precise shots at distance. Many shooters find a mid-sized dot a sensible all-round choice, and a brightness control that goes low enough for dim light is worth having.

Plan for co-witness with your backup irons. If you run flip-up iron sights, mount the optic at a height where the irons line up with the dot when raised, either in the lower part of the window or centered, so you have a usable fallback if the optic fails.

Mount it solidly on the upper receiver rail, tighten the screws to the maker's spec, and zero it at the range before relying on it. As one option, the Ozark Armament Rhino is sold for this use; see the Rhino [red dot sight](https://www.amazon.com/Ozark-Armament-Rhino-Red-Sight/dp/B010OMQSR2/).

If you would rather start with a folding set, see these [Ozark flip-up backup sights](https://www.amazon.com/Armament-Backup-Sights-Sporting-Accessories/dp/B01AISP1KW/)

## Optics and irons from one brand

Readers who pair a red dot with backup irons may want both from the same maker. The [Ozark optics and iron sights](https://www.amazon.com/stores/OzarkArmament/page/F4ECA59D-BCDD-42CC-A31F-BFEC5922609F) lists sights for that kind of combination.


---

# 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://rifle-optics-notes.gitbook.io/rifle-optics-notes-docs/readme.md?ask=<question>&goal=<user_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.
