The Chassis brand and what the facility sees

A facility that takes a Grid through a robot vendor or integrator sees that party's name everywhere: on the agreement, on the support line, on the rack if the vendor labels it. This is by design. Czar Chassis exists so that a vendor can ship the pool with its fleet and the customer receives one system from one name. What this article covers is the layer beneath the brand, because the facility should know what it is getting regardless of whose name is on the front.

What the brand covers

Under Czar Chassis the vendor holds the subscription for the configured Grid, hardware, platform license, and sustainment in one line, and wraps it with its fleet in whatever way it structures its own offer. The facility's agreement is with the vendor. When something on the pool needs attention, the facility calls the vendor. When the vendor's robots need a model served, the vendor's Grid serves it.

The brand therefore covers the relationship. It does not cover the engineering, which is the same Czar on every route. The Czar Chassis page describes the arrangement from the vendor's side; here it is described from the floor.

What the facility sees on the rack

The nodes in the rack are Czar nodes: sealed enclosures with sealed, signed, read-only images. Each one attests what it is running before it joins the Grid or accepts a task. The brand on the bezel does not change what the node will or will not do. A node that fails attestation does not join, under any name.

Substrate runs on the Grid in the same way it would under Facility Direct: inference across the pool, each robot's latency budget, memory, retrieval over the site's documents, adaptation on the site's captures, evaluation and the record, integrity verification through Watchman, and governed connectivity through Local Bridge. Agency Studio is the task layer, with the same named roles and the same replayable record. A Chassis Grid does not run a vendor edition of any of this.

What the facility should be able to read

Whatever the brand, the operator should be able to open three things. The first is the provenance record for each node: its integration, its sealing, and its software load, so that the question of where the hardware came from is answered from a record rather than from the vendor's assurance. The second is the record of every site task run and every decision the pool served, kept on the operator's hardware and read by the operator's named roles. The third is the attestation each node performed when it joined.

A vendor shipping under Czar Chassis should expect to be asked for all three and should be able to show them, because they exist underneath its brand regardless. A facility that cannot read them under a vendor's name is not receiving a Czar Grid as it is meant to be run, and should ask why. The questions to ask any facility AI vendor article lists what to request.

What sits beneath the brand

Element 31 provides sustainment and attestation beneath the vendor's name. That means the signed image and every signed update to it, the attestation machinery each node uses, the provenance record, and the support path the vendor relies on when a question goes past the fleet. Remote sessions are customer-initiated through the portal and never initiated from outside, and on a sovereign site an uplink window requires the customer's attestation before it is approved and carries a hard expiry.

The facility may never deal with Element 31 directly under a Chassis arrangement, and that is the point of the route. But the facility should know that the party signing the image is the party that sealed the node, and that the vendor's brand sits on top of that chain rather than in place of it.

Keeping the record with the operator

The single most important term in a Chassis agreement is who reads the record. The pool keeps the record on the operator's hardware inside the operator's network. Agency Studio's named roles approve tasks and replay runs. Those should be the operator's people. A vendor may be granted a role, as an integrator may, but by the operator's decision.

Camera feeds, captures, and adapted weights stay in the building too. The vendor's brand on the pool does not make the vendor the custodian of the floor's data, and a facility should make sure the agreement says so. Done properly, a Chassis Grid gives the facility one name to call and the same evidence it would hold under any other route. The How to buy page sets the two routes side by side.