AGENT PLATFORM
Agents that do the job, on the appliance you already run.
E31 Agency is how a team turns Czar into agents that prepare real work, wait where a person has to own the outcome, and leave a run someone can open later. The models are the ones you host. The material stays on the appliance. The appliance runs fully sovereign, or connected only to the systems you already secure. A published version is what goes live.
RUNS ON CZAR · BUILT WITH E31 CONSULTING
WHAT AN AGENT IS HERE
A version of a job your applications can call.
An agent on Agency is a sequence you can name. It takes the packet your desk already uses, reads the material it is allowed to read, drafts or decides, waits where you said a person has to decide, and calls only the systems you described. That sequence is the product. People compose it. Publishing freezes it. A deploy points your applications at one frozen version.
The work executes on Czar. Agency is the control plane: who may publish, which model the agent may use, which tools exist, and the record of what a given run did. If the appliance is air-gapped, the agent is air-gapped. If Czar is allowed to reach systems you already secure, the agent uses the ones you named.
ONE RUN
Prepare the packet. Wait for the person. Keep the record.
A review desk is the shape most of this work takes. The agent does the reading and the draft. The step that changes something outside the appliance belongs to a person.
01
The packet arrives
A claim, a request, a file the desk already understands. The agent takes that packet as its input, through the front door the desk already has.
02
It reads what it may read
The step looks up the material this agent is allowed to use, on the appliance, and drafts from those passages. The corpus stays where you put it.
03
A person owns the outcome
The step that sends, spends, or changes a record waits. The reviewer sees the draft and what it used, and the run continues on that decision.
04
The record closes
The allowed call is made, or the run ends. Inputs, draft, decision, and call are one sequence someone can open tomorrow.
BUILD, RUN, GOVERN
The same agent, from the first sketch to the run you open later.
BUILD
Compose the job
An operator draws the agent as the work actually happens: what it reads, what it decides, where a person has to approve, and which systems it may call. A developer can keep that same agent as a file, so it can be reviewed and moved like any other artifact. Canvas and file are one design.
RUN
Publish a version
Publishing freezes the design. Deploying points a stable address at that version, and your own applications call the address. One live version at a time. When a version is wrong, you point the address back at an earlier published one. Drafts stay drafts.
GOVERN
Account for the run
Each run keeps what went in, what each step did, whether policy allowed it, and who approved when a person had to. A reviewer can follow a live run or open a finished one. Publishing, deploying, and changing a role are written down with who did them.
WHO DOES WHAT
Four roles. One agent between them.
The operator who owns the outcome, the developer who keeps the file, the reviewer on the waiting step, and the admin who decides what the platform is allowed to offer.
Operator
Owns the outcome. Composes the agent, publishes a version, and turns the live address on or off. The canvas is the job, not a prototype beside it.
Developer
Describes the same agent as a file when the team wants it in review, in source control, or generated. The file and the canvas publish as one version.
Reviewer
Sits on the steps that wait. Sees the draft, the sources, and the call that would happen next, then approves or stops the run. The decision stays on the record.
Admin
Decides which models an agent may use, who may publish, and which outside systems are available to be named as tools. A new capability is an administrative decision, then a version.
THE WORK
Jobs an operator can put an agent on.
A PERSON IN THE PATH
Prepare the work, then wait for the person who owns it.
The draft is fast. The step that sends, spends, or changes a record waits.
YOUR MATERIAL
Brief from the corpus already on the appliance.
The sources stay on Czar. The draft comes back with them.
NAMED SYSTEMS
Act in a system you already operate.
The call is described in advance: where it goes, what it sends, which credential.
ONE LIVE VERSION
Publish a version your applications can keep calling.
The address stays. The version behind it is one you froze.
THE RUN
Open yesterday's run and read it in order.
What went in, what came out, who approved, and which call was made.
Your team builds it, or Consulting does.
Operators and developers on your side use Agency directly. When you want engineers who are already trained on Czar, Substrate, and Agency, E31 Consulting takes the use case — sitting with your team, or building it as a project and handing it back running.