Who produces the public content?
Public content is produced under the responsibility of Équipe Diagolia. No individual technical reviewer is shown unless a real person is publicly identified for that role.
How is information structured?
Content separates the observed signal, vehicle context, hypotheses, evidence that strengthens or weakens those hypotheses, and checks to consider. A fault-code page starts with a short answer before explaining what the code means and what it cannot establish.
Which categories of sources may be used?
A source is included in structured data only when it is also visible on the page. Explaining this method does not require naming a technical supplier.
- applicable technical documentation and procedures;
- vehicle information and data added to the case;
- similar cases and available field experience;
- relevant and verifiable public resources.
How are information, hypotheses and confirmed causes separated?
Information describes an available element: a fault code, symptom, measurement, observation or documented instruction. A hypothesis is a possible explanation consistent with some or all of those elements. A cause is confirmed only after suitable checks on the vehicle.
A cause appearing often in similar cases is not enough to confirm it on the current vehicle.
Why is vehicle context essential?
The same code can have different causes depending on the vehicle, powertrain, equipment, associated faults, occurrence conditions and previous work. A public page provides a general framework; it cannot replace analysis of the vehicle concerned.
Which review and caution principles are applied?
- do not present a possible cause as certainty;
- do not invent measurements, expected values or confirmed faults;
- state limitations and missing information;
- use sentences that remain clear outside their immediate context;
- keep visible content, dates and structured data consistent.
How is content updated?
The last-updated date changes when a significant content change is made. Generating a sitemap or deploying the site is not, by itself, an editorial update.
Field feedback may lead to clearer wording, a useful pitfall or a better distinction between hypotheses. It is not presented as collective approval of each page.
How can an error be reported?
Errors, ambiguity or outdated information can be reported to hello@diagolia.com. Please include the page URL, the passage to check and, when it can be shared, the source supporting the report.