Editorial Standard

Purpose before traffic

Every page must solve a distinct user problem, explain an important concept, or provide a validated tool. We do not create one page per keyword, publish placeholder articles, add automatic FAQ sections, or stretch material to an arbitrary word count.

Sources

We prefer applicable manufacturer manuals, official technical documentation, standards, datasheets, primary engineering references, and safety guidance. Established technical education and reputable specialist material can provide context and corroboration. Forums, videos, and community discussions are useful for discovering real vocabulary and failure patterns, but not as sole evidence for consequential instructions.

Originality and quotations

Sources are used to verify claims, not as prose templates. Drafts must use an original structure, explanation, and examples rather than copying or lightly rewriting source or competitor material. Necessary direct quotations must be clearly marked, cited beside the quotation, and no longer than 25 words.

Every ready article requires a hash-bound originality review. The build also checks the local corpus for repeated prose, long matching sequences, excessive article similarity, and overlong quotations. This complements—but does not pretend to replace—editorial comparison against cited sources and representative search results.

Confidence and uncertainty

Claims are distinguished as confirmed, variable, expert practice, needing validation, or controversial. Vehicle-, product-, configuration-, and environment-dependent behavior must not be written as a universal engineering fact. Unresolved important claims do not enter approved copy.

Technical risk

• Low risk: basic definitions and non-actionable background.
• Medium risk: technical explanations and general compatibility concepts.
• High risk: electrical loads, wiring, protection, conductor sizing, grounding, energized testing, vehicle systems, and instructions that could cause damage or harm.

Low-risk material may publish after its sourcing and validation checks pass. Medium-risk material additionally requires adversarial review. High-risk material requires claim-level evidence, at least two applicable Tier 1 sources from independent publishers, deterministic testing where applicable, programmatic technical diagrams, explicit assumptions and exclusions, and a visible safety/limitations notice. A failed or unresolved requirement blocks publication.

No qualified human technical reviewer is currently available. Review records state that accurately; AI/source review is never presented as human or expert approval. The notice clarifies proper use but does not repair unsupported or unsafe content.

Calculations and diagrams

When code can reproduce a result, code—not prose confidence—must do the work. Technical wiring diagrams should be generated from validated structured data so the topology, labels, calculated nominal load, explanatory text, and visual remain consistent. Generative imagery is never evidence for a wiring connection.

Corrections and updates

Substantive corrections are logged publicly. Review and modification dates change only when meaningful work occurred; they are not cosmetic freshness signals.