Editorial standards

Official sources first

Core specifications come from official manufacturer sources only — spec pages, manuals and PDFs, datasheets, and support docs. Retailer and marketplace listings are never canonical for current products. Where a field is not officially documented, it is stored as a null and said plainly, never filled from a weaker source.

Field-level provenance

Every core field carries its own provenance: the normalized value, the exact raw claim text it came from, the official source URL and type, the date checked, and a confidence grade. Conflicts between official sources are preserved and surfaced, not silently resolved. This is visible on entity pages and included in the JSON exports.

Honest nulls and anti-hype

• No guessing. Unknown specs are null, not inferred.
• No marketing inflation. Boost/surge modes never count as continuous output; partial-recharge claims never become full-recharge times; "up to" figures are treated as maxima.
• No unsupported real-world claims. No runtime hours, "days off-grid", or air-conditioner support without a stated load and assumption basis.
• Safety fields are stricter still. Generator CO-shutdown status is never inferred; ambiguous safety documentation blocks publication.

Cross-category honesty

Use-case guides compare product families (battery, generator, solar) on shared user-facing axes only — indoor safety, fumes, noise, output, runtime model, setup. They never merge the categories into one fake spec table, never equate watt-hours with gallons, and never hide a major tradeoff for a cleaner ranking. Recommendations are grouped by category with an explicit tradeoff summary, and the visible HTML always matches the machine-readable JSON.

Merchant independence

The index is merchant-agnostic. Product entities may link to merchants, and some outbound links may eventually be affiliate links (marked rel="sponsored"), but merchant relationships have no input into specifications, rankings, verdicts, or ordering. Data and monetization are separate layers by design.

Corrections and freshness

Incorrect data is a defect. When an error is found, the entity is corrected and its updated_at date advances. Every entity shows a last-updated date on the page and in its machine summary, and the sitemap carries per-URL lastmod values.