Open Source RoboticsRobots, software & learning

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:

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

FieldApplies toTypeReviewWhat it records
NameRobots, projectsTextRequiredThe upstream project's name.
Short summaryRobots, projectsTextRequiredA one-paragraph description used on index cards.
Primary upstream URLRobots, projectsLinkRequiredThe project's official home.
CategoriesRobots, projectsListRequiredThe primary category first, then up to two secondary categories from the controlled vocabulary.
Maintainers / organizationRobots, projectsListOptionalWho maintains the project, as established from sources.
RepositoryRobots, projectsLinkOptionalThe source repository.
DocumentationRobots, projectsLinkOptionalThe official documentation.
Revision coveredRobots, projectsTextRequiredThe release tag, dated commit or described snapshot the entry was researched against.
MaturityRobots, projectsTextRequiredThe development stage as described by the project or assessed by us.
Project typeProjectsTextRequiredFramework, library, middleware, tool, model, dataset or simulation; it must agree with the primary category.

Purpose

FieldApplies toTypeReviewWhat it records
PurposeRobots, projectsTextRequiredWhat the robot or project is for.
Intended audienceRobots, projectsListRequiredWho it is meant for, such as researchers, educators or hobbyists.
Use casesRobots, projectsListOptionalDocumented tasks or applications.
Known limitationsRobots, projectsListOptionalDocumented constraints and failure conditions.

Setup

FieldApplies toTypeReviewWhat it records
Getting startedRobots, projectsLinkOptionalThe official starting point.
Setup routeRobots, projectsListOptionalA concise sequence of steps to a first result.
Required skillsRobots, projectsListOptionalSkills the setup assumes.
DependenciesRobots, projectsListOptionalSoftware or hardware the project depends on.
Host / compute requirementsRobots, projectsTextOptionalThe computer or accelerator needed.
Supported operating systemsRobots, projectsListOptionalDocumented operating-system support.
Build toolsRobotsListOptionalTools needed for assembly.
Assembly / fabricationRobotsTextOptionalHow parts are made and put together, including printing.
CalibrationRobotsTextOptionalCalibration steps after assembly.
Upstream bill of materialsRobotsLinkOptionalThe project's own parts list.
Replacement parts and repairabilityRobotsTextOptionalHow parts can be replaced or repaired.
Documented assembly effortRobotsTextOptionalBuild time stated upstream; not our measurement.

Technical

FieldApplies toTypeReviewWhat it records
Interfaces / protocolsRobots, projectsListOptionalCommunication interfaces, APIs or protocols.
Robot formRobotsTextOptionalArm, rover, humanoid, quadruped, gripper and similar.
Degrees of freedomRobotsNumberOptionalThe count of controllable joints or axes.
ActuatorsRobotsListOptionalMotors and drives.
SensorsRobotsListOptionalBuilt-in sensors.
ControllerRobotsTextOptionalThe control board or onboard computer.
Power requirementsRobotsTextOptionalSupply voltage or battery.
Dimensions and configurationRobotsTextOptionalSize, reach and weight, with the configuration they describe.
Languages / runtimesProjectsListOptionalProgramming languages and runtimes.
Supported hardwareProjectsListOptionalRobots and devices with documented support.
Inputs and outputsProjectsTextOptionalWhat the project consumes and produces.
Model / dataset / file formatsProjectsListOptionalFormats it reads or writes.
InstallationProjectsTextOptionalThe supported installation route.
Published evaluation and its conditionsProjectsTextOptionalUpstream results together with their test conditions.
Supported workflowsProjectsListOptionalControl, teleoperation, data collection, training, evaluation, deployment or simulation.
Supported algorithms / modelsProjectsListOptionalAlgorithms or model families the project supports.
CPU / GPU / memory / storage requirementsProjectsListOptionalCompute needed for a stated workload.

Project health

FieldApplies toTypeReviewWhat it records
Last relevant release dateRobots, projectsDateOptionalThe date of the relevant published release; a commit date is not substituted.
Upstream last updatedRobots, projectsDateOptionalThe latest relevant upstream change we could establish, with its source.
Scope of upstream activity dateRobots, projectsTextRequired when an activity date is knownWhether that date describes a software repository, a hardware design, documentation, a mixed repository or something else.
Community / supportRobots, projectsLinkOptionalWhere users get help.
Maintenance assessmentRobots, projectsTextOptionalA 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

