Skip to content
ELEMENT 31

Substrate

Substrate is the serving system that runs on a Czar Grid: inference across the pool, latency budgets, memory, retrieval, adaptation, evaluation, integrity verification, and governed connectivity.

· 2 min read

IN SHORT

Substrate is the serving system that runs on a Czar Grid. It performs inference across the pool for every robot in the building and manages the latency budgets, memory, retrieval over the site's documents, adaptation on the site's own captures, evaluation, integrity verification, and governed connectivity around that inference. It is the same on every Czar, whatever the posture or commercial route.

Substrate is the serving system that runs on a Czar Grid. It performs inference across the pool for every robot in the building and manages the latency budgets, memory, retrieval, adaptation, evaluation, integrity verification, and governed connectivity around that inference.

Why it matters

A pool of compute is not useful to a robot on its own. Something has to decide which node answers, make sure the answer arrives inside the time the robot can wait, remember what the site has seen, and keep the whole thing honest. Substrate is that layer.

Without it, an operator would assemble a serving stack from several open projects and then own the integration, the upgrades, and the security review. With it, the pool arrives as a working system: the robot asks, the pool answers, and the record is kept.

How it works at Element 31

Substrate schedules inference across the nodes of the Grid and holds each robot to its own latency budget. A pick arm, a mobile robot, and a humanoid can share the pool without any one of them starving the others.

It keeps memory and retrieval over the site's own documents, so a model answering a floor question can draw on the procedures, layouts, and records that belong to the building. Nothing is fetched from outside.

Adaptation runs on the pool. Models are fine-tuned on the site's own captures, inside the building, and the adapted weights stay on the operator's hardware. Evaluation runs alongside, and the results go into the record.

Watchman is Substrate's integrity verification. It checks that each node is running the sealed, signed, read-only image it claims to run, before the node joins the Grid and before it accepts a task.

Local Bridge is governed connectivity. On a connected site, only routes the site declared are open, and egress is denied by default. On an air-gapped site, there is no path out at all, and updates arrive as signed bundles on media.

Substrate is the same on every Czar, whether the site subscribes through Facility Direct or receives the Grid as Czar Chassis. The posture is a setting, not a different build. The Substrate and Technology pages give the fuller picture.

Questions this raises

Is Substrate a separate product from Czar?
No. Substrate is the serving system that runs on every Czar and across every Czar Grid. A site does not license it separately; the platform license is part of the one subscription for the configured Grid.
What does adaptation mean in Substrate?
Adaptation is fine-tuning models on the site's own captures, performed on the pool inside the building. The adapted weights stay on the operator's hardware, and evaluation runs alongside so the results go into the record.
What does Local Bridge allow out of the building?
Only routes the site declared, with egress denied by default. On a connected site that might be the robot vendors' fleet software or the warehouse system. On an air-gapped site there is no path out at all.

KEEP READING

Related.