Skip to content
ELEMENT 31

Glossary: reviewer

The reviewer is the role that sits on the steps where an agent on Czar waits. They see the draft and what it used, approve or stop, and their decision stays on the record.

· 2 min read

IN SHORT

The reviewer is one of the four E31 Agency roles. A reviewer sits on the steps where a run waits, which are the steps that would send, spend, or change a record. They see the draft and the material it used, and they approve or stop. The run continues on that decision, and the decision stays on the record under the reviewer's name.

The reviewer is the E31 Agency role that sits on the steps where a run waits: the steps that would send, spend, or change a record. The reviewer sees the draft and what it used, approves or stops, and the decision stays on the record under their name.

Why it matters

The whole arrangement of an agent on Czar rests on one fact: the agent drafts, and a person decides. The reviewer is that person. Without a reviewer the step that waits would wait forever, which is the design working as intended. An agent cannot promote itself past the reviewer by being confident.

The reviewer is usually the person who already approved that desk's work before there was an agent. The approval step is placed where their decision was already happening. What changes for them is that a draft with its sources arrives instead of a blank form.

How it works here

A packet arrives and the agent reads only what it may read, drafting from those passages on the appliance. When the run reaches a step the version's bounds mark as waiting, it holds. The reviewer sees the draft and exactly what it used: the passages from the corpus and any reads from connected systems.

The reviewer approves or stops. On approve, the allowed call is made. On stop, the run ends with no call. Either way the decision, the reviewer's name, and the moment are written to the run record in sequence with the inputs and the draft. A reviewer can follow a live run as it reaches the waiting step, or open a finished run later to see what was decided and by whom. Changing who holds the reviewer role is itself written down with who changed it.

  • Bounds: where the version marks which steps wait for the reviewer.
  • Run record: where the reviewer's decision is kept.
  • Version: the frozen design that places the waiting step.

Questions this raises

Can a reviewer edit the draft before approving?
The reviewer's decision is to approve or stop the step that waits. A draft that needs changing is a reason to stop, or a reason for the operator to change the design in the next version. The record keeps the draft as the agent produced it and the decision as the reviewer made it.
Does a reviewer have to watch every run live?
No. A reviewer can follow a live run or open a finished one. The step that waits holds until the reviewer decides, so a run can wait for the reviewer to reach it in the course of their work.
Is the reviewer the same as the operator?
They are different roles. The operator composes and publishes the agent; the reviewer clears or stops its actions. A site may assign both to one person on a small desk, but keeping them separate puts two named people on the record for each action.

KEEP READING

Related.