Choose the route that matches the evidence
| Route | Use it for |
|---|---|
| Correction | An exact RCI field, value or sentence that conflicts with stronger evidence. |
| New component | A precise manufacturer, model, order code or hardware revision not yet represented. |
| Source recommendation | A primary, independent, standards, regulatory or licensed dataset channel worth monitoring. |
| Version or lifecycle update | A datasheet, firmware, SDK, PCN, EOL or successor change with a dated upstream record. |
| Independent test evidence | A reproducible measurement with exact hardware, conditions, raw data and analysis boundary. |
| Compatibility evidence | A version-bound vision, LiDAR, compute, battery, actuator or interface integration result. |
| Rights clarification | Reuse, quotation, attribution, embargo or takedown terms from an authorized rights holder. |
Download JSON submission template ↓
Pin the exact identity before stating a value
Supply the manufacturer, official model, order code or variant, hardware revision, firmware and software version, region and lifecycle state where they matter. For an existing RCI record, include the public page URL and claim ID. A family name cannot silently stand in for every member of that family.
A result needs a reproducible boundary
For measured or compatibility evidence, identify the exact devices, serial-to-role mapping, firmware and software manifest, wiring revision, instruments and calibration, protocol, predeclared thresholds, operating conditions, raw data, analysis code, exclusions and failed runs. A screenshot, successful demo or vendor email alone is not independent validation.
Share only material that may be reviewed
- Prefer public upstream links over attachments.
- State the license, quotation permission, attribution and any embargo or restriction.
- Do not send trade secrets, credentials, export-controlled material or unnecessary personal data.
- Disclose your relationship, affiliation and financial or commercial interest in the subject.
- RCI will not treat a submission as permission to republish an entire document or dataset.
RCI verifies before changing the record
- We acknowledge and triage the package.
- We resolve the exact identity, source revision and rights boundary.
- We compare it with upstream and conflicting evidence already in the record.
- We assign the evidence state independently; vendor-supplied material remains manufacturer evidence unless separately verified.
- A material accepted change updates the affected page or data release and receives a dated public change-log entry. Rejected or incomplete material does not silently alter the database.
Payment, product access or submission volume cannot purchase inclusion, ranking, evidence status or a favorable conclusion. Submitters do not receive editorial approval rights.
Corrections do not make history disappear
| Label | Use |
|---|---|
| Clarification | Wording improved; finding unchanged. |
| Correction | A factual field or conclusion changed. |
| Superseded | A newer revision replaces a formerly valid record. |
| Retraction | The evidence no longer supports publication. |
Send the structured package
Complete the JSON template or mirror the same fields in plain text. Link large public files and datasets instead of attaching confidential material.
For a hosted bench test, independently operated replication or applicable accredited-laboratory project, first review the testing partner program and its publication boundaries.
Submission does not guarantee publication or a reply beyond operational acknowledgement. Do not include material that RCI is not authorized to review.