At OBDAssistant, accuracy is our foundational principle. A diagnostic platform that asserts unverified claims undermines user safety and mechanical trust. Every code definition and diagnostic guide published across our platform is governed by explicit build-time verification gates.
1. Single Source of Truth & Canonical Hierarchy
Definitions across our website and mobile applications consume one unified canonical dataset. In strict priority order, definitions must originate from:
- SAE J2012 / ISO 15031-6: The standardized international automotive diagnostic code specification.
- OEM Manufacturer Service Information: Official service manuals for manufacturer-specific trouble codes (e.g. P1xxx, B1xxx, C1xxx, U1xxx).
- OBDAssistant Verified-Outcome Corpus: First-party confirmed workshop repair records.
Every code record in our database carries a mandatory definition_source metadata field. Where no authoritative source exists, no definition is published.
2. 3-Tier Classification & Indexation Standard
Every trouble code URL is evaluated and assigned to exactly one tier, which strictly dictates page structure and search engine indexation:
Tier A — Corpus-Verified Diagnostic Guide (index, follow)
Requires an authoritative standards-derived definition plus confirmed repair data meeting or exceeding sample size n ≥ 10. Renders empirical cause distributions, visible sample size, diagnostic steps, and verified repair costs.
Tier B — Short Verified Definition Page (index, follow)
Requires an authoritative standards-derived definition with insufficient empirical repair data. Renders exact definition, family-correct system architecture notes, standards citation, and app guidance. No invented symptoms, causes, or cost ranges are permitted.
Tier C — Unverified / Unassigned Code Notice (noindex, follow)
Assigned to any code lacking a verified definition in standard or OEM specifications. The URL remains live with an honest library notice directing users to verified family hubs and live app diagnostics. Excluded from sitemaps and search indexation.
3. Substantive Empirical Thresholds (n ≥ 10)
Diagnostic causes, symptom frequencies, and repair steps are empirical claims. We do not publish fabricated cause rankings. Cause distributions are rendered exclusively when backed by first-party confirmed repair logs with a sample size meeting our minimum threshold (MIN_N = 10), and the exact sample size n is displayed transparently to the reader.
4. Family-Correct Technical Language
Vehicle subsystems operate under distinct physical constraints. Content generation templates enforce family-correct technical language:
- Powertrain (P): Governed by ECM/PCM. Illuminates Check Engine Light (MIL). Emissions and fuel-economy relevant.
- Body (B): Governed by BCM and restraint modules. Does NOT illuminate MIL (illuminates SRS/Airbag or Body warning lamps). Emissions language is strictly prohibited.
- Chassis (C): Governed by ABS/ESC and steering modules. Does NOT illuminate MIL (illuminates ABS/Traction warning lamps). Emissions language is strictly prohibited.
- Network (U): Governed by CAN bus communication protocols across interconnected vehicle modules.
5. Named Author Bylines & Peer Review
A byline is a formal claim of personal editorial review. Named person bylines render exclusively on pages that have been individually reviewed by a named human editor, with reviewed_by and reviewed_date stored in the record metadata. All other pages display organizational authorship by the OBDAssistant Engineering Team.
6. Corrections & Technical Inquiries
If you identify a technical discrepancy or an outdated protocol specification in our library, please contact our engineering team directly at admin@obd2assistant.com.