31 profiles, 1,730 normalized records, 20 exact links.

The direct answer

What is now public? The Robot System Index at data version 0.8.21: 31 robot platform and configuration profiles across five morphologies, carrying 1,730 normalized responsibility-party records, 30 commit-addressable BOM surfaces, 12 manufacturer relations, 20 exact row-level Robot→Component relations, 21 lifecycle and configuration relations, and an interface topology of 168 nodes and 159 source-supported relations across 28 profiles.

What is it? A structured index of what each platform's responsibility party published at a selected source and revision. Every normalized record preserves the publication surface, revision pin, quantity boundary and unresolved items. Where a source is a repository, the profile pins a specific commit rather than a mutable default branch.

What is it not? It is not an as-built inventory, a compatibility guarantee or a test result. Physically validated interface relations: 0. Complete independent rebuild evidence packages: 0. In the dataset's own words: a public BOM "does not independently prove current availability, qualified substitutions, safe wiring, regulatory suitability, performance, a unit-level as-built configuration or successful independent replication."

Five morphologies, 31 profiles

The index reaches all five target morphologies. Profile counts describe published configuration profiles, not distinct chassis: closely related configurations—such as the ToddlerBot actuator variants or the LeKiwi power variants—are separate profiles because their responsibility-party sources publish separate boundaries.

Of the 31 profiles, 30 expose a commit-addressable BOM surface: the selected parts list, requirements file or engineering inventory can be re-fetched at the exact pinned revision. The interface topology covers 28 of the 31 profiles; the remaining three profiles publish normalized records without a topology map.

What the 20 exact relations mean

An exact Robot→Component relation is the strictest link in the index: one pinned responsibility-party BOM row crosswalked to one exact-model record in the RCI component catalog. Each relation preserves the published part number, the published quantity, the source revision and an explicit evidence boundary. The TurtleBot3 Waffle Pi profile, for example, links its pinned parts-list rows for DYNAMIXEL XM430-W210-T (published quantity 2) and OpenCR1.0 (published quantity 1) at a fixed ROBOTIS e-Manual commit.

Ten of the 31 profiles carry at least one exact relation. The other 21 profiles publish normalized records without exact crosswalks because their BOM rows do not yet meet the identity bar: a row must publish an exact model or order code that matches a versioned catalog record, not a family name, a category label or a filename.

A relation proves shared identity between two published records. It does not prove installed serials, current supply, firmware state, electrical compatibility, endorsement or any RCI hardware test—each relation record carries that boundary in its own text.

What was deliberately rejected

The exact-relation count is 20 partly because automated candidates were refused. Four rejection classes are preserved in the crosswalk audit trail:

• Substring false positives. A Solo12 bearing row reading "ET2520 2Z VA" superficially matches HEBI's T25-20, and a reBot repository file named "D435_Gemini2_Mount.step" superficially matches Orbbec's Gemini 2. Both were rejected: string overlap is not identity, and a mounting-plate filename proves only that an optional mechanical surface exists in the repository—not that any sensor is installed, compatible or powered. A validator now blocks both from future promotion.
• Probable identity. The OpenAMR source describes its lidar as a probable RPLIDAR A1M8 with the unit label unconfirmed. The A1M8 catalog record is publishable on its own, but no exact edge is created from a "probable" declaration.
• Unsplit variant families. Among the crosswalk-candidate rows alone, STS3215 appears in three distinct boundaries—7.4 V/1:345/C001, 12 V/1:345 and 5 V/1:147—and further variants exist elsewhere in the index. A shared family name does not license a shared edge; versioned identities must be established before any of these rows can link.
• Version layers. Solo12 v1 and v1.1 remain separate version layers rather than one merged, versionless parts package.

The same conservatism applies to the 21 lifecycle relations: 7 standard configuration changes, 5 version upgrades, 3 revision separations, 3 replacements, 2 end-of-life discontinuations and 1 regional procurement boundary—each as declared by the responsible sources, not as observed product status.

Method and limits

Every count above is recomputed from the published v0.8.21 dataset, not quoted from working notes. Highest completed work level: EV3 public-data recomputation. RCI verified source identity and revisions, audited the pinned artifacts and recomputed structural aggregates from the identified public sources. No level-EV4, EV5 or EV6 work exists for this index.

• Physically validated interface relations: 0. All 159 interface relations restate endpoint claims supported by the responsibility party's own documents at a pinned revision. None has been checked with instruments on a physical unit.
• Complete independent rebuild evidence packages: 0. No profile has been independently rebuilt, powered or measured by RCI or a named external party.
• Recommendation rows and mutable documents are not as-built facts. A recommended compute module, a default configuration file or a wiki page describes a configuration intent at a point in time; the index preserves it as such.
• Quantities are configuration declarations. A published quantity applies to the source's stated BOM boundary (often one robot) and is never converted into an inspected inventory.

This separation follows the contract set out in RCI 001: source quality and claim status answer different questions. A pinned responsibility-party BOM can be an authentic, current, first-party source and still describe only what that party declared. The index therefore records the declaration, its location and its revision—and stops there. The 12 manufacturer relations follow the same rule: each records that a responsibility-party BOM mentions a manufacturer and links the profile to that manufacturer's RCI page, and it implies no partnership, supply agreement or endorsement in either direction.

Download the data

The full index is served as robots.json with flat exports for each layer: profile-level CSV, normalized BOM records, exact component relations, interface relations and lifecycle relations. Browse the profiles at the Robot System Index landing page.

Each export embeds its own rights notice and completeness boundary. RCI publishes source mapping, counts, disclosure states and editorial findings; it does not redistribute third parties' full BOM rows, CAD, images, marks or retailer data.

For version-aware BibTeX and machine citation records, use Cite RCI.