Open Spec
Published September 29, 2026 · Updated October 17, 2026 · Current version 0.7.0-draft.5 · Approved prerelease
Open Spec is the versioned template every entry in our catalog follows: it lists which facts a robot or robotics-project entry records and how each fact cites its evidence. It is our working profile format, not a certification, and a researched entry does not mean we have built or tested the project.
An entry's facts fall into five groups:
- Identity: name, summary, upstream links, categories, maintainers, the revision we reviewed, maturity and, for projects, the project type.
- Purpose: what it is for, who it is for, documented use cases and known limitations.
- Setup: the official starting point, setup route, skills, dependencies, host computer and operating systems; for robots, also tools, assembly, calibration, the upstream parts list, replacement parts and documented assembly effort.
- Technical: interfaces; for robots, form, degrees of freedom, actuators, sensors, controller, power and dimensions; for projects, languages, supported hardware, inputs and outputs, formats, installation, published evaluation, workflows, algorithms and compute needs.
- Project health: release and activity dates with their scope, the support route and a dated maintenance assessment.
Around those facts, the format fixes how evidence, source files and licenses, costs, references, dates, categories, review state and discussion are recorded. The tables below describe the whole contract. Field names used by the validator are listed on the versioned contract page.
Which projects qualify?
The catalog selection guide explains merit-based review for hardware, software, models and datasets: a concrete robotics contribution, inspectable artifacts, useful next steps, distinct identity and an honest account of rights and limitations. Stars and popularity do not determine eligibility. The guide uses the existing scope and evidence fields; it does not change this record format or automatically reassess earlier entries.
Entry fields
Required fields must be established before an entry is ready for review. Optional fields can stay unknown, and an unknown value is shown as unknown rather than filled with a default. Robot entries also cover end effectors (grippers, robotic hands, extrusion and dispensing tools, other process tools and tool changers) and standalone hardware components such as motor controllers, sensors and wearable devices. A component entry says that it is a component, not a complete robot.
Identity
| Field | Applies to | Type | Review | What it records |
|---|---|---|---|---|
| Name | Robots, projects | Text | Required | The upstream project's name. |
| Short summary | Robots, projects | Text | Required | A one-paragraph description used on index cards. |
| Primary upstream URL | Robots, projects | Link | Required | The project's official home. |
| Categories | Robots, projects | List | Required | The primary category first, then up to two secondary categories from the controlled vocabulary. |
| Maintainers / organization | Robots, projects | List | Optional | Who maintains the project, as established from sources. |
| Repository | Robots, projects | Link | Optional | The source repository. |
| Documentation | Robots, projects | Link | Optional | The official documentation. |
| Revision covered | Robots, projects | Text | Required | The release tag, dated commit or described snapshot the entry was researched against. |
| Maturity | Robots, projects | Text | Required | The development stage as described by the project or assessed by us. |
| Project type | Projects | Text | Required | Framework, library, middleware, tool, model, dataset or simulation; it must agree with the primary category. |
Purpose
| Field | Applies to | Type | Review | What it records |
|---|---|---|---|---|
| Purpose | Robots, projects | Text | Required | What the robot or project is for. |
| Intended audience | Robots, projects | List | Required | Who it is meant for, such as researchers, educators or hobbyists. |
| Use cases | Robots, projects | List | Optional | Documented tasks or applications. |
| Known limitations | Robots, projects | List | Optional | Documented constraints and failure conditions. |
Setup
| Field | Applies to | Type | Review | What it records |
|---|---|---|---|---|
| Getting started | Robots, projects | Link | Optional | The official starting point. |
| Setup route | Robots, projects | List | Optional | A concise sequence of steps to a first result. |
| Required skills | Robots, projects | List | Optional | Skills the setup assumes. |
| Dependencies | Robots, projects | List | Optional | Software or hardware the project depends on. |
| Host / compute requirements | Robots, projects | Text | Optional | The computer or accelerator needed. |
| Supported operating systems | Robots, projects | List | Optional | Documented operating-system support. |
| Build tools | Robots | List | Optional | Tools needed for assembly. |
| Assembly / fabrication | Robots | Text | Optional | How parts are made and put together, including printing. |
| Calibration | Robots | Text | Optional | Calibration steps after assembly. |
| Upstream bill of materials | Robots | Link | Optional | The project's own parts list. |
| Replacement parts and repairability | Robots | Text | Optional | How parts can be replaced or repaired. |
| Documented assembly effort | Robots | Text | Optional | Build time stated upstream; not our measurement. |
Technical
| Field | Applies to | Type | Review | What it records |
|---|---|---|---|---|
| Interfaces / protocols | Robots, projects | List | Optional | Communication interfaces, APIs or protocols. |
| Robot form | Robots | Text | Optional | Arm, rover, humanoid, quadruped, gripper and similar. |
| Degrees of freedom | Robots | Number | Optional | The count of controllable joints or axes. |
| Actuators | Robots | List | Optional | Motors and drives. |
| Sensors | Robots | List | Optional | Built-in sensors. |
| Controller | Robots | Text | Optional | The control board or onboard computer. |
| Power requirements | Robots | Text | Optional | Supply voltage or battery. |
| Dimensions and configuration | Robots | Text | Optional | Size, reach and weight, with the configuration they describe. |
| Languages / runtimes | Projects | List | Optional | Programming languages and runtimes. |
| Supported hardware | Projects | List | Optional | Robots and devices with documented support. |
| Inputs and outputs | Projects | Text | Optional | What the project consumes and produces. |
| Model / dataset / file formats | Projects | List | Optional | Formats it reads or writes. |
| Installation | Projects | Text | Optional | The supported installation route. |
| Published evaluation and its conditions | Projects | Text | Optional | Upstream results together with their test conditions. |
| Supported workflows | Projects | List | Optional | Control, teleoperation, data collection, training, evaluation, deployment or simulation. |
| Supported algorithms / models | Projects | List | Optional | Algorithms or model families the project supports. |
| CPU / GPU / memory / storage requirements | Projects | List | Optional | Compute needed for a stated workload. |
Project health
| Field | Applies to | Type | Review | What it records |
|---|---|---|---|---|
| Last relevant release date | Robots, projects | Date | Optional | The date of the relevant published release; a commit date is not substituted. |
| Upstream last updated | Robots, projects | Date | Optional | The latest relevant upstream change we could establish, with its source. |
| Scope of upstream activity date | Robots, projects | Text | Required when an activity date is known | Whether that date describes a software repository, a hardware design, documentation, a mixed repository or something else. |
| Community / support | Robots, projects | Link | Optional | Where users get help. |
| Maintenance assessment | Robots, projects | Text | Optional | A dated editorial assessment; age alone does not mean abandonment. |
Measurements such as payload, reach and speed are recorded as separate metrics, each with a name, numeric value, unit, configuration, conditions and source. Two figures measured under different conditions stay separate and are never averaged.
How each fact is recorded
| Part | Meaning |
|---|---|
| Value | The typed value, or empty when unknown. |
| Status | One of the six evidence statuses below. |
| Sources | The IDs of the references that support the value. |
| Checked | The date the evidence was checked. |
| Notes | Conditions, scope, uncertainty, or the reason a value is conflicting or not applicable. |
| Evidence status | Meaning |
|---|---|
| Reported | A cited source says it. Visiting the source does not make the claim observed. |
| Observed | We performed or inspected the relevant thing and hold local evidence. |
| Inferred | An editorial conclusion, with an explanation and supporting sources. |
| Conflicting | Sources disagree. The value stays empty and the notes describe each alternative with its source. |
| Unknown | Not established. It is shown as unknown, never filled with a guess or a zero. |
| Not applicable | The field does not apply, with a reason. |
| Entry label | Meaning | Status |
|---|---|---|
| Source researched | Cited information was checked against the identified sources. Nothing was run or built. | In use. |
| Setup reproduced | A linked experiment records the exact configuration, the instructions followed, deviations and the result of a named task. | Proposed standard; not assigned by current tooling. |
| Performance tested | A linked test report describes the metric, equipment, conditions, repetitions, outcomes and limitations. | Proposed standard; not assigned by current tooling. |
Source files and licenses
Available files and permission to reuse them are separate questions, so each layer is assessed on its own. A repository's root license does not establish the status of every component.
| Layer | Robots | Projects |
|---|---|---|
| Mechanical design | Assessed | Not assessed |
| Electronics | Assessed | Not assessed |
| Firmware | Assessed | Not assessed |
| Software | Assessed | Assessed |
| Model weights | Assessed | Assessed |
| Datasets | Assessed | Assessed |
| Documentation | Assessed | Assessed |
| Per-layer record | Values |
|---|---|
| Applicability | Unknown, applicable, or not applicable with a reason. |
| Availability | Unknown, available, not found, or unavailable. Not found describes our search, not proof that files do not exist. |
| Artifact link | Where the files are. |
| License and license link | The identifier or text exactly as published; never guessed from a hosting platform. |
| Sources, checked date and notes | The evidence behind the assessment and any restrictions. |
| Inclusion decision | Meaning |
|---|---|
| Unresolved | Openness is not yet established; the entry stays in research. |
| Include as open | Every applicable layer has an available artifact and a cited license. |
| Include as partial | Some layers are open; the gaps are stated. |
| Include as source-available | Files are visible but reuse is restricted; the restrictions are stated. |
| Exclude | Not listed, with a reason. |
The decision is an internal inclusion choice with a written rationale, not a certification or a legal opinion. No openness score is derived from it.
Costs
A cost is an offer or an estimate for a particular configuration, not a property of the whole project. Prices keep their quoted currency, a conversion appears only with a dated conversion source, and a missing price is shown as unknown rather than zero.
| Cost kind | Meaning |
|---|---|
| Vendor price | A specific seller's offer. |
| Parts estimate | The sum of a bill of materials. |
| Measured expenditure | What we actually paid for a build. |
| Robot cost scenario | Meaning |
|---|---|
| Parts only | A do-it-yourself parts list; whether printed parts are included is stated. |
| Kit | A specific vendor kit, naming the components it leaves out. |
| Assembled | An assembled robot, stating calibration and accessory coverage. |
| First working setup | Everything required for a named first task, including peripherals and compute, or equipment explicitly assumed to be owned. |
| Every price records | Meaning |
|---|---|
| Configuration and quantity | The named revision and variant, how many robots or leader arms, and the units priced. |
| Amount or range | A single amount, or a lower and upper bound with the assumptions behind the range. |
| Currency and region | As quoted; prices in different currencies are not compared. |
| Included and excluded | Motors, controllers, structure, cameras, power, cables, host computer and tools, as relevant. |
| Shipping and tax | How delivery and tax were treated; unknown charges stay unknown. |
| Availability | Stock at the time of the check. |
| Checked date | When this quote or estimate was checked. |
| Evidence | The claim status and the sources behind the figure. |
Each robot entry states whether a hardware budget is available or unknown. Available means at least one sourced scenario or priced parts rollup exists, not that every scenario is known. When no defensible estimate exists, the entry reads "Cost not yet established". Project entries may record operating costs for a named workload, with the time basis, hardware assumptions and provider.
Line-level parts and sourcing
Since version 0.7, a robot entry may add a line-level bill of materials priced from a shared parts library of US supplier offers. The headline is a Parts total in US dollars for US delivery, and every price shows its date.
| Concept | Meaning |
|---|---|
| Configuration | A named robot revision or variant with one first task. |
| Part | A technical identity in the shared parts library: exact voltage, gear ratio, dimensions and revision where relevant. |
| Requirement | A configuration's purchased item, printed group, fabrication job, peripheral or tool, with quantity, cost layer, required or optional status and evidence. |
| Offer | One supplier listing for a part, with immutable dated price and stock observations. Price changes never change technical identity. |
| Substitute | An alternative candidate with an explicit compatibility scope and evidence; never an automatic replacement in a total. |
| Ownership scenario | Quantities a reader already owns. The public baseline assumes nothing is owned. |
| Rollup | The derived estimate for one configuration and one ownership scenario. |
| Cost layer | Contents | In the Parts total |
|---|---|---|
| Purchased parts | Motors, controllers, bearings, fasteners and cables specific to the robot. | Yes |
| Printed parts | Material to buy, or the selected print service. | Yes |
| Fabricated parts | CNC, laser-cut or PCB fabrication. | Yes |
| Power and cabling | Power and data components not counted elsewhere. | Yes |
| Host compute | The computer or single-board computer the first task needs. | Shown separately; required unless owned |
| Sensors and camera | Sensors or cameras the first task needs. | Shown separately; required unless owned |
| Tools | One-time tools, and a printer when self-printing. | Shown separately; required unless owned |
| Shipping and tax | A destination- and basket-specific estimate, or unknown. | Shown separately |
| Labor | Build hours. | Never priced |
| Measure | Values | Meaning |
|---|---|---|
| BOM coverage | Complete, partial or unknown | Whether every requirement of the first task is listed. Pricing every listed line does not make a BOM complete. |
| Pricing coverage | Priced groups out of required groups, with named gaps | How much of the required purchase has an eligible price. |
| Setup readiness | Priced, priced with owned items, or incomplete | Whether a first-working-setup budget can be stated. It is budget readiness, not proof that the build works. |
| Pricing rule | Effect |
|---|---|
| Dates, not freshness labels | Every price shows the date it was observed. Rereading a page does not move a published figure's date forward. |
| Eligibility | A price counts only when it is in US dollars, dated, and has a known pack size and minimum order. A listing we checked directly must also have a working link and be in stock, low on stock or of unknown stock. A figure published by the project counts when its source is retained at a pinned revision and no broken link, withdrawal, sold-out or back-order status has been verified for that listing. Ineligible prices stay visible. |
| Upstream versus direct | Once an eligible directly checked price exists for a requirement, the project's published figure for it stays visible but no longer counts. A verified failure of a listing also excludes that listing's earlier prices; an unknown status or a blocked fetch alone does not. |
| Pack arithmetic | Whole packs and minimum orders are charged. Each supplier counts once at its cheapest expenditure, and the range is the lowest to highest expenditure across suppliers. |
| Printed material | Material consumed is reported separately from the spools that must be bought; only the purchase enters the total. |
| Incomplete totals | When any required item is unpriced, the page shows a known parts subtotal with the unresolved requirements named. That subtotal has no upper bound and is not a guaranteed minimum budget. Unknown required shipping or tax keeps setup readiness incomplete. |
| Referral links | Offer URLs carry no affiliate, referral or tracking parameters. We earn nothing from any offer. |
References and credits
Every externally sourced specification, price, compatibility statement, activity date and openness assessment links to its reference beside the claim.
| Reference field | Meaning |
|---|---|
| ID | A stable identifier within the entry, cited next to claims. |
| Type | Upstream, license, paper, maintainer, vendor, secondary reporting or local test. |
| Title and link | The source title and its direct public URL. |
| Publisher | The author or organization when established; otherwise a note that attribution is not established. |
| Locator | The release, commit, file, API field or section used, preferring a revision-specific permalink. |
| Accessed date | When the source was retrieved. Retrieval is distinct from the claim's checked date. |
| Finding | Which information the source supports and any limits on its scope. |
| Retrieval method | Manual, API or local test, with the public endpoint and fetch time when recorded. |
| Asset credit field | Meaning |
|---|---|
| Asset | The reused image, diagram, excerpt or dataset. |
| Creator and source URL | Who made it and where it came from. |
| Rights URL and license or permission | The evidence that reuse is allowed. |
| Credit text | The wording the terms require. |
| Modifications | Any changes we made. |
Asset credits are recorded separately from the project's license assessment. Reuse that cannot be established is replaced with a link or original material.
Dates
| Label | Meaning |
|---|---|
| Upstream last updated | The latest relevant upstream change we could establish, with its source and scope. |
| Latest release | The date of the relevant published release. |
| Profile updated | When we last materially changed the entry's content. |
| Sources last checked | Our latest substantive source review, even if nothing changed. |
| Price checked | When each particular quote or estimate was checked. |
| Next review | When the entry is due for another check. An overdue date stays visible. |
None of these dates moves on its own: a repository check, a formatting edit, a site deployment or a new comment does not refresh them. A substantive source review updates Sources last checked, and an evidenced relevant upstream change updates Upstream last updated.
Categories, tags and relationships
Categories describe what an entry is. Tags describe what it can do and where it fits. Compatibility links need evidence.
| Robot categories | Project categories |
|---|---|
| Robot arms and manipulators | Frameworks |
| Wheeled and tracked robots | Libraries |
| Legged robots | Middleware |
| Humanoids | Tools |
| Aerial robots | Models |
| Marine robots | Datasets |
| Other physical robots | Simulation |
| End effectors: grippers, robotic hands, extrusion and dispensing tools, other process tools, tool changers |
| Tag facet | Terms |
|---|---|
| Capability | Manipulation, navigation, perception, teleoperation, mapping / SLAM, grasping, locomotion, data collection, robot learning, simulation, motion planning, material extrusion, material dispensing, tool changing. |
| Use case | Learning and education, research, prototyping, inspection, logistics, agriculture, assistive applications, entertainment. |
| Ecosystem | ROS 2, ROS 1, LeRobot, Arduino, Raspberry Pi, NVIDIA Jetson, MuJoCo, Gazebo, Isaac Sim. A tag means a documented integration, never probable compatibility. |
| Mechanism | Parallel jaws, adaptive grip, soft grip, vacuum / suction, magnetic pickup, tendon drive, pellet extrusion, filament extrusion, syringe extrusion, pneumatic actuation, tool changing. |
| Platform | Documented cobot interface, delta robot tooling, delta printer tooling, cartesian printer tooling, industrial arm tooling, cable robot tooling. A platform tag requires a documented interface or application and is not certification. |
Each tag records its facet, term, a reported or inferred status, sources, a checked date and notes. An entry carries at most eight tags, and zero is allowed when the evidence is insufficient.
| Relationship | Meaning |
|---|---|
| Uses | The entry depends on another project. |
| Compatible with | A documented, versioned integration. |
| Based on | Derived from another design or project. |
| Fork of | A fork of another project. |
| Successor to | Replaces an earlier project. |
Relationships cite a source and keep the upstream link even when the related project is not yet in the catalog. Suggestions ranked by shared tags are labelled as similar entries, not as compatibility.
Review and change history
| Stage | Meaning |
|---|---|
| Draft | Research in progress; not published. |
| Review ready | Required fields, at least one primary source, valid citations and dates, a completed layer-by-layer openness check, a reasoned inclusion decision, a next review date and a plain-language list of unknowns are in place. |
| Approved | A named reviewer, approval date and decision note are recorded. |
| Published | The entry additionally has a real public URL. |
| Held or archived | Set aside with a reason. |
Each entry also records why it matters, its open unknowns, any commercial disclosures and a dated change history. Automated checks validate structure and completeness. A separate LLM editorial review assesses the wording against an explicit evidence packet, and a human remains accountable for publication; neither establishes source truth.
Discussion
| Part | Values |
|---|---|
| Discussion status | Planned, disabled or enabled. Enabled requires a real public discussion URL. |
| Robot reactions | Useful, Want to build, Built it. |
| Project reactions | Useful, Want to try, Used it. |
| Comment categories | Question, build or usage experience, correction, tip or resource. |
Reactions and comments are reader interest and attributed reader experience. They are not ratings, verification or our testing, and no counts are shown until a service is enabled. A correction is reviewed before it changes a published fact.
Versions
| Version | Approved | What it added | Contract |
|---|---|---|---|
| 0.5.0-draft.1 | September 29, 2026 | First public pilot: configuration-specific costs, activity scope, source attribution and asset credits. | Read 0.5.0-draft.1 |
| 0.6.0-draft.1 | September 30, 2026 | The end-effector category hierarchy and evidenced mechanism and platform tags. | Read 0.6.0-draft.1 |
| 0.7.0-draft.5 | October 4, 2026 | Optional line-level parts and sourcing with dated US prices; the current version. | Read 0.7.0-draft.5 |
We follow semantic versioning. During 0.x development an incompatible change advances the minor version and a compatible correction advances the patch; no stable 1.0.0 exists yet. Entries keep the version they were reviewed under, shown at the bottom of each page, and their archived validators remain supported. A changed price or article does not change the specification.
Read the methodology for how claims are reviewed and the contribution guide to submit a correction or project suggestion. Reader discussion services are not yet enabled.