Skip to content

01/07

Manual procedure

Trust is hand-made today

Today, humanoids deploy where trust was built one partner at a time: a shareholder in the cap table, years of joint pilots, an industrial partner with its own stake in the outcome. Schaeffler is the clearest case: minority investor in Agility, deployment and actuator deals with Hexagon and Humanoid, four-digit fleets planned in its own plants. It deploys the humanoids and supplies the joints they run on: both sides of the table.

That model created the first references. It cannot scale.

Your next hundred customers hold no shares, ran no pilot with you, and will not take your word for the state of your machines.

02/07

Failure mode

What actually blocks the signature

You know better than anyone what a long pilot costs in engineers on site and revenue pushed back. The blocker at the end is rarely the humanoid. It is the proof around it: the customer’s insurer, its works council, its safety officer, and the next customer who was not in the room. None of them can accept the seller grading its own machines.

Not because your numbers are wrong: because nobody can check them.

03/07

Scope boundary

We do not redo your work

Type testing, homologation, update validation on reference units: yours. We never touch it, the same way the vehicle inspection does not redo the crash test.

Our object is the unit in service: does humanoid no. 047, with 4,000 hours in that plant, still hold the specifications you declared? Industry already treats every machine that runs near people this way. An elevator is certified at build; in Germany an approved independent body still inspects it every year and re-triggers the safety gear, and after an accident, that body’s safety assessment is what the law asks for. Nobody reads that as distrust of the elevator maker. It is what lets elevators be everywhere.

Your telemetry is the OBD. We are the periodic inspection.

On cars the two have coexisted for thirty years, and the modern test lane plugs into the OBD and cross-checks it. We work the same way: your fleet data is an input we anchor to an external calibrated reference, not a rival we ignore.

SCOPE BOUNDARYYOURSREFERENCE UNITTYPE TESTINGHOMOLOGATIONUPDATE VALIDATIONON REFERENCE UNITSAIH GLOBALCALIBRATEDREFERENCEUNIT IN SERVICEHumanoid no. 0474,000 hTELEMETRY (OBD)PERIODIC INSPECTION
Fig. 03 — Left of the boundary: type testing, homologation, update validation on reference units. Right of it: the unit in service, measured against a calibrated reference. Telemetry crosses the boundary as an input.

04/07

Interface requirement

What we need from you

One thing, once per model, not per humanoid: a test mode.

Direct joint commands, AI correction off, read access to motor currents and temperatures. With it, our station measures your humanoids in open loop: the naked mechanical truth, before the controller compensates it.

CLOSED LOOPCOMMANDAI CORRECTIONOFFTEST MODEDIRECT JOINT COMMANDSOPEN LOOPJOINTREAD ACCESSMOTOR CURRENTTEMPERATURE
Fig. 04 — The AI correction path opened, the joint driven directly in open loop, motor current and temperature read while the station measures.

05/07

Measured output

What you get

A real layer of trust with your customers. Humanoids that clear the insurer and the works council sell faster, and stay deployed. And something your telemetry structurally cannot produce: independent, calibrated wear data from worn units in real sites, measured against an external reference that survives your updates. Your engineers get ground truth from the field. Your customers get proof.

Your sales team stops arguing about whose dashboard to believe.

06/07

First article

Our vision, and why the first maker wins

We believe every deployed humanoid will end up needing independent in-service proof, and that operators will write it into purchase orders: their insurer, their works council and their own legal duties all push in that direction.

That proof cannot exist without two objects: a test protocol per humanoid model, and a test interface in the humanoid’s software.

Both will be written a first time, on somebody’s machines.

The maker who opens first gets three compounding advantages. The reference protocol is shaped on your humanoid: your machines are verifiable from day one, competitors retrofit later. Your fleet starts its verified history first, and a measurement history is the one asset a latecomer cannot replay. And when insurers and buyers start referencing a protocol in policies and purchase orders, they reference the one that exists: the one written on your machines.

That is what defining the standard means here. Not a committee seat: the physical protocol the market copies. The OBD port is the precedent: one test interface, defined once, that the whole inspection world now plugs into.

Once one maker opens, refusing starts to look like hiding.

FIRST TO OPENREFERENCEPROTOCOLYOUA LATECOMERRETROFIT LATERVERIFIED FLEETHISTORYYOUA LATECOMERCANNOT BE REPLAYEDPOLICIES ANDPURCHASE ORDERSYOUA LATECOMERTHE ONE THAT EXISTSPRECEDENT — OBD PORTOne test interface, defined once.
Fig. 06 — Three compounding advantages, row by row. Precedent: the OBD port.

07/07

Selection open

Design partners

We are selecting design partners now. We co-write the protocol on your humanoid, prepare your model for the station, and run it at your first customer’s site.