Claims need support
We prefer primary documentation, original research and direct product checks. We distinguish verified facts from interpretation and do not present generated prose as evidence.
Trust and transparency
Useful tools need honest explanations. This policy describes how we publish factual pages, product guides and research summaries—and how to tell us when something is wrong.
We prefer primary documentation, original research and direct product checks. We distinguish verified facts from interpretation and do not present generated prose as evidence.
AI may assist with drafting or organization, but a named human reviewer remains responsible for published claims, links, limitations and corrections.
A dateModified value should change only after a substantive content review. A rebuild or deployment alone is not an editorial update.
FaddyAI-operated pages identify FaddyAI's role, avoid invented rankings, and state trade-offs. Inclusion does not imply independent endorsement.
State exactly what a page is trying to establish, including the product version, date and audience when relevant.
Use first-party documentation for product behavior and primary research for scientific claims whenever it is available.
Confirm routes, inputs, core actions and public access. A catalog audit is labeled separately from an end-to-end generation test.
Note uncertainty, service dependencies, safety constraints and cases where professional judgment is still required.
Update the reviewed date only when the facts or analysis received a substantive check.