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 placeholders, or stretch material to an arbitrary word count.

Sources and originality

We prefer primary documentation, standards, datasheets, engineering references, and established technical education. Discovery sources can reveal vocabulary and failure patterns but are not sole evidence for consequential claims.

Sources verify truth. Drafts must use original wording, structure, examples, and synthesis. Necessary quotations are clearly marked and kept short. Every ready article receives an originality check against sources and the local corpus.

Confidence and risk

Claims are classified as confirmed, variable, expert practice, needs validation, or controversial. Low-risk definitions need basic sourcing. Medium-risk explanations need adversarial review. High-risk calculations, sizing, wiring, protection, and safety instructions need claim-level evidence, independent Tier 1 sources, deterministic checks where possible, explicit scope, and a visible safety notice.

No human review is claimed unless a named human actually reviewed the page. AI/source review is not presented as expert approval.

Calculations and diagrams

When code can reproduce a result, code performs the validation. Technical diagrams are generated from validated structured data so the topology, labels, calculations, and SVG remain consistent. Raster images are editorial context only, never technical evidence.

Corrections and updates

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