1. Start with the exact configuration
A family name is not enough. We identify the model, version, optical state, reducer or flattener, camera variant, and measurement reference plane whenever those details affect the answer. A value for one generation or native configuration is not silently reused for another.
2. Prefer sources closest to the specification
Current manufacturer manuals, technical drawings, specification pages, and support documents are the primary source tier for product dimensions and interfaces. A guide links the relevant sources and notes what each source supports. Dealer summaries and community reports can help locate a question, but they do not override an identified primary specification without a documented reason.
3. Keep the evidence chain visible
A useful technical conclusion should let a reader follow four stages: the named input, the formula or comparison, the boundary on the result, and the source for each external specification. Reproducible worked examples show this chain with units rather than presenting an unexplained compatibility score.
- Input — exact configuration, dimensions, units, and reference surface
- Formula — stated arithmetic or comparison that can be repeated
- Boundary — what the result does not establish
- Source — current document supporting each external specification
4. Separate calculation from physical proof
Nominal geometry does not certify corner quality, illumination, thread engagement, focuser stiffness, tracking performance, safety, or a successful purchase. Calculator results are planning aids. Users should confirm current manufacturer documentation, inspect the real mechanical chain, and test the assembled system.
5. Date and correct the record
A guide’s “references reviewed” date means its cited specifications and published arithmetic were checked on that date. It is not a claim that every product remains unchanged afterward. Material corrections update the affected copy and review record; reports can be sent through the corrections process.
Privacy by design
Core equipment and observation inputs are calculated in the browser. They are not uploaded for calculator analysis. Standard web infrastructure may still process ordinary request data; the Privacy Policy describes the applicable scope and user choices.