Otodunyam DTC Application Research Layer V2

Overview

This layer cleans candidate application-specific DTC content for exact duplication, identifier collision and template cloning.

Canonical heading count is not treated as raw record count. Distinct root-cause variants under the same application and code are retained while exact and semantic repeats are reported separately.

It is not an OEM service database. Exact part numbers, thresholds, pins and manufacturer-internal code mappings require physical service evidence before publication.

In the research files are protected from the public web root; only source-honest general diagnostic methods become editorial guides.

The goal is not artificial page growth, but correct merging into technical families and a verifiable publication queue.

Identity and Key Facts

Mapped source rows

1,839

Canonical DTC headings

1,420

Meaningful diagnostic variants

1,470

Technical modules

50

Licence / source status

Internal compilation; not a replacement for OEM service information

Cleaning principles

• Identifier collision repair
• Byte and normalised exact-duplicate checks
• Application + DTC variant merging
• Template and brand-swap clone detection
• Keeping unsupported exact values out of publication

Publication gate

• General engineering methods may publish after editorial review.
• Application-specific exact values require manufacturer or authorised evidence.
• Weak records remain noindex/research.
• A new page opens only for a distinct search intent and technical scope.

Check and Verification Sequence

• Place each new batch in a separate intake pool.
• Run global exact and semantic duplicate checks.
• Identify the application/DTC family.
• Assign source grade and publication state.
• Keep unsupported exact values in the research layer.
• Add only quality-cleared content to the sitemap.

Technical Sources and Verification

1. AutoAtlas technical source and verification policy