PartMeaning
ValueThe typed value, or empty when unknown.
StatusOne of the six evidence statuses below.
SourcesThe IDs of the references that support the value.
CheckedThe date the evidence was checked.
NotesConditions, scope, uncertainty, or the reason a value is conflicting or not applicable.
Evidence statusMeaning
ReportedA cited source says it. Visiting the source does not make the claim observed.
ObservedWe performed or inspected the relevant thing and hold local evidence.
InferredAn editorial conclusion, with an explanation and supporting sources.
ConflictingSources disagree. The value stays empty and the notes describe each alternative with its source.
UnknownNot established. It is shown as unknown, never filled with a guess or a zero.
Not applicableThe field does not apply, with a reason.
Entry labelMeaningStatus
Source researchedCited information was checked against the identified sources. Nothing was run or built.In use.
Setup reproducedA 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 testedA 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.

LayerRobotsProjects
Mechanical designAssessedNot assessed
ElectronicsAssessedNot assessed
FirmwareAssessedNot assessed
SoftwareAssessedAssessed
Model weightsAssessedAssessed
DatasetsAssessedAssessed
DocumentationAssessedAssessed
Per-layer recordValues
ApplicabilityUnknown, applicable, or not applicable with a reason.
AvailabilityUnknown, available, not found, or unavailable. Not found describes our search, not proof that files do not exist.
Artifact linkWhere the files are.
License and license linkThe identifier or text exactly as published; never guessed from a hosting platform.
Sources, checked date and notesThe evidence behind the assessment and any restrictions.
Inclusion decisionMeaning
UnresolvedOpenness is not yet established; the entry stays in research.
Include as openEvery applicable layer has an available artifact and a cited license.
Include as partialSome layers are open; the gaps are stated.
Include as source-availableFiles are visible but reuse is restricted; the restrictions are stated.
ExcludeNot 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 kindMeaning
Vendor priceA specific seller's offer.
Parts estimateThe sum of a bill of materials.
Measured expenditureWhat we actually paid for a build.
Robot cost scenarioMeaning
Parts onlyA do-it-yourself parts list; whether printed parts are included is stated.
KitA specific vendor kit, naming the components it leaves out.
AssembledAn assembled robot, stating calibration and accessory coverage.
First working setupEverything required for a named first task, including peripherals and compute, or equipment explicitly assumed to be owned.
Every price recordsMeaning
Configuration and quantityThe named revision and variant, how many robots or leader arms, and the units priced.
Amount or rangeA single amount, or a lower and upper bound with the assumptions behind the range.
Currency and regionAs quoted; prices in different currencies are not compared.
Included and excludedMotors, controllers, structure, cameras, power, cables, host computer and tools, as relevant.
Shipping and taxHow delivery and tax were treated; unknown charges stay unknown.
AvailabilityStock at the time of the check.
Checked dateWhen this quote or estimate was checked.
EvidenceThe 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.

