Research & Insights / Standards
What we publish. What the evidence supports.
A clear distinction between product explanation, practical guidance, opinion and research.
Research needs more than a label.
A completed study identifies its research question, method, evidence, findings and material limitations. Product evaluations should identify the configuration, sample and comparison conditions.
A protocol describes planned work. A working paper is preliminary. Peer review is stated only when it has occurred. No illustrative result is labelled an observed finding.
Product explanations describe a defined scope.
Distinguish available functionality, configuration requirements, illustrative examples, research and future direction. A screenshot does not prove an outcome it does not show.
Dainin publishes its own product explanations. They are not represented as independent reviews.
Sources and contribution.
Attribute external methods to their sources and Dainin-specific mechanisms to the relevant Dainin documentation. Keep company achievements distinct from personal ones. Publish customer material only with the appropriate permission.
Historical claims distinguish formulation, implementation, demonstration and availability. A publication date or trademark record does not by itself prove invention.
Responsibility and correction.
AI assistance does not remove editorial responsibility to verify claims, protect confidential information and correct mistakes. A meaningful correction should identify what changed and when.
Report a correction through the enquiry route and identify the page and statement concerned. Correction enquiries are distinguished from commercial requests.
Useful guidance, not a guarantee.
A method helps structure a decision; it does not guarantee the result. State material assumptions and explain where the evidence is limited.
Relevant commercial relationships or sponsorship should be disclosed when they affect how a publication is interpreted. Do not manufacture reviewer identities, ratings or independent recognition.
Bring one business question.
Explore the relevant Dainin workflow and the decisions behind it.
Request a demo