Editorial standards

Evidence before volume

Publication should answer a real technical question. We prefer original papers, standards, source code, datasets and manufacturer documentation for claims about their own products. Secondary sources can provide context; they do not replace a primary source for a consequential numerical claim.

Identify the kind of claim

• Reported result: identify the original study, population, observation window and event definition.
• Manufacturer claim: attribute specifications and performance claims to their source and version.
• Hesela calculation or model: state inputs, units, assumptions, code and limitations.
• Unresolved question: say what is unknown rather than presenting an inference as an established fact.

Different fleets, workloads and failure definitions are not interchangeable. Benchmarks require measured evidence. Simulations and deterministic examples must be labelled; they cannot establish a real device failure rate.

AI-assisted work

Hesela uses AI-assisted research, drafting, coding and validation. AI output is not evidence. Important claims must be checked against identifiable sources, and executable results should include reproducible inputs and checks. Publication under Hesela team does not imply that every page received independent human or external peer review.

Corrections

Use the report link on a publication or email support@hesela.com. Include the URL, disputed statement, proposed correction and supporting source. Do not include private telemetry, credentials or personal data.

We assess reports against the evidence. Substantive corrections should identify what changed and update the editorial date; formatting changes should not make an old result appear new. Where a claim cannot be supported, it should be qualified or removed. Security reports belong at security@hesela.com.

Dates and versions

Publication dates, substantive update dates, source access dates and dataset generation timestamps describe different events. The update index uses recorded editorial dates, not the date a site build ran. Historical revision notes are shown only when recorded; we do not reconstruct missing review histories.

Independence and reuse

Hesela is a knowledge reference, not a vendor endorsement. Relevant relationships should be disclosed if they affect a publication. Sources retain their rights; consult citation and reuse guidance before redistributing material.