Why a facility keeps a neutral pool

Every robot vendor that sells into a facility would like to sell the compute that serves its robots. That is reasonable from the vendor's side. From the building's side it produces a floor with as many pools as there are vendors, each one tuned to its owner's fleet, each one holding a slice of the site's captures, and none of them answering to the operator. A neutral pool is the alternative: one Grid the building holds, serving every robot in it on equal terms. This article explains why an operator should want that and what it takes to keep it.

Equal service across fleets

A pool owned by one vendor will, in practice, serve that vendor's robots first. Its latency budgets are set for those machines. Its models are adapted on those machines' captures. When a second vendor's humanoids arrive, they are guests on someone else's compute, and the first vendor has no obligation to serve them well.

A Grid the building holds has no such preference. Substrate enforces each robot's latency budget inside the pool regardless of who made the robot. Mobile robots from one vendor, pick arms from a second, and humanoids from a third draw from the same pool under their own budgets, and each falls back to its own on-board model when the pool cannot answer in time. No fleet is a guest. The solutions for logistics page describes a warehouse floor where this matters daily.

Fleets turn over; buildings stay

A warehouse or a plant is operated for far longer than any one fleet is kept. Vendors are replaced. A pilot fleet from one supplier gives way to a production fleet from another. A new kind of machine arrives that none of the current vendors make. If the pool belongs to a vendor, every one of those changes is also a compute decision, and the departing vendor takes its pool, its adapted models, and its slice of the record with it.

A neutral pool stays through all of it. The departing fleet stops drawing from the Grid. The remaining fleets continue. The incoming fleet is connected under its own budgets, and the models adapted on the site's captures remain the site's. The pool is part of the building, in the way the rack and the network are, and it changes on the building's schedule.

The record belongs to the operator

Agency Studio records every run of every site task, and Substrate keeps the record of every decision the pool served. That record is the thing a safety officer reads after an incident, the thing an auditor can read, and the thing the operator uses to improve the floor. It should not live inside a vendor's system where the operator reads it by permission.

On a neutral pool the record stays on the operator's hardware inside the operator's network, and the roles that approve tasks and read the record are the operator's named people. The same is true of the captures and the adapted model weights. A vendor whose robots are served by the pool sees what the operator grants, and nothing more. This is not a slight against vendors; it is the only arrangement in which the operator can answer for its own floor.

Neutral in practice, not only in principle

Neutrality is a property of who holds the subscription. Under Facility Direct the building subscribes to the configured Grid, and the pool is the building's to point at any fleet. Under Czar Chassis a vendor ships the same Grid under its own name, and the pool is technically capable of serving any vendor's robots, but whether it does is a matter of the vendor's agreement with the facility.

An operator that wants a neutral pool and also wants a vendor's bundled offer can have both, provided the agreement says so. The things to secure are plain: the pool serves any fleet the operator connects, the named roles are the operator's, and the record and captures stay with the operator. A vendor that agrees to those terms is shipping a neutral pool under its own name, which is a fine outcome for everyone. The How to buy page describes how each route holds the line.

What neutrality costs

Holding the pool means the building holds the relationship with Element 31 directly, through the customer portal, and names the people who will approve tasks and read the record. It does not mean maintaining the appliance. The sealed image, attestation, signed updates, and support are Element 31's for the term under one subscription line that does not move as fleets are added.

The cost of neutrality, then, is a decision and a few named roles. The cost of its absence is a floor whose intelligence belongs to whichever vendor was there first.