Documentation / THOR
06 / 22
Why THOR
THOR replaces the private vendor chain with a standing market for specified and verified work.
A traditional data vendor controls supply, pricing and quality inside one contract. That model becomes restrictive when robotics work is specialised, repeated and distributed across many capable teams.
| Dimension | Centralised vendor | THOR orderbook |
|---|---|---|
| Supply | VendorFixed headcount in one or two geographies | THOROpen pool of humans, AI-assisted teams and vendors |
| Selection | VendorThe buyer picks one vendor and hopes | THORNetwork routes to the cheapest supply that clears spec |
| Verification | VendorSampled QA after delivery | THOREvery unit checked against a pre-committed spec |
| Pricing | VendorPer hour; multiple prices for the same hour | THORPer verified unit; one auditable price |
| Scaling | VendorCost rises with headcount | THORIncentives expand supply and improve the cost curve |
THOR coordination mechanism creates efficiency for researchers to source data
THOR publishes the brief, separates production from validation and records how each item was judged. The customer still buys a managed service, while the market underneath can admit more suppliers and compare them on the same work.