1 · Define the decision and comparison boundary
Each dataset begins with a fixed user question, included component class, excluded variants and minimum evidence fields. RCI does not expand the boundary mid-comparison to accommodate whichever products have cleaner marketing data.
2 · Establish a stable component identity
A record requires a manufacturer, model or orderable identifier, variant boundary and a traceable first-party source. Family-level claims are not silently assigned to every variant. Revisions, regions and discontinued models remain distinguishable.
3 · Preserve the source claim
RCI stores the reported value, original unit, wording, test condition, source URL, document title or revision, source location and last-verified date before any normalization. A screenshot or cached document may support an audit, but the public citation points to the lawful upstream source whenever possible.
4 · Normalize without deleting context
Units may be converted only through a documented, reversible transformation. Values with materially different test conditions remain separate. When a definition is unclear, the value stays unnormalized and the missing condition is published.
Peak and continuous ratings, precision-specific compute, range under different reflectivity, and cycle life under different depth-of-discharge assumptions are not collapsed into one field.
5 · Assign evidence at claim level
| Code | State | Operational meaning |
|---|---|---|
| V | Independently verified | Supported by independent testing, a disclosed deployed BOM, or another qualified external record. |
| M | Manufacturer claimed | Directly stated by the manufacturer; useful primary evidence, but not independent verification. |
| D | RCI derived | Calculated or normalized by RCI with the source values, units and method preserved. |
| C | Conflicting | Credible sources disagree. The conflict remains visible until evidence resolves it. |
| U | Unknown | No adequate public evidence. Unknown is a valid result, not a blank to fill with inference. |
The state describes the claim, not the prestige of the source. A value can change state as stronger evidence appears. Prior evidence remains in the change history.
6 · Pass a publication gate
Reference records require stable identity, upstream citation, last-verified date and visible evidence state. Comparative outputs additionally require compatible definitions and conditions. Research articles distinguish reported facts, RCI analysis and inference.
7 · Recheck, supersede and correct
High-volatility product pages and software support records are checked more often than stable standards metadata. Material corrections identify what changed, why, when and which downstream pages or files were affected. See the corrections process and public change log.