1. Start with the work
We define the outcome, inputs, owner, decision and approval point before recommending a product or capability.
2. Primary sources first
Official documentation, changelogs, API references and product support pages are the basis for capability and policy claims.
3. Explain before implementing
We define unfamiliar terms, show what the product can and cannot do, and describe a safe first test before implementation details.
4. Original, verifiable analysis
We do not republish full documentation. We produce our own explanations, comparisons and decision paths with direct links to relevant sources.
5. AI supports the work, not the claim
AI may help organize, translate and review material. Product claims are still checked against current primary sources before publication.
6. State the bad fit
A useful guide must explain when a tool, connection or automation adds more cost, risk or maintenance than value.
7. Corrections and independence
Commercial relationships do not buy positive coverage. Material corrections and changes are reflected in the content and its review date.