ERRHIVE CARS
Editorial policy
A useful code page must distinguish its reference definition from a diagnosis for an individual vehicle.
Source labels remain visible
Community datasets are described as reference material. We do not label their entries as manufacturer-verified. Manufacturer documents are attributed separately, and their model, year, market and powertrain restrictions remain part of the guidance.
One canonical reference
Shared manufacturer labels can point to one definition page. Alternative spellings and manufacturer associations do not create extra repair articles. Exact-model pages require specific documentation; we do not multiply generic codes across models and years.
No invented repairs
A code alone cannot prove a component failure. We do not generate replacement instructions, repair prices, or supported vehicles from a code label. General preparation steps are identified separately from any source-supported diagnostic instructions.
Corrections and conflicts
When references conflict, the exact vehicle documentation takes priority. Preserve the complete code, source link and vehicle context when reporting a concern. An unresolved definition should not be presented as a universal instruction.