Knowledge work is already being routed to models. Physical work is next. When a task can be dispatched to a crew, a contractor, or a robot, the question stops being who's available and becomes which unit of labour is cheapest and competent.
// dispatch a task, not a personawait allometry.work.dispatch({ task: "panel_inspection", location: "loc_8f2a", constraints: { sla: "4h" }}) → routed: bot_fleet_02 · $18 · 41min
Because the substrate already knows the true cost of a crew hour at that address, it can compare a crew, a subcontractor, and a robot fleet on the same basis — and route accordingly.
Anyone can list vendors. Deciding correctly requires knowing the fully-loaded cost of a crew hour at that specific address, on that specific asset — which is exactly what the Deploy loop already computes.
We're working with a small group of operators to model buy-versus-build-versus-rent on real job data — so when programmable labour is available at scale, the decision is already underwritten.