Technical source policy
Product statements should identify whether they come from a catalog, a project document, a test record or an independent source.
Source levels
Stronger publication claims require stronger, more specific records.
Supplier-published product information without an attached model-specific report.
A drawing, map or interface file released for a named model and revision.
A result linked to model, configuration, conditions, method and acceptance criteria.
An official registry, readable certificate or third-party source with scope and validity.
Product catalog visuals may be AI-enhanced from supplied product imagery to improve material legibility, lighting, resolution and framing. They preserve the documented equipment category but are not manufacturing drawings, photographs of a delivered unit, dimensional references or performance evidence.
Review the product portfolioMissing evidence is shown as a request or status—not filled with marketing assumptions.
Publication rules
Scope, model, configuration, method, conditions and validity remain attached to the source that supports the statement.
Content standards
Technical writing here is held to the same evidence boundary as the product pages. Each article states what it rests on, and neither the claim nor the date is left for the reader to guess.
What this page does not claim: there is no named individual reviewer, no external editorial board and no third-party fact-checking arrangement. Stating one would be the kind of unsupported claim the rules above exist to prevent.
Corrections
When an underlying product value changes, the related page and document should identify the new source and revision date. Contact the product team with the affected model, page and value.
Report a technical correction