Skip to content
ELEMENT 31

RESOURCES

Guides, definitions, and plain answers on Czar: the pool inside a facility, and the one appliance a team runs its agents on.

Topics

  • What a facility inference pool is, how it is sized, and how it serves a floor.

    Browse
  • Humanoids, mobile robots, and arms from more than one vendor, served from one pool.

    Browse
  • Warehouses, plants, terminals, airports, fabs, mines, hospitals, farms, yards, labs: what changes when the pool is in the building.

    Browse
  • One Czar for a team: agents on the team's own records and systems, a named approver, and a record the team holds.

    Browse
  • Czar Keep, the Czar for the data center: four or eight engines in one sealed chassis, serving an organization's people from a machine that never leaves its walls.

    Browse
  • Czar Forge, for technology and AI teams: coding agents, the repository index, tuning, and evaluation on the team's own code and data.

    Browse
  • Air-gapped or connected only to what the site secures. What leaves the building: nothing.

    Browse
  • Installing, updating, and running a pool, including on sites with no path out.

    Browse
  • Facility Direct or Czar Chassis, the subscription, and the integrator's role.

    Browse
  • Short definitions of the terms used across Element 31.

    Browse
  • Direct answers to the questions facilities and robot vendors ask first.

    Browse

LATEST

Recently published.

  • Keep

    A Grid in one chassis

    Czar Keep is not a bigger Czar. It is the engines a Czar Grid is made of, four or eight of them, in one enclosure built for a room that already has racks, with nothing else changed.

    · 4 min read

  • Keep

    A hundred people on one machine

    A Czar Keep serves an organization's people from one machine in its own server room: internal applications calling the models, retrieval over its own records, its agents in Agency Studio, and a record it holds.

    · 5 min read

  • Keep

    A Keep in the server room

    A Czar Keep goes into the rack and the segment the organization already owns, with routes declared at commissioning, signed updates by media or by the organization's network, and support the customer initiates.

    · 5 min read

  • Keep

    Buying Czar Keep

    An organization holds one subscription for a configured Czar Keep: hardware, platform license, and sustainment in one line, fixed for the term. Usage, more people, and more agents do not move it; a change to the configured appliance does.

    · 4 min read

  • Keep

    What Czar Keep is

    Czar Keep is the Czar for the data center: four or eight sovereign AI engines in one sealed chassis, running the same Substrate on the same subscription, standing alone or joining a Czar Grid pool.

    · 4 min read

  • Keep

    Who Czar Keep is for

    Czar Keep is for platform and infrastructure teams that already own a rack and a server room and must serve a hundred-plus people from one machine that never leaves its walls.

    · 5 min read

  • Forge

    A merge a person makes

    On a Czar Forge, agents prepare and propose; a named engineer merges, promotes, or releases. The approvals, the versions, and the replayable record in Agency Studio are how a team stays answerable for what ships.

    · 4 min read

  • Forge

    Adapting models on Czar Forge

    A general model reads the public world's code well and a team's own code as a stranger would. Adaptation on a Czar Forge tunes an open-weight model on the team's repositories and data, on the appliance, and the adapter stays inside.

    · 4 min read

  • Teams

    Supplier commitments on one Czar in the program office

    A program runs on hundreds of supplier promises scattered across inboxes, portals, and spreadsheets. Agents on one Czar in the program office keep the ledger, draft the follow-up for a person to send, and put each slip in front of a named owner.

    · 4 min read

240 articles across 11 topics.Archive: 94 earlier articles