ConceptMeaning
ConfigurationA named robot revision or variant with one first task.
PartA technical identity in the shared parts library: exact voltage, gear ratio, dimensions and revision where relevant.
RequirementA configuration's purchased item, printed group, fabrication job, peripheral or tool, with quantity, cost layer, required or optional status and evidence.
OfferOne supplier listing for a part, with immutable dated price and stock observations. Price changes never change technical identity.
SubstituteAn alternative candidate with an explicit compatibility scope and evidence; never an automatic replacement in a total.
Ownership scenarioQuantities a reader already owns. The public baseline assumes nothing is owned.
RollupThe derived estimate for one configuration and one ownership scenario.
Cost layerContentsIn the Parts total
Purchased partsMotors, controllers, bearings, fasteners and cables specific to the robot.Yes
Printed partsMaterial to buy, or the selected print service.Yes
Fabricated partsCNC, laser-cut or PCB fabrication.Yes
Power and cablingPower and data components not counted elsewhere.Yes
Host computeThe computer or single-board computer the first task needs.Shown separately; required unless owned
Sensors and cameraSensors or cameras the first task needs.Shown separately; required unless owned
ToolsOne-time tools, and a printer when self-printing.Shown separately; required unless owned
Shipping and taxA destination- and basket-specific estimate, or unknown.Shown separately
LaborBuild hours.Never priced
MeasureValuesMeaning
BOM coverageComplete, partial or unknownWhether every requirement of the first task is listed. Pricing every listed line does not make a BOM complete.
Pricing coveragePriced groups out of required groups, with named gapsHow much of the required purchase has an eligible price.
Setup readinessPriced, priced with owned items, or incompleteWhether a first-working-setup budget can be stated. It is budget readiness, not proof that the build works.
Pricing ruleEffect
Dates, not freshness labelsEvery price shows the date it was observed. Rereading a page does not move a published figure's date forward.
EligibilityA 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 directOnce 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 arithmeticWhole 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 materialMaterial consumed is reported separately from the spools that must be bought; only the purchase enters the total.
Incomplete totalsWhen 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 linksOffer 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 fieldMeaning
IDA stable identifier within the entry, cited next to claims.
TypeUpstream, license, paper, maintainer, vendor, secondary reporting or local test.
Title and linkThe source title and its direct public URL.
PublisherThe author or organization when established; otherwise a note that attribution is not established.
LocatorThe release, commit, file, API field or section used, preferring a revision-specific permalink.
Accessed dateWhen the source was retrieved. Retrieval is distinct from the claim's checked date.
FindingWhich information the source supports and any limits on its scope.
Retrieval methodManual, API or local test, with the public endpoint and fetch time when recorded.
Asset credit fieldMeaning
AssetThe reused image, diagram, excerpt or dataset.
Creator and source URLWho made it and where it came from.
Rights URL and license or permissionThe evidence that reuse is allowed.
Credit textThe wording the terms require.
ModificationsAny 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

LabelMeaning
Upstream last updatedThe latest relevant upstream change we could establish, with its source and scope.
Latest releaseThe date of the relevant published release.
Profile updatedWhen we last materially changed the entry's content.
Sources last checkedOur latest substantive source review, even if nothing changed.
Price checkedWhen each particular quote or estimate was checked.
Next reviewWhen 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 categoriesProject categories
Robot arms and manipulatorsFrameworks
Wheeled and tracked robotsLibraries
Legged robotsMiddleware
HumanoidsTools
Aerial robotsModels
Marine robotsDatasets
Other physical robotsSimulation
End effectors: grippers, robotic hands, extrusion and dispensing tools, other process tools, tool changers
Tag facetTerms
CapabilityManipulation, navigation, perception, teleoperation, mapping / SLAM, grasping, locomotion, data collection, robot learning, simulation, motion planning, material extrusion, material dispensing, tool changing.
Use caseLearning and education, research, prototyping, inspection, logistics, agriculture, assistive applications, entertainment.
EcosystemROS 2, ROS 1, LeRobot, Arduino, Raspberry Pi, NVIDIA Jetson, MuJoCo, Gazebo, Isaac Sim. A tag means a documented integration, never probable compatibility.
MechanismParallel jaws, adaptive grip, soft grip, vacuum / suction, magnetic pickup, tendon drive, pellet extrusion, filament extrusion, syringe extrusion, pneumatic actuation, tool changing.
PlatformDocumented 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.

RelationshipMeaning
UsesThe entry depends on another project.
Compatible withA documented, versioned integration.
Based onDerived from another design or project.
Fork ofA fork of another project.
Successor toReplaces 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

StageMeaning
DraftResearch in progress; not published.
Review readyRequired 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.
ApprovedA named reviewer, approval date and decision note are recorded.
PublishedThe entry additionally has a real public URL.
Held or archivedSet 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

PartValues
Discussion statusPlanned, disabled or enabled. Enabled requires a real public discussion URL.
Robot reactionsUseful, Want to build, Built it.
Project reactionsUseful, Want to try, Used it.
Comment categoriesQuestion, 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

VersionApprovedWhat it addedContract
0.5.0-draft.1September 29, 2026First public pilot: configuration-specific costs, activity scope, source attribution and asset credits.Read 0.5.0-draft.1
0.6.0-draft.1September 30, 2026The end-effector category hierarchy and evidenced mechanism and platform tags.Read 0.6.0-draft.1
0.7.0-draft.5October 4, 2026Optional 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.