What does not change for the robot vendor

A robot vendor hearing that a facility is installing an inference pool is right to ask what it means for the machines it ships. Vendors have seen facility systems that quietly took over functions the robot was designed to own, and they have taken the support calls when those systems failed. A Czar Grid is built around a different division of labor. This article lists what stays with the vendor, because it is most of what the vendor cares about.

Safety stays on the machine

The pool serves perception, decisions, and language models. It does not serve stops. Speed limits, reflexes, motion limits, and emergency behavior stay on the robot exactly as the vendor set them, and nothing in the Grid has a path to override them. A site task authored in Agency Studio is bounded by zones, speeds, distances, and stops, but those bounds are applied within the robot's own limits, not in place of them.

This has a direct consequence for how the pool fails. A pool that is down leaves a robot that stops, because the robot's own safety behavior is still there. It does not leave a robot that guesses, because the pool was never in the loop that decides whether to move. For a vendor, this means the safety case it built for the robot is the safety case that still applies on a floor with a Grid.

The on-board model stays, and it is the fallback

Every robot keeps its own on-board model for reflexes and for the moments when the pool cannot answer within the robot's budget. The vendor decides where that boundary sits: which requests go to the pool, which stay on board, and how long the robot waits before falling back. Substrate enforces the budget inside the pool, but the budget itself comes from the vendor's knowledge of its own machine.

The pool therefore adds capability above the on-board model rather than replacing it. A mobile robot that could already navigate a fixed aisle on its own now gets perception for an aisle that changed overnight. A pick arm that could already grasp known items now gets a decision for an item it has never seen. When the pool is silent, the robot is what it was before the pool arrived.

The vendor's fleet software stays in command

On a connected site, the pool reaches only the systems the site declared, and the vendor's fleet software is usually one of them. That connection exists so the pool can serve the vendor's robots; it does not make the pool a fleet manager. The fleet software still dispatches the robots, tracks them, and reports on them. The warehouse system still issues the work.

Local Bridge enforces the declared routes and denies everything else by default. From the vendor's side, this means the pool talks to its fleet software over a route the site authorized, and to nothing else of the vendor's. On an air-gapped site, the vendor's fleet software and the pool live inside the same closed network and nothing reaches out from either. The technology page describes how declared routes work.

The customer relationship stays with the vendor

The vendor supports its own robots as it did before. A fault in a robot is the vendor's call. A question about a task is the operator's, answered from the record in Agency Studio. A question about the pool goes to whoever holds the subscription: the building under Facility Direct, or the vendor itself under Czar Chassis.

Under Czar Chassis, the vendor becomes the name on the pool as well as on the fleet. The facility sees one system and calls one party. Element 31 provides sustainment and attestation underneath: the signed image, the attestation each node performs, the provenance record, and the signed updates. The vendor's customer relationship does not shrink; it widens to include the pool, without the vendor having to build or staff it. The Czar Chassis page describes that arrangement.

The data stays in the building, which protects the vendor too

Camera feeds, captures, task records, and adapted model weights stay on the operator's hardware inside the operator's network. The vendor is never asked to host them, carry them, or answer for them. Adaptation happens on the pool, on the site's own captures, and the resulting weights stay on site. A vendor whose own cloud would otherwise have become the custodian of a customer's floor is relieved of that role.

None of this requires the vendor to change the robot. The pool fits around the machine as shipped, respects the boundaries the vendor drew, and gives the robot more than it could carry. What changes is what the fleet can do on that floor. What does not change is everything the vendor is responsible for.