Scenarios we've worked through, waiting on one missing piece.
Each one is written out from the request to the receipt. None of them is available yet: each needs something the task spec can't express today, and we'll build it with the first partner who runs the work.
7 of 7
LabsPhysical AIStuck? Hand over the controls.A humanoid fails the same grasp three times and hands its body to a remote operator for ten minutes. The rescue becomes licensed training data.See the scenario 
LabsHospitalityCheckout starts the clean.The humanoid does the heavy turnover, then posts the finishing touches to a housekeeper. The room is ready only when both parts are proven.See the scenario 
LabsLogisticsOne trailer. Three kinds of hands.Humanoids lift, a person takes the awkward cases, robots move the pallets. One count against the manifest, with each member's share.See the scenario 
LabsMobilityLeft on the back seat. Back in your hand.The car spots a phone and a spill, then asks for a clean and a return. Every handoff of the phone is signed until the rider has it back.See the scenario 
LabsPhysical AIA benchmark you can check.Two robot policies are tested blind in fifty real kitchens. Every attempt is a claim, and the success rates come with proof.See the scenario 
LabsHealthcareNo gap in the chain.Blood samples go from ward to lab. When a lift breaks, a porter takes over, and custody and temperature are unbroken throughout.See the scenario 
LabsAgricultureSprayed only where it was needed.Traps raise the alarm, a scout confirms, and the robot treats six rows and no more. The proof covers restraint as well as work.See the scenario
The missing pieces, in the order we'll build them.
One partner per gap unlocks several scenarios at once. We run two or three co-design projects at a time.
| Gap | What's missing | Scenarios it unlocks | Priority |
|---|---|---|---|
| Custody chains | An ordered list of custodians, each with a signed handoff and seal state, and a check that fails on any break. | Left on the back seat. Back in your hand., No gap in the chain. | 1 |
| Team member shares | Who did which part of a shared task, with a pay share and evidence for each member. | One trailer. Three kinds of hands., Checkout starts the clean., A benchmark you can check. | 1 |
| Remote performers | How a machine was controlled (autonomous, supervised, teleoperated) and the remote operator as a second actor. | Stuck? Hand over the controls. | 2 |
| By-product data rights | Who owns training data created as a side effect, and whether the person who did the work shares in it. | Stuck? Hand over the controls. | 2 |
| Blinded evaluation | A field hidden from the performer but committed in the proof. | A benchmark you can check. | 3 |
Protocol changes from co-design are published openly. Your data, sites, prices and configuration stay private. How co-design works