Compliance for robots that keep changing.

Every update can change what a robot is and who answers for it. Odom is building the file and the change log that keep up, starting with robots entering Europe.

Message Mohamed

Message Mohamed

A checked file for each model. A dated log for each robot.

We're starting with firms that bring robots into Europe.

The maker's paperwork, read against the rules that apply, with every item marked.
Model fileSample
  • Who answers for it in each marketFound
  • Which rules apply, by date of first saleFound
  • Maker's signed declarationFound
  • Certificates and who issued themConflicts
  • Technical fileAsk the maker
  • Radio and battery test reportsNot public
  • Risk assessmentNeeds an engineer
A dated entry for every sale, update and repair, from paperwork the firm already holds. Every update gets a review.
Serial 00417Sample
  1. Built, serial 00417Maker's file
  2. Sold in EuropeSales recordJudged under the 2027 machinery rules.
  3. Software 2.4Release note
  4. Security fix 2.4.1Release note
  5. Service, left arm replacedService invoice
  6. Software 3.0, carries loadsRelease noteNeeds an engineer: could this make the firm the legal manufacturer?
  7. Resold to a second ownerSales record

It leaves the factory with a file.

A distributor sells it in Europe.

The importer is now responsible for a robot it didn't build.

Then the robot changes.

The factory file still describes the old machine.

A flaw is found and fixed.

Some robots get it. No shared record says which.

A part is replaced.

Same serial number, new abilities.

A big enough change can make the firm behind it the legal manufacturer.

A buyer asks what happened.

A used car has a history. This robot's sits in pieces.

Who holds whatMakerDistributorService firmBuyer
  1. Built, serial 00417
  2. Sold in Europe
  3. Software 2.4
  4. Security fix 2.4.1
  5. Service, left arm replaced
  6. Software 3.0, carries loads
  7. Resold to a second owner

Other machines got here first.

  1. ShipsUnderwriters couldn't see the hull.
  2. Steam boilersOwners paid inspectors after 104 explosions in the 1840s.
  3. Electrical goodsFire insurers backed the lab that became UL.
  4. AircraftA treaty required log books. They pass with the plane at sale.
  5. CarsLenders needed to see what was owed. Carfax came in 1984.
  6. DronesRegulators made owners register, the year one crashed at the White House.

The first to ask was rarely the maker. Usually it was whoever paid for the failure.

Why not robots?

Five million factory robots have no shared record, and neither do forklifts. They change slowly, so a check at handover shows a buyer most of what matters.

New robots change with every update. No check at handover shows that.

HumanoidsChina began a national record. No widely used shared record exists in Europe.

The volumes are forecast.The dates are fixed.

  1. About 7,000

    humanoids sold in 2025, IFR

  2. Over 510,000

    a year by 2030, IDC forecast

  3. About 6.5 million

    a year by 2035, Goldman Sachs forecast

  1. EU liability law extends to software
  2. New EU machinery rules apply
  3. Cyber Resilience Act in full
  4. AI safety rules for machinery due

No rule requires a shared record. Importers already answer for what they bring in, so we start there and follow the robots to other markets.

Why Odom.

Odometry is how a robot knows where it's been.Odom is how everyone else will.

We're building a platform of AI agents that follow every robot after it's sold. They'll read each release note, certificate and service invoice, trace every line to its source, and log what changed on each robot. We're pre-product today, starting with files made by hand.

The firms that bring robots in will get one file that stays current, and an answer the day an authority, insurer or buyer asks what changed. We keep the evidence. They make the call.

Machines get a record when a lender, insurer or regulator demands one.We're betting robots are next.

Message Mohamed

Message Mohamed

Mohamed Sharif, founder. sharif@odom.app