Skip to content
ELEMENT 31

RESOURCES

Short definitions of the terms used across Element 31.

ALL TOPICS

Articles in Glossary

  • Glossary

    Run record

    A run record is the stored, replayable account of one execution of a site task on a Czar Grid: the task version, who approved it, what the robot did, and which decisions the pool served.

    · 2 min read

  • Glossary

    Site task

    A site task is a unit of work for robots on a facility floor, authored in Agency Studio, versioned, bounded by zones, speeds, distances, and stops, and approved by named roles.

    · 2 min read

  • Glossary

    Fallback to the robot

    Fallback to the robot is the rule that when the pool cannot answer within a robot's latency budget, the robot acts on its own on-board model, and if that cannot proceed, it stops.

    · 2 min read

  • Glossary

    Latency budget

    A latency budget is the time a specific robot can wait for an answer from the inference pool before it must act on its own. Substrate holds each robot to its own budget.

    · 2 min read

  • Glossary

    Provenance record

    A provenance record is the documented history of a Czar node, covering its integration, sealing, and software load, so a site can say where its hardware came from from a record.

    · 2 min read

  • Glossary

    Signed update

    A signed update is a software bundle for Czar that carries Element 31's signature. A node verifies the signature before accepting it, so only software Element 31 built reaches the rack.

    · 2 min read

  • Glossary

    Attestation

    Attestation is the step in which a Czar node proves what it is running, its sealed, signed, read-only image and its sealing state, before it joins a Grid or accepts a task.

    · 2 min read

  • Glossary

    Air-gapped

    An air-gapped Czar has no network path out of the building. Inference, adaptation, and the record run inside the operator's network, and updates arrive as signed bundles on media.

    · 2 min read

  • Glossary

    Agency Studio

    Agency Studio is the task layer on a Czar Grid, where site tasks are authored, versioned, bounded, approved by named roles, and recorded so every run can be replayed.

    · 2 min read

  • Glossary

    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

  • Glossary

    Czar Chassis

    Czar Chassis is the Czar Grid shipped by a robot vendor or systems integrator under their own name, with their fleet, so their customer receives one system.

    · 2 min read

  • Glossary

    Czar Grid

    A Czar Grid is several Czar nodes joined into one inference pool for a whole facility. It is the same appliance multiplied, not a second product.

    · 2 min read

  • Glossary

    Czar

    Czar is Element 31's appliance: a sealed node installed in a facility's own rack that provides the inference pool for the robots on that floor.

    · 2 min read

  • Glossary

    Inference pool

    An inference pool is shared compute inside a facility that runs the perception, decision, and language models for every robot in the building, over the building's own network.

    · 2 min read