Skip to content
ELEMENT 31

Glossary: Agency Studio

Agency Studio is where an agent on Czar is designed: drawn on a canvas as the work actually happens, or written as a file, and published as a version.

· 2 min read

IN SHORT

Agency Studio is the part of E31 Agency where an agent is designed. An operator draws the agent as the work actually happens, showing what it reads, what it decides, where a person approves, and which systems it may call. A developer can keep the same agent as a file. Canvas and file are one design, and publishing freezes that design into a version.

Agency Studio is the design surface of E31 Agency, running on the Czar appliance, where an operator draws an agent as the work actually happens and a developer can hold the same agent as a file. Canvas and file are one design, and publishing turns that design into a version.

Why it matters

Most agent tooling asks the desk to describe its work in a vocabulary built for software. Agency Studio asks the opposite: draw the work the way it already happens. The packet arrives, the agent reads these things, decides this, waits here for a person, and may call that system. The person who owns the desk can draw that without a developer, and a developer can review it as a file without redrawing it.

Because the canvas and the file are the same design, there is no gap between what the operator intended and what the developer checked in. One version is published from either form, and that version is what the address points at.

How it works here

The operator opens Agency Studio on the appliance and composes the agent step by step. Each step says what the agent reads, what it decides, whether a person has to approve, and which tools the step may call. The admin's decisions set the edges: only models the admin has allowed and only systems the admin has made available as tools can appear on the canvas.

A developer can open the same agent as a file, keep it in source control, review changes line by line, or generate parts of it. Saving the file and saving the canvas are the same act. When the design is ready, publishing freezes it into a version with its bounds written in. Drafts that are not published stay drafts and are never called by anyone.

  • Version: what publishing a design in Agency Studio produces.
  • Bounds: the limits written into a version from the design.
  • Stable address: where a published version is pointed so applications can call it.

Questions this raises

Is Agency Studio a separate product from Czar?
No. It is part of the agent layer that runs on the Czar appliance and ships within the appliance subscription. There is no separate license or seat for it.
Who uses Agency Studio?
Operators, who draw the agent on the canvas, and developers, who describe the same agent as a file. Both publish the same version. Reviewers and admins work with what Agency Studio produces rather than in it.
Can a design be edited while a version is live?
Yes. Editing the design does not change the live version. The live address keeps pointing at the published version until the operator publishes the edited design and points the address at the new one.

KEEP READING

Related.