Skip to content
ELEMENT 31

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

IN SHORT

Agency Studio is the task layer on a Czar Grid. It is where site tasks are authored, given a version, bounded with zones, speeds, distances, and stops, approved by named roles, and recorded so that every run can be replayed. It sits above Substrate, which serves inference, and below the robots, which keep their own safety limits.

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

Why it matters

A pool that can perceive and decide is only half of what a floor needs. Someone has to say what the robots are allowed to do, where, how fast, and who signed off. On most sites today that lives in a mix of vendor consoles, spreadsheets, and the memory of the automation lead.

Agency Studio puts that in one place on the pool, inside the building. The safety officer sees the bounds. The integrator sees the version. The operator sees who approved it. When a run goes wrong, the record shows what the task said and what the robot did.

How it works at Element 31

A site task is written in Agency Studio and given a version. Each version carries its bounds: the zones a robot may enter, the speeds it may travel, the distances it may reach, and the stops it must respect. The bounds are part of the task, not a note beside it.

Approval is by named role. A task does not run on the floor until the roles the site defined have signed the version. A change to the bounds is a new version and needs a new approval.

Every run is recorded on the Grid and can be replayed. The record ties the run to the task version, the approvals, and the decisions the pool served. It stays on the operator's hardware alongside the rest of the site's data.

Agency Studio sits above Substrate, which does the inference, and below the robots, which keep their own safety. Stops, speed limits, reflexes, and motion limits remain on the machine as the robot vendor set them. Agency Studio bounds what is asked of the robot; it does not replace the robot's own limits.

It is the same layer whether the site subscribes directly or receives the Grid as Czar Chassis, and it runs on air-gapped and connected sites alike. The Technology page shows where it sits in the stack.

Questions this raises

Who approves a site task?
The site defines named roles, such as an automation lead or a safety officer, and a task version runs only once those roles have signed it. A change to the bounds produces a new version that needs approval again.
Does Agency Studio control the robot's safety functions?
No. Stops, speed limits, reflexes, and motion limits stay on the robot as the vendor shipped them. Agency Studio bounds what a task may ask of the robot and can ask for less than the robot allows, never more.
Where does the run record live?
On the Grid, inside the operator's network, alongside camera feeds, captures, and adapted weights. It is kept on air-gapped and connected sites alike and can be replayed on site.

KEEP READING

Related.