Source hierarchy
Standards, RFCs, official documentation, security advisories, release notes, source repositories, and primary legal texts come first. Community discussions help us discover problems, but they are not used as the only source for technical claims.
Facts, analysis, and uncertainty
We distinguish what a source says from our analysis. Performance claims require a test environment and reproducible method. Composite cases are labeled and never presented as named customers, measured incidents, or invented results.
AI-assisted work
AI may help organize research, compare versions, find gaps, and edit prose. It may not invent sources, customers, benchmarks, vulnerabilities, or safety conclusions. The named author remains responsible for checking factual claims against the cited sources and clearly labeling analysis.
Checks and updates
Each technical page shows when its facts and sources were last checked and when the next check is due. Independent technical review is disclosed only after a named reviewer has completed it. Content known to be unsafe or materially wrong is corrected, marked, redirected, or removed.
Corrections
Substantive corrections update the conclusion, source list, source-check date, and change record as needed. We do not silently alter a technical conclusion to satisfy a sponsor or vendor.
Commercial content
Sponsored or partner-supported work is labeled. Partners may provide access, data, or subject-matter input, but they do not control the final technical conclusion, remove material limitations, or buy rankings.