Skip to content
ELEMENT 31

RESOURCES

Guides, definitions, and direct answers on building and governing agents on the appliance.

Topics

  • Agents on Czar

    5

    What an agent is on the appliance, what it may read, call, and change, and where it runs.

    Browse

  • Building

    5

    Designing an agent in Agency Studio: tasks, tools, bounds, tests, and publishing.

    Browse

  • Governance

    5

    Bounds, approvals by named roles, pinned versions, and the run record.

    Browse

  • Operations

    5

    Deploying, pausing, rolling back, and reviewing agents on a site that keeps its own records.

    Browse

  • Integrations

    5

    Connecting agents to the systems the site already secures, and to nothing else.

    Browse

  • Adopting

    5

    From a first agent to a governed estate: who decides, who approves, who reviews.

    Browse

  • Glossary

    6

    Short definitions of the terms used across E31 Agency.

    Browse

  • Questions

    4

    Direct answers to the questions operators, IT, and compliance teams ask first.

    Browse

LATEST

Recently published.

  • Questions

    What happens when a version is wrong?

    The operator points the stable address back at an earlier published version. Nothing is rebuilt, the applications keep calling the same place, and the change is on the record.

    · 3 min read

  • Operations

    Changing a role and leaving a trace

    When someone becomes a reviewer, gains the right to publish, or loses either, the appliance writes it down with who made the change. Roles on Czar have a history.

    · 4 min read

  • Questions

    Can developers work in code instead of the canvas?

    Yes. A developer can keep an agent on Czar as a file for review, source control, or generation. The file and the operator's canvas are one design and publish as one version.

    · 3 min read

  • Operations

    Opening a finished run the next morning

    A question comes in about something the agent did yesterday. The reviewer opens the run and reads it from the packet to the call, with every decision named. No reconstruction.

    · 4 min read

  • Questions

    Does Agency need the internet?

    No. E31 Agency runs on the Czar appliance in the customer's rack. Design, publishing, runs, review, and the record all work with no outside connection.

    · 3 min read

  • Questions

    Can an agent send money or change a record on its own?

    No. On Czar, the step that sends, spends, or changes a record always waits for a person. The agent drafts; a named reviewer decides; then the call is made or the run ends.

    · 3 min read

  • Operations

    Following a live run

    A reviewer can watch a run as it happens: the packet arriving, the passages retrieved, the draft forming, the pause. Here is what that looks like and when it is worth doing.

    · 4 min read

  • Operations

    Pointing the address back at an earlier version

    When a version is wrong, recovery is one deployment act: the stable address is pointed at an earlier published version, exactly as it was. Nothing is rebuilt.

    · 4 min read

  • Glossary

    Glossary: run record

    A run record is what each run of an agent on Czar leaves behind: what went in, what each step did, whether policy allowed it, and who approved. It stays on the appliance.

    · 2 min read

40 articles across 8 topics.