Editorial policy
Technical claims should be traceable and correctable
This policy applies to Orch8 field guides, comparison pages, and explanatory website content. Product documentation remains the source of truth for supported behavior.
Sources
We prefer official documentation, standards, original research, and reproducible tests for technical claims. Community discussions can reveal real questions and failure patterns, but they are labeled as problem signals rather than proof.
Product claims
A product capability must be supported by current documentation or repository behavior. We avoid unsupported benchmark numbers, customer outcomes, adoption claims, and absolute guarantees.
Comparisons
Comparison criteria should be useful to the reader and applied consistently. Material claims about another product link to that product's official documentation. Pages include a reviewed date and are updated when the evidence changes.
Corrections
Send a correction with the page URL and supporting evidence to hello@orch8.io. We review factual issues, update the page when warranted, and change the modified date for material revisions.
Authorship and assistance
Organizational articles use the Orch8 Engineering byline. Drafting and analysis may use software tools, including AI assistance; published claims are still held to the sourcing and verification rules above.
Verify the technical details
The documentation is the source of truth for current behavior.