Who operates the pool

The shortest answer is that the people who already operate the floor operate the pool. A Czar Grid is a fixture in the building's own rack, serving the building's own robots over the building's own network, and the team that runs the controllers and the fleet software runs it. There is no remote operations center, no vendor on a standing connection, and no new department. What follows is how the existing roles divide the work.

The automation team

The automation team owns the pool. They read its record each shift, watch latency budgets and fallbacks, apply updates in the order they choose, and decide when a node comes out of service and goes back in. They are the people who notice that a fleet fell back more than usual overnight and go find out why.

They also own the approval queue in Agency Studio, or at least a seat on it. Tasks are authored, versioned, and bounded, and a named role approves each version before it runs. The automation lead is nearly always one of those roles, because the lead is the person who knows what the floor looks like today and whether a task's bounds still fit it.

The safety officer

Safety stays on the robot. Stops, speed limits, reflexes, and motion limits remain on the machine exactly as the vendor delivered them, and the pool cannot change them. Even so, the safety officer has a direct role in the pool, because the bounds on a site task are safety decisions: which zones a robot may enter, how fast it may move there, how close it may come to a person or a structure, where it must stop.

On a well-run site the safety officer is a named approver for task versions and reads the record after any incident. The officer does not need to understand inference. The officer needs to be able to read a task's bounds, compare them to the floor, and sign or refuse. Agency Studio is built so that is exactly what the approval shows.

The integrator

Where a site has a systems integrator, the integrator maintains the seams: the declared routes through Local Bridge to the fleet software, the warehouse system, and the controllers; the onboarding of each new fleet onto the pool; the conversation with each vendor about budgets and fallbacks. On a connected site the integrator is usually the person who proposes a new route and the automation lead the person who approves it.

Sites without an integrator fold these duties into the automation team. The role is a set of responsibilities rather than a required contractor, and the record looks the same whoever carries it.

The robot vendors

Each robot vendor remains responsible for its machines. The pool serves perception, decisions, and language to a vendor's robots over the facility's network; it does not reach inside them. The vendor's on-board model stays on the robot as the fallback, the vendor's safety stays on the robot without exception, and the vendor's fleet software remains the vendor's.

What vendors need from the site is clear communication about budgets and about what the record shows for their fleet. What the site needs from vendors is their fleet software and their cooperation in pointing robots at the pool. In a mixed fleet the pool serves them all, and the operations team is the one place where the whole picture is visible.

Where Element 31 stands

Element 31 engineers install the pool with the operator's team, the integrator, and the vendors through E31 Consulting. During installation they are on the floor. After it, their role narrows deliberately. The pool does not report to Element 31 and Element 31 does not operate it.

When the site wants help, a session is customer-initiated through the portal. Customer appliances never connect to the portal; the customer opens the session. On sovereign sites, a remote session happens only inside an uplink window the customer has attested to, with data disks detached, the network isolated, the console supervised, and authority confirmed, and the window carries a hard expiry. Outside those windows and those sessions, Element 31 has no presence on the floor.

One variation deserves a note. Under Czar Chassis, a robot vendor or integrator ships the Grid under its own name, with its own fleet, so the customer receives one system. The same Czar, the same Substrate, the same record. In that arrangement the vendor or integrator may carry the operating duties described above as part of the system it delivers, while Element 31 provides sustainment and attestation underneath. The building still decides posture, still holds its record, and still approves its tasks. Which route a site takes is a commercial choice covered on the How to buy page, not a technical one.

Whichever route, the principle is constant: the pool is operated from inside the building by named people whose approvals and observations are in the record. Training the site team describes how those people come up to speed.