Verified route, exact plan documented
The exact host and optic have a manufacturer-supported path, and every critical component, hardware, warning, and evidence field required by the plan is recorded.
Receipts before certainty
The map shows where the evidence ends.
A useful route system has to distinguish verified directions, incomplete installation detail, documented conflicts, and unanswered questions. This is the standard behind every Optics Intel route—and the process for correcting one.
Report an optic-route problemControlled outcomes
What each route label means
Verified route, details still open
The fit path is supported, but one or more exact installation facts are missing. Missing screw, torque, or clearance data is shown—not copied from a similar product.
Verified route with a model-specific warning
The interfaces connect, but the first-party record identifies a clearance, revision, hardware, or other exact-product condition that must remain visible.
Documented exact-product conflict
A first-party source or safety notice establishes that the nominal interface match is not a supported route for the selected products.
Route not established
The current graph does not have enough exact evidence to answer. Unknown does not mean incompatible, and a shared footprint alone does not create a route.
Evidence hierarchy
What can change the map
- Exact first-party documentationCurrent firearm, slide, plate, optic, or mount documentation that names the applicable model, interface, or part.
- Conservative downgradeA credible unresolved safety or identity problem may move a positive route to unknown, caution, or conflict while research continues.
- Secondary and field reportsRetailer listings, owner reports, photos, and correspondence can prioritize research, but cannot create a positive route by themselves.
Private correction workflow
What happens after you report a problem
Quarantine
The exact route, controlled issue type, severity, source, and your private description enter a non-public queue. Exact duplicates stay private and are counted separately.
Triage
Critical safety or materially wrong-route reports become P0. High-priority issues become P1. Neither priority changes the live answer.
Research
The route is checked against current first-party sources and exact product identity. Ambiguity is preserved rather than filled with a nearby model's facts.
Revision
An accepted change is published only with first-party support or as a conservative downgrade. The before/after outcome, facts, source, reviewer, date, route snapshot, and release record are retained.
Privacy boundary
Your report is not analytics.
Correction reporting works whether analytics consent is accepted or denied. Reporter prose, contact details, sources, and attachment metadata are not sent to route analytics or included in demand summaries.
Contact information is optional and is used only when you explicitly ask for follow-up. Do not submit firearm serial numbers, purchase records, home addresses, or unrelated personal information.
See something wrong?
Send the exact pair and what changed.
The route form carries the controlled platform and optic identities forward. A current manufacturer URL is especially helpful, but a safety concern can be reported without one.
Open the private report formOr email [email protected].