Editorial policy

Evidence before claims

I distinguish verified vendor specifications, editorial analysis, and firsthand observations. A genuine review must document the tested version, host, operating system, methodology and limitations. The current guides use official documentation and educational analysis; they do not claim hands-on testing.

How I select products

I select tools to illustrate distinct production needs: transparent dynamics, character, synthesis, modulation and practical free workflows. Order is editorial organization, not a measured performance ranking. I identify free editions, paid upgrades and restrictions separately.

Verification and updates

Product features, availability and licensing are checked against the linked official developer pages. Each new guide records its source-check date. Pricing and compatibility can change; where a fact cannot be established I say so, omit the claim, and direct readers to the developer. Recommendations are reviewed when documentation, products or material reader corrections change.

Publication and corrections

Drafts require human fact-checking and approval. Publication dates reflect actual publication, not draft creation. Material corrections are noted with the date and reason. AI assisted the site implementation, research and article drafting. This assistance does not constitute product testing. Each article identifies its sources and the limits of its evidence.

Commercial independence

I label affiliated products and commercial relationships near relevant links. Commercial relationships must not determine conclusions or manufacture rankings. I publish no star ratings without documented review evidence.