The record

Why a record, before a robot

A hub with no record is a parking lot. What makes a hub worth paying for is that every robot on it produces evidence: that it was launch-ready when it left, who made it so, what went wrong and what changed because of it. Three readers need that evidence and today none of them can get it in the Carolinas. Tesla's network needs to know its vehicles are ready and who signed them so. An underwriter prices what it can read and nothing else. A lender that financed a member's Cybercab needs to know the collateral is working, maintained, and where it is supposed to be. One record, one format, three readers. We are writing it before the first robot arrives because a record that starts on day one is worth more than one that starts on day one hundred.

What the record contains, per robot

Identity and status. Which robot (Cybercab, Robotaxi vehicle, Robovan, or Optimus unit), which hub, which owner of record, and its current state: launch-ready, in service, out of service with the reason, or retired.

Launch-ready, system by system. The written standard says what a robot must be to carry a rider or to work the floor, system by system. Each inspection records each system's result, the time, and the name of the qualified person who signed it. A robot that fails any system is out of service, and the record says so.

Hours in service and hours out of service. The number the hub lives by, per robot, per day, with every out-of-service interval attributed to a cause: inspection, repair, cleaning, charging, waiting for a part, held by a review.

Who touched it and when. Every inspection, repair, clean, charge, and move carries the time and the name of the person or the identifier of the Optimus unit that did it, and the qualification that person held for that task on that day.

Incidents against a procedure. A vehicle that stops, a rider who needs help, a near miss on the floor, damage in a bay: each one logged against the written procedure that governs it, with what was done and when.

Root-cause reviews. Any repeat fault within thirty days, any repeated rider complaint on the same robot or route, any charging position that fails twice, any near miss: the review, the cause it landed on (a part, a procedure, a supplier, or a training gap), and the change to the standard it produced.

Maintenance and parts. What was replaced, when, by whom, from which supplier, and against which fault.

Charging and energy. Sessions per position, energy delivered, failures, and the position's uptime.

Cleaning. Interior turnarounds, full details, and camera-clear checks, each against the checklist and the card that shows what clear looks like.

Rider feedback. Cleanliness and condition as the rider reported it, entered as a measurement, because the rider defines quality.

Who reads it, and what each reader gets

• Tesla's network. Launch-ready status and sign-off for every vehicle, hours in and out of service, incidents, and the record of who did what. The numbers the network reports coming from our floor.
• An insurer. The qualification record, the incident log against procedures, the root-cause reviews closed with a change. Not a loss record, which does not exist yet, but the evidence that lets an underwriter price the risk of a floor run this way.
• A lender. For a robot a credit union or bank financed for a member or a business: where it is, whether it is working, hours in service, maintenance history, and incidents, as a monthly statement. The collateral, accounted for.
• A partner or municipality. Utilization, wait times, and incidents at the pickup points and hubs they host. We report what happened, not what we hoped would happen.

How it is produced

The record is not a report written after the fact. It is the by-product of the four procedures every hub runs: the launch-ready inspection produces the status and the sign-off; the incident procedure produces the incident entry; the root-cause review produces the cause and the change; the weekly improvement review produces the adopted changes. Nothing enters the record that did not happen on the floor, and nothing happens on the floor without entering the record.

The format

One machine-readable schema, published in our repository and versioned, that every hub's systems write to and every reader can be given access to under an agreement. Monthly statements per robot for lenders and owners. Live status for the network. The schema exists today as a first draft; it will change as Tesla's vehicles, the first insurer, and the first lender tell us what they need, and every change will be versioned.

Talk to us about the record

If you would read this record as a network, an insurer, or a lender, or if you have built one like it for another fleet, use the form and say so. The first reader who tells us what is missing shapes version 0.2.

What we do not know yet

What Tesla's vehicles report and in what form, until Tesla makes them available to independent operators. What the first insurer and the first lender will ask for beyond what is listed here. Whether an Optimus unit's work is recorded by the unit itself or by the floor's systems. We will find out from them and change the record accordingly, and we will not pretend the record is finished until a robot has written to it.

This page is an expression of interest only. It is not an offer to sell, or a solicitation of an offer to buy, any security. Any offering would be made only to accredited investors through definitive offering documents. Robot Mercantile LLC is an independent company and is not affiliated with, endorsed by, or acting on behalf of Tesla, Inc. Tesla, Robotaxi, Cybercab, and Full Self-Driving are trademarks of Tesla, Inc.