Editorial standards.

Last updated 2026-05-11 Source-anchored Engineer-reviewed Corrections within 48h

Every page on MetricMech is grounded in a published engineering standard, reviewed by a working engineer before publication, and updated when the underlying standard changes. This page documents the editorial process, source policy, AI disclosure, and corrections workflow.

Source policy

Every claim on MetricMech that is verifiable against a published standard is cited to that standard, by version. The site does not invent values, paraphrase from unverified secondary sources, or carry forward outdated material.

Primary sources the site relies on:

DomainAuthoritative sourceVersion cited
GD&T symbols and tolerance zonesASME Y14.5 (US) and ISO 1101 (international)Y14.5-2018, ISO 1101:2017
Fits and limitsISO 286-1 / 286-2ISO 286-1:2010, ISO 286-2:2010
General tolerancesISO 2768ISO 2768-1:1989, ISO 2768-2:1989
Aerospace First Article InspectionAS9102 Rev CAS9102C:2024
Aerospace quality managementAS9100DAS9100D:2016
Automotive PPAPAIAG PPAP 4th EditionPPAP 4th Edition:2006
Automotive quality managementIATF 16949IATF 16949:2016
Medical-device quality managementISO 13485ISO 13485:2016
Surface finish parametersISO 4287 / ISO 21920ISO 21920-2:2021
Statistical process controlAIAG SPC, ISO 22514AIAG SPC 2nd Edition:2005
Measurement systems analysisAIAG MSAAIAG MSA 4th Edition:2010
Material weights and propertiesASTM, Indian Standards (IS), and supplier datasheetsCited per-page

Review process

Every page goes through four stages before publication:

  1. Source anchoring. The author maps the topic to one or more primary sources from the table above. Pages that cannot be anchored to a published standard are not published.
  2. Drafting. First draft is produced by an engineer or AI-assisted with an engineer in the loop. Formulas, worked examples, and tolerance ranges are verified against the source standard before the draft moves forward.
  3. Technical review. A working QA, production, or aerospace engineer reviews the page for technical accuracy, real-world relevance, and clarity. Reviewer comments are addressed before publication.
  4. Publish with metadata. The page is published with the author byline, publication date, last-modified date, and the standards referenced. Schema.org metadata is added so the authorship is machine-readable.

AI disclosure

MetricMech uses AI assistance during the drafting phase. The site discloses this openly because the alternative — pretending the content is hand-typed when it is not — is dishonest, and because Google's helpful-content policies require disclosure when AI is the primary creator.

What this means in practice:

Corrections policy

48-hour correction window Confirmed calculation errors, outdated standards references, or factually wrong claims are corrected within 48 hours of a verified report. The corrected page is re-dated and a note is added to the bottom of the page recording what was changed and when.

To report an error: file a GitHub issue with the page URL and what you observed. Public issue tracking is intentional — it lets every reader see what has been challenged, what has been corrected, and what is still in dispute.

Update cadence

Pages are revisited on three triggers:

Citation and attribution

MetricMech content may be quoted and embedded with attribution. Specifically:

Conflicts of interest

MetricMech is funded by CadNexa. This is disclosed in the site footer, the about page, and throughout the article CTAs. CadNexa references appear in editorial content when the topic is directly related to a CadNexa capability (e.g. ballooning automation, browser-based 3D viewing, FAI report generation). Editorial content is not influenced by CadNexa's marketing priorities — the calculator outputs, standards explanations, and pass/fail logic are determined by the source standards, not by what CadNexa sells.

Reviewers and contributors who work for organizations whose products are mentioned on MetricMech will disclose that affiliation in their byline.

What we don't do

How to flag a concern

The fastest path is a GitHub issue. For non-technical concerns (sponsorship questions, press inquiries, partnership proposals), use the contact page.