Editorial Standards

Claims that appear on public dossiers should be traceable to a source. Editors prefer corroboration across independent documents when a specification is contested. If evidence is thin, the field stays empty or marked unverified rather than filled with guesswork.

• Manufacturer product pages and datasheets
• Official press releases and technical blogs
• Academic papers and institutional project pages
• Standards and certification documents when applicable

Product identity (name, generation, company) should match the maker’s own naming. Marketing nicknames may appear as aliases, but the canonical title follows official usage where possible.

Research robots and lab platforms should cite the lab, paper, or project page that defines the system. Secondary blogs are supporting context, not the sole basis for hard specs.

Images require provenance. See Image Attribution Policy and Official Media Policy.

RoboDex does not invent payload weights, battery chemistries, or deployment counts to make a card look complete. Hype language from social media is not a specification source.

Empty fields are honest. “Unknown” is preferable to a plausible but unsourced number. Readers should be able to trust silence as much as they trust a filled cell.