IDWorthy for robots

The Robot Operational Record

A controlled, current view of a robot's identity, responsibility, deployment, software, maintenance, and lifecycle history—every field carrying its source, evidence, and verification state.

019b8df2-7c35-7a14-8c95-6f26b73fd421

Illustrative UUIDv7-format example · Meridian Robotics · MRD-40

● activerecord v41

Identity

Serial: SN 40-08812
GS1: (01) 09521234…
Cloud ID: iot:dev/mrd40
Fleet ID: NG-EAST-117

Responsibility

Owner: Axiom Leasing
Operator: Northgate Facilities
Maintainer: RoboServe GmbH
Since: 2025-08-14

Software & AI

Firmware: v4.2.1
Autonomy: nav-core 12.3
AI model: percept-lg-0625
SBOM: linked · sha256✓

Recent lifecycle events

2026-07-11software_updatedverified

2026-06-28maintenance_performedverified

2026-05-02component_replacedcorroborated

2025-08-14operator_changedverified

What it is—and what it deliberately isn't.

IDWorthy is

✓ An evidence-backed operational record around one permanent identity

✓ Cross-manufacturer, cross-fleet, cross-jurisdiction

✓ A linking layer for serials, GS1, cloud IDs, twins, and registrations

✓ Bitemporal: what was true, and when it became known

IDWorthy is not

× A replacement for serial numbers, GS1, or product passports

× A device-management platform or digital twin

× A public rating—records exist without scores by default

× A public directory of where robots operate

The initial commercial offer

Fleet Identity and Reconciliation Pilot

Paid early-adopter engagement for fleets of approximately 50 to 500 commercial or service robots.

Reconcile the records you already have, establish a controlled operational record for each in-scope robot, and identify practical data and implementation gaps.

Reconciled fleet records

Connect manufacturer, serial, fleet, maintenance, and deployment records. Surface duplicates, gaps, and unresolved conflicts.

Persistent Robot IDs

Issue one immutable IDWorthy identity for each in-scope robot, linked to its permanent resolver.

Controlled operational records

Establish a current record for responsibility, deployment, software, configuration, maintenance, and lifecycle history.

Handover and transfer continuity

Maintain an evidence-backed record as robots move between sites, operators, maintainers, or customers.

Controlled lifecycle exports

Produce permitted records for maintenance, customer handover, audit preparation, and insurer review.

Implementation findings

Receive a reconciliation report identifying data gaps, ownership questions, and practical next steps.

Starting with commercial and service robots.

Where robots change owners, sites, software, and tasks—and where insurers, integrators, and facility operators already ask who is accountable.

See your fleet as one governed record.

Discuss a paid engagement to reconcile your fleet records and establish operational continuity.

Discuss a paid pilot How